Please wait...
0 files
Subject: Re: Message with more than 40 destinataries
Cloud you please increase to say 4096 or 8192 charaters instead
of 1024?
Or it has difficult implications on the database?
The database should be able to support it. The bigger problem is the protocol, which accepts commands no longer than 1024 characters. It's a little different from SMTP, which accepts additional recipients one line at a time. Probably if you used SMTP you could go bigger. It's been a while since I've tested it.
It's a legitimate concern, and something we'll likely be working on. But unfortunately it's not a quick fix.
Since updating to 1012, the first access of the website issues a 503 error:
This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
If you reload, it works and stays working. If you navigate away for a while (half hourish?) and go back you get the error again.
In the log, I see a message like:
This is a private/testing instance so I'm the only user, so I can't comment if other users have this problem.
I am not sure if I broke something or it's a regression from 1011 to 1012
Thanks!
Do you have set a Session limit in the options ?
Since updating to 1012, the first access of the website issues a 503 error:
This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
If you reload, it works and stays working. If you navigate away for a while (half hourish?) and go back you get the error again.
In the log, I see a message like:
2025-05-07T17:41:59.145989868Z webcit[8]: StrBuf_ServGetln(): Server connection broken: Resource temporarily unavailableThis is a private/testing instance so I'm the only user, so I can't comment if other users have this problem.
I am not sure if I broke something or it's a regression from 1011 to 1012
Thanks!
I just double checked and concurrent session limit is set to 0.
Thank you
Subject: Re: Initial web access pops 503 error.
I just double checked and concurrent session limit is set to 0.
So ... did changing that to some nonzero value fix it?
Got same Error and set befor session limit to 50. After setting to 0, i got no error anymore.
I just double checked and concurrent session limit is set to 0.
So ... did changing that to some nonzero value fix it?