Just wait untill tomorrow, user should be purged an you can create it again.

Sun Jul 11 2021 16:17:54 EDT from johno Subject: user deletion

Having deleted a user I now cannot recreate that user as it says it already exists

hey i have a error when i install citadel on a raspberry 4.

Setup could not connect to a running Citadel server.: Connection refused citadel-admin.socket

everyone a idea?

Greeting to all citadel users.  I just completed an easy-install on a CentOS 8 system and I am having an issue with the cli client.  When I run ./citadel I am prompted to log in and that works, but once i get to the Lobby> prompt then it no longer accepts any input. No matter what commands I try to type, it does nothing.  I cannot even (T)erminate.  The only thing I can do is open another session and do a "killall citadel" to close the client.  I was really hoping for the text client option for use as a legacy BBS style setup.

Thanks in advance for any help!

Never mind... I figured it out.  Finally found that the generated citadel.rc file was placed in the root instead of /usr/local/citadel.  Once i moved it everything works as expected.

Wed Jul 28 2021 22:58:44 EDT from jbach34 Subject: text client not accepting input after logion

Greeting to all citadel users.  I just completed an easy-install on a CentOS 8 system and I am having an issue with the cli client.  When I run ./citadel I am prompted to log in and that works, but once i get to the Lobby> prompt then it no longer accepts any input. No matter what commands I try to type, it does nothing.  I cannot even (T)erminate.  The only thing I can do is open another session and do a "killall citadel" to close the client.  I was really hoping for the text client option for use as a legacy BBS style setup.

Thanks in advance for any help!

Hi all!

I‘ve been running a Citadel server happily for around a year now on a Pi4 under Raspbian Buster, using it as an IMAP and SMTP server.

One of my users needs to change his password due to a potential breach.

When either he changes it or I change it (as admin) it seems to change it ok on the IMAP side but doesn’t change the SMTP side. I‘ve tried both Thunderbird and Microsoft mail as clients.

I think I can probably get around it by creating a temporary new account (say usertemp), copy all of his emails into that on the client, delete his original account, then reply-create the original account the next day with the new password after the auto-purge, then copy everything back from the temp account.

Any ideas about my problem though? 

Appreciate any help,

thanks

Col 

Sat Jul 31 2021 10:19:42 EDT from IGnatius T Foobar Subject: Re: Changing a user password - only changes imap, not smtp

Interesting. I hate to be the one to say "the problem is on your end" but ... Citadel does not have any concept of different passwords for different protocols. The password for an account is the password for all protocols -- IMAP, SMTP, web client access, etc.

The only thing I can think of is perhaps the client is caching old credentials?
Or maybe you have something other than Citadel listening on port 587?

Thanks for replying, what you say makes sense.

I’ll try to set up his client on a fresh device so no there‘s no possibility of the passwords being cached.

There’s definitely only Citadel listening on 587 (goes away to hastily check!) :)

Hi,

tried to use your "AppImage" today to install a fresh Raspberry Pi 4 with 4GB running following Raspian:

lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

cat /etc/debian_version
10.9

Used following image: citadel-932-armv7l.appimage

Independant using citadel-932-armv7l.appimage with run or install, the citadel start crashes with the following information and loops the start every second:

 ./citadel-932-armv7l.appimage -p 8088 -s 8444 run
ctdlvisor: Welcome to the Citadel System, brought to you using AppImage.
ctdlvisor: LD_LIBRARY_PATH = /tmp/.mount_citadeXGtRbm/usr/lib
ctdlvisor:            PATH = /tmp/.mount_citadeXGtRbm/usr/bin
ctdlvisor:          APPDIR = /tmp/.mount_citadeXGtRbm
ctdlvisor:  data directory = /usr/local/citadel
ctdlvisor:       HTTP port = 8088
ctdlvisor:      HTTPS port = 8444
ctdlvisor: citserver running on pid=4882
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: webcit (HTTP) running on pid=4883
ctdlvisor: webcit (HTTPS) running on pid=4884
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/webcit/webcit
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/webcit/webcit
ctdlvisor: pid=4882 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=4885
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=4885 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=4888
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=4888 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=4892
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=4892 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=5019
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=5019 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=5026
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=5026 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=5028
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel

After CTRL-C the following output appears:
^Cctdlvisor: caught signal 2
ctdlvisor: waiting for all child process to exit...
ctdlvisor: 5029 (Citadel Server) ended, status=139
ctdlvisor: waiting for all child process to exit...
ctdlvisor: 4883 (WebCit HTTP) ended, status=15
ctdlvisor: waiting for all child process to exit...
ctdlvisor: 4884 (WebCit HTTPS) ended, status=15
ctdlvisor: waiting for all child process to exit...
ctdlvisor: exit code 0

ps -ef | grep cit shows:
ps -ef | grep -i cit
root     13683     1 25 21:51 ?        00:00:00 /usr/local/citadel/citadel.appimage run -h /usr/local/citadel -p 8088 -s 8444
root     13688 13681  4 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -p 8088 uds /usr/local/citadel
root     13689 13681 34 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -s -p 8444 uds /usr/local/citadel
root     13694 13681  4 21:51 ?        00:00:00 [citserver] <defunct>
root     13696  3876  0 21:51 pts/0    00:00:00 grep -i cit

ps -ef | grep 13681
root     13681     1  0 21:51 ?        00:00:00 ctdlvisor run
root     13688 13681  0 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -p 8088 uds /usr/local/citadel
root     13689 13681  2 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -s -p 8444 uds /usr/local/citadel
root     14047 13681  5 21:51 ?        00:00:00 [citserver] <defunct>
root     14103  3876  0 21:51 pts/0    00:00:00 grep 13681

