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