I thought of that too, but never got far enough on mine to try .. Something tells me in his case it might fail too.. Since its the same process that set it up 'wrong'.  So the thought of doing it 'direct' with a clearly known value.  Wasn't sure if that is even possible? Didn't know if you encrypted it or not. And since my install failed... wasn't able to go look, but it was on my original list of things to do.  ( im still curious, only reason i mention it )

Tue Nov 26 2024 02:25:45 UTC from IGnatius T Foobar

And while someone else would need to chime in, i would assume
you could go into the DB manually and reset the password to a
known value. Just in case something weird is going on with your
terminal when you entered it during hte install.

Or you could just run "setup" and it would let you do the same thing.

Fri Nov 22 2024 16:31:51 UTC from kamyl Subject: Problem with perfoming configuration setup after installation

Hi,

I installed Citadel on Raspbery Pi 5 8GB. I know it is possible because this process is described here:

https://pimylifeup.com/raspberry-pi-email-server/

Unfortunately, after the installation is completed, at the last stage of configuration, when the reconfiguration that ends the installation process is suspended.

 

Reconfiguring Citadel server
  Citadel Server setup

Restarting Citadel server to apply changes
[***********************************************************************....]

 

I tried to repeat this process several times but without any changes.

I used the curl and wget installation. Unchanged.

 

Perhaps someone has already reported such a problem, or you have suggestions what I could do to be able to use your product.

 

Thank you in advance.

 

Kamil

 

@Kamil

I had the same problem on different distributions.

My solution was to forward the ports for the server on my router to the raspberry pi 4

Because the setup of Citadel did try to connect to the server and without the right open ports the connection failed.

After forwarding the ports to the server the setup did finalize.

Maybe this can cause the problem with your setup also.

In my case, i have no firewall installed ( i let my nginx server handle that for external facing services ). Not ever seen this before in the past. tho i do fully admit ive not done an install for quite a few versions now, so this might be a 'new' issue or an older one. no clue.

Not a huge deal for me as im not running an instance these days but it at least did confirm the issue and am more than willing to try other things and report them back to the crew.

Wed Nov 27 2024 13:31:41 UTC from alcomys Subject: Re: Problem with perfoming configuration setup after installation

 

 

I had the same problem on different distributions.

My solution was to forward the ports for the server on my router to the raspberry pi 4

Because the setup of Citadel did try to connect to the server and without the right open ports the connection failed.

After forwarding the ports to the server the setup did finalize.

Maybe this can cause the problem with your setup also.

 

Wed Nov 27 2024 15:03:34 UTC from Nurb432 Subject: Re: Problem with perfoming configuration setup after installation

In my case, i have no firewall installed ( i let my nginx server handle that for external facing services ). Not ever seen this before in the past. tho i do fully admit ive not done an install for quite a few versions now, so this might be a 'new' issue or an older one. no clue.

Not a huge deal for me as im not running an instance these days but it at least did confirm the issue and am more than willing to try other things and report them back to the crew.

Wed Nov 27 2024 13:31:41 UTC from alcomys Subject: Re: Problem with perfoming configuration setup after installation

 

 

I had the same problem on different distributions.

My solution was to forward the ports for the server on my router to the raspberry pi 4

Because the setup of Citadel did try to connect to the server and without the right open ports the connection failed.

After forwarding the ports to the server the setup did finalize.

Maybe this can cause the problem with your setup also.

 

 

Due to the problems installing citadel, i try to find another server to install.

I love the interface and functions from citadel but without a working install i have to move to another platform i think.

Maybe in the future when the easy installer has some update or something i can switch back.

@Nurb432 Thanks for the help.

before you go, please try docker... 

Wed Nov 27 2024 17:42:49 UTC from alcomys Subject: Re: Problem with perfoming configuration setup after installation

 

 

 

Due to the problems installing citadel, i try to find another server to install.

I love the interface and functions from citadel but without a working install i have to move to another platform i think.

Maybe in the future when the easy installer has some update or something i can switch back.

 

@Nurb432 Thanks for the help.

 

For what its worth, it died on me in a X86 VM, bare Debian. ( from my notes above ).   So may not need to try this on a PI to reproduce.

Wed Nov 27 2024 18:56:54 UTC from IGnatius T Foobar Subject: Re: Problem with perfoming configuration setup after installation

Gee, and I was in the process of clearing away existing workloads on my Pi so I could try to reproduce your problem.

I'm running latest bookworm with today's updates.  On a raspberry pi 5 b 1.0 8 gig memory.

I would happy to give you an "atta boy" if you can get this to run on my pi.

Night

Linux raspberrypi 6.6.51+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"

VERSION_ID="12"

VERSION_CODENAME=bookworm

Linux raspberrypi 6.6.51+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

Model: Raspberry Pi 5 Model B Rev 1.0

Raspberry Pi problems, difficulties with the build, and problems using the default username/password, are all likely to be fixed in Citadel version 1007.

The updated build is now available in Easy Install, and the Docker version is likely to be pushed by the time you read this.

