Login to a blank page
-
Hello, just installed Sogo. Logged in for the first time and all I get is a blank page.
Logs show a lot of " No child available to handle incoming request!"
Anyone have any ideas?
-
When I google the problem I see a lot of editing the 'PREFORK=' in /etc/default/sogo to start more workers but there is no such file.
-
@brynjar can you retarting the app (it's in the Repair section) ? Also, maybe try giving it a bit more memory (under Resources).
-
@girish I have restarted, given it up to 4GB of ram and tried re installing. Always the same result.
-
@girish In the start.sh file for Sogo I see the line "WOWorkersCount = 5;" are there only 5 workers running?
The default minimum according to what I have found is 10.
I am unable to edit the file to change that.
-
@brynjar So, what you can do is open a web terminal. Then edit the file
/run/sogo.conf. Then you can dosupervisorctl restart allin the web terminal. This is not the final fix, but atleast it will help figure if that WOWorkersCount fixes it for you.FWIW, I tried installing SOGo now on a couple of cloudrons and it seems to install fine. Strange.
-
@girish Did not help, now all I get is
"[WARN] <0x0x55e73349a5b0[WOWatchDog]> listening socket: attempt 5 failed"
Alot
-
@girish This error is common to
"Feb 12 19:12:35 Feb 12 19:12:35 sogod [17]: [WARN] <0x0x55be928acad0[WOWatchDogChild]> pid 39 has been hanging in the same request for 1 minutes
Feb 12 19:12:35 Feb 12 19:12:35 sogod [17]: [WARN] <0x0x55be9281e400[WOWatchDogChild]> pid 36 has been hanging in the same request for 1 minutes" -
@brynjar Is there anything interesting in
/run/sogo.log(in the app's web terminal)? -
@girish
"Feb 12 19:28:28 sogod [36]: [ERROR] <0x55a7b4350e20[SOGoMailAccount]:0> Could not connect IMAP4
Feb 12 19:28:28 sogod [37]: [ERROR] <0x55a7b3d5f3d0[SOGoMailAccount]:0> Could not connect IMAP4""Feb 12 19:30:03 sogod [35]: [ERROR] <0x0x55a7b3a2bcd0[NGImap4ConnectionManager]> IMAP4 login failed:"
-
@girish Hmm strange, for some reason the old MX settings are active. I am going to look into it further.
-
@brynjar Still a bit strange that IMAP login makes SOGo show white screen. This reminded me of https://docs.cloudron.io/apps/sogo/#ui-issues . Can you try visiting SOGo directly and not via the dashboard on Cloudron and see if the UI appears?
-
also, SOGo is meant to work only with the Cloudron mail server and the package pre-configures for login with the mail server.
-
@girish Going directly to the mail url changed nothing, still blank. I tried connecting to IMAP with Thunderbird and I get my mail fine so the problem is not IMAP. More like Sogo is not able to talk to it maby?
In dns my old mail server and the new cloudron were both added and with same priority, 10. I deleted the old server from dns.
-
@girish I see the sogo server is trying to log in to my main url. The server is not directly connected to its external ip, it is behind nat. Can that be causing this?
-
@brynjar Do you know if hairpin routing works on your setup? Essentially, you should be able to curl the external IP from the Cloudron. Does that work? You can try
curl https://my.domain.comfrom the server. If that doesn't work, then I can provide some alternate solutions.edit: https://en.wikipedia.org/wiki/Network_address_translation#NAT_loopback
-
@girish I get this:
"<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
" -
@brynjar Did you do http by any chance or was it https? Can you paste the output of
curl -v https://my.domain.com(maybe remove any sensitive stuff). But I feel this is probably your router login page or something, let's see. -
@girish This is from http - https gives an ssl error.
"curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.htmlcurl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
" -
@brynjar
curl -kv https://my.domain.comthen (-k will accept self-signed cert) -
@girish I get the login page of the router, pfsense. This is a dns rebind blocking thing.
-
@girish Disabling dns rebind check does not change anything. Not sure why.
-
@brynjar Given this is a server in the local network, how do you plan to make the mail server make anyway? It will need inbound port 25 (does your ISP allow this?) for email to work at all.
Anyway if you have a plan for all that
... Cloudron uses a DNS server called unbound internally. You can configure unbound to make queries via an intermittent resolver, for example, maybe pfsense. Then in pfsense you can configure my.domain.comto point to your internal IP. This ways curl my.domain.com from inside Cloudron will work. There's some info at https://docs.cloudron.io/networking/#internal-dns-server (instead ofcloudron.lanin the example you would usedomain.com) -
@girish This server is on a corp network with more then one external ip's. I have all traffic for one external ip natted to the cloudron server, both directions.
-
@brynjar Ah ok. FWIW, this is only a problem with SOGo. They made a change where the IMAP/SMTP servers must have a proper certificate and there is no way to work with self-signed certs. rainloop/roundcube are configured to use the internal docker hostnames, so they don't have this problem iirc.
-
@girish Damn it, Sogo is the only webmail I like of these, Roundcube is so boring.