Using Citadel for several years meanwhile. Running one instance on a Rasperry Pi 3b that I installed with "Easy Install". But as you also provide an Image version, I thought giving this one a try. But it seems not to work for me.

If you need any furhter information, give me a note.

Cheers,
Garfield73

Just to give you a bit more information. After running systemctl stop citadel, the defunc pid disappears - as all the other citadel ones.

If I use then either ...run or do systemctl start citadel, the ps output looks similar to the one I pasted earlier - with different pid´s for sure.

Cheers,
Garfield73

That is the sort of results i got with the pre-release ( on both a PI 2 and a BPI - M3 ). But i didnt really have time to go into it deeper.  I also assumed it was just something i was doing wrong and not systemic ( not uncommon )

Hi,

Did Easy Installation now again. That way works like a piece of cake. But wondering why the AppImage way didn´t work for me.

Thanks,
Garfield73

Hi,

After my pi installation tanked I installed latest onto our 20.04 server.

But we get this

This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More...  (this was the same as I got on the pi)

The status gives this:

$ service citadel status
● citadel.service - LSB: control citadel server start at boot time
     Loaded: loaded (/etc/init.d/citadel; generated)
     Active: active (running) since Mon 2021-08-02 08:52:36 UTC; 1min 13s ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 2 (limit: 2225)
     Memory: 14.8M
     CGroup: /system.slice/citadel.service
             ├─8492 /usr/sbin/citserver -d -x3 -lmail -t/dev/null
             └─9216 /usr/sbin/citserver -d -x3 -lmail -t/dev/null

When I try too check configuration with sudo dpkg-reconfigure citadel-server

The wizard stops after I enter username.

Thanks for any help.

Mon Aug 02 2021 05:06:53 EDT from Knossos Subject: Install on Ubuntu 20.04

Hi,

After my pi installation tanked I installed latest onto our 20.04 server.

But we get this

This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More...  (this was the same as I got on the pi)

The status gives this:

$ service citadel status
● citadel.service - LSB: control citadel server start at boot time
     Loaded: loaded (/etc/init.d/citadel; generated)
     Active: active (running) since Mon 2021-08-02 08:52:36 UTC; 1min 13s ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 2 (limit: 2225)
     Memory: 14.8M
     CGroup: /system.slice/citadel.service
             ├─8492 /usr/sbin/citserver -d -x3 -lmail -t/dev/null
             └─9216 /usr/sbin/citserver -d -x3 -lmail -t/dev/null

When I try too check configuration with sudo dpkg-reconfigure citadel-server

The wizard stops after I enter username.

Thanks for any help.

 

Aug 02 09:02:34 server.xxxxco.uk webcit[665]: tcp_connectsock(127.0.0.1,504)
Aug 02 09:02:34 server.xxxxco.uk webcit[665]: Trying IPv4
Aug 02 09:02:34 server.co.uk webcit[665]: connect() failed: Connection refused
Aug 02 09:02:34 server.tco.uk webcit[665]: HTTP: 200 [0.010416] GET //landing?go=?failvisibly=1
Aug 02 09:10:35 server.o.uk webcit[665]: GET / HTTP/1.1
Aug 02 09:10:35 server.tco.uk webcit[665]: language found: en_GB
Aug 02 09:10:35 server.to.uk webcit[665]: tcp_connectsock(127.0.0.1,504)
Aug 02 09:10:35 server.tco.uk webcit[665]: Trying IPv4
Aug 02 09:10:35 server.co.uk webcit[665]: connect() failed: Connection refused
Aug 02 09:10:35 server.co.uk webcit[665]: HTTP: 200 [0.001800] GET //landing?go=?failvisibly=1

Not a real fan of docker, but i suspect that may be better option in the long run for those that dont want to use easy install.

Tue Aug 03 2021 11:40:55 AM EDT from IGnatius T Foobar

Hmm. The compatibility of the AppImage doesn't seem to be as widespread as I hoped it would be.

I'm starting to wonder whether we should discontinue it before it causes more problems. Most of the work that went into it, can be re-used for a Docker version. That might be a better option.

Just did a fresh install using the easy install, having issues providing certificates for the webcit and citadel ssl authentication.

First, I deleted the /usr/local/webcit/keys directory and linked it to /usr/local/citadel/keys.

Then, I took an existing [domainname].all.pem file generated by ACME and used openssl to pull out the .cer, .csr, and .key files and copied them to the /usr/local/citadel/keys directory.

I restarted the server, but when I went to login again the certificate still reads as the "Certificate for *" with all the default values filled in.

I followed the directions at https://citadel.org/how_to_install_a_certificate_signed_by_a_recognized_certificate_authority.html

Any suggestions would be appreciated.

For clarification, I'm running Debian 10.10 headless on a Raspberry pi 4, apologies for not being more clear

So, the default certificate that Citadel issues is set to an unsupported encryption method - too small of a key. I am hazy on the exact details now - but I had a lot of problems until I figured that out and set the encryption key higher than the default - then all the problems went away. I may be shooting wildly in the dark here. I'm having trouble recalling exactly what the problems were. 

Wed Aug 04 2021 19:07:51 EDT from garrick Subject: Re: issue installing certificates

For clarification, I'm running Debian 10.10 headless on a Raspberry pi 4, apologies for not being more clear