Turned out to be one of those bugs that makes you say "how did this ever work?" but for some reason it usually did.  Usually.

Thank you everyone for the bug reports.  Please give the new version a try.

Thu Nov 28 2024 04:49:40 UTC from IGnatius T Foobar Subject: All recently reported bugs are likely fixed in Citadel 1007

Raspberry Pi problems, difficulties with the build, and problems using the default username/password, are all likely to be fixed in Citadel version 1007.

The updated build is now available in Easy Install, and the Docker version is likely to be pushed by the time you read this.

Turned out to be one of those bugs that makes you say "how did this ever work?" but for some reason it usually did.  Usually.

Thank you everyone for the bug reports.  Please give the new version a try.

@Ignatius T Foobar

That sounds good.

I try the new version for the last time, I hope it works on my Pi

I let you know the results here.

Thu Nov 28 2024 09:03:29 UTC from alcomys Subject: Re: All recently reported bugs are likely fixed in Citadel 1007

 

Thu Nov 28 2024 04:49:40 UTC from IGnatius T Foobar Subject: All recently reported bugs are likely fixed in Citadel 1007

Raspberry Pi problems, difficulties with the build, and problems using the default username/password, are all likely to be fixed in Citadel version 1007.

The updated build is now available in Easy Install, and the Docker version is likely to be pushed by the time you read this.

Turned out to be one of those bugs that makes you say "how did this ever work?" but for some reason it usually did.  Usually.

Thank you everyone for the bug reports.  Please give the new version a try.

@Ignatius T Foobar

That sounds good.

I try the new version for the last time, I hope it works on my Pi

I let you know the results here.

 

Hi Guys.

I can confirm that the new version works on the fly.

No problems anymore on my Rapsberry pi 3/4 and debian 12 bookworm.

The password problem when login at webcit has also solved.

We are good to go now. Thanks to the creator for this nice update.

You posted this while i was reloading a VM to test..  so you beat me to it ;)  But ya success again here too. yay.

Thu Nov 28 2024 09:53:00 UTC from alcomys Subject: Re: All recently reported bugs are likely fixed in Citadel 1007

 

 

Hi Guys.

I can confirm that the new version works on the fly.

No problems anymore on my Rapsberry pi 3/4 and debian 12 bookworm.

The password problem when login at webcit has also solved.

 

We are good to go now. Thanks to the creator for this nice update.

 

Thu Nov 28 2024 15:07:37 UTC from Nurb432 Subject: Re: All recently reported bugs are likely fixed in Citadel 1007

You posted this while i was reloading a VM to test..  so you beat me to it ;)  But ya success again here too. yay.

 

 

Thu Nov 28 2024 09:53:00 UTC from alcomys Subject: Re: All recently reported bugs are likely fixed in Citadel 1007

 

 

Hi Guys.

I can confirm that the new version works on the fly.

No problems anymore on my Rapsberry pi 3/4 and debian 12 bookworm.

The password problem when login at webcit has also solved.

 

We are good to go now. Thanks to the creator for this nice update.

 

 

I'm sorry Nurb432,

I can install this with my eyes closed now :) , lol

So I made two SD-cards with different systems and try to install on it so that i can switch fast between systems.

But everybody is happy now i think of a working easy-install.

So let me ask a question to anyone who is paying attention right now.

What made you decide to go with the Easy Install build instead of the Docker build?

One of the guiding principles of the Citadel project is that we want it to be really easy to get the software installed.  Easy Install was built with that goal in mind, but the Docker install is even easier.  So what was it that made those of you who did the Easy Install decide to go that way?  Did you try the Docker build and it didn't work?  Was there something missing from it?  Or just an aversion to using Docker out of unfamiliarity?  Something else?

The target audience for the Citadel system has changed over the years.  In the 1980s it was just the BBS crowd.  In the late 1990s/2000s it became popular with people who needed a simple groupware server.  Today, with the mainstream having moved from onsite servers to the clown, we are popular with people who are into repatriation, self-hosting, and data sovreignty.  That does have an impact on how we deliver the software.  Obviously it makes no sense to go the SaaS route, "just put it in the clown and let people sign up for accounts".  Our users want the software and have their own opinion about how to run it.  So we want to know from the audience, what are you looking for and how can we continue making it easier to deploy.

I know my vote does not count ( and i have mentioned it before ), but in general prefer native installs over containers ( be it docker, jails, whatever ).  For separation i use VMs, its 100% separate that way.  I just prefer to work with 'native' OS installs, that are truly isolated. 

Of course if there is no other option for a particular piece of software for whatever reason, ill use docker, but not by preference.

whatever was done, it fixed my install problem.  Works great.  Thank you.

night

Being completely honest, I'm a total noob when it comes to docker, and have always had a poor experience with it, so, I just go native.

My desire to run the software has helped me continue to learn the nature of modern *nix systems, since I'm still somewhat of a novice with them.

So basically a case of carefully picking my battle, if that makes sense?