Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Navigation

    Cloudron Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Login to a blank page

    SOGo
    2
    26
    56
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      brynjar last edited by

      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?

      B 1 Reply Last reply Reply Quote 0
      • B
        brynjar @brynjar last edited by

        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.

        girish 1 Reply Last reply Reply Quote 0
        • girish
          girish Staff @brynjar last edited by

          @brynjar can you retarting the app (it's in the Repair section) ? Also, maybe try giving it a bit more memory (under Resources).

          B 2 Replies Last reply Reply Quote 0
          • B
            brynjar @girish last edited by

            @girish I have restarted, given it up to 4GB of ram and tried re installing. Always the same result.

            1 Reply Last reply Reply Quote 0
            • B
              brynjar @girish last edited by

              @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.

              girish 1 Reply Last reply Reply Quote 0
              • girish
                girish Staff @brynjar last edited by

                @brynjar So, what you can do is open a web terminal. Then edit the file /run/sogo.conf. Then you can do supervisorctl restart all in 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.

                B 2 Replies Last reply Reply Quote 0
                • B
                  brynjar @girish last edited by

                  @girish Did not help, now all I get is

                  "[WARN] <0x0x55e73349a5b0[WOWatchDog]> listening socket: attempt 5 failed"

                  Alot

                  1 Reply Last reply Reply Quote 0
                  • B
                    brynjar @girish last edited by

                    @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"

                    girish 1 Reply Last reply Reply Quote 0
                    • girish
                      girish Staff @brynjar last edited by

                      @brynjar Is there anything interesting in /run/sogo.log (in the app's web terminal)?

                      B 2 Replies Last reply Reply Quote 0
                      • B
                        brynjar @girish last edited by brynjar

                        @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:"

                        1 Reply Last reply Reply Quote 0
                        • B
                          brynjar @girish last edited by

                          @girish Hmm strange, for some reason the old MX settings are active. I am going to look into it further.

                          girish 1 Reply Last reply Reply Quote 0
                          • girish
                            girish Staff @brynjar last edited by

                            @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?

                            1 Reply Last reply Reply Quote 0
                            • girish
                              girish Staff last edited by

                              also, SOGo is meant to work only with the Cloudron mail server and the package pre-configures for login with the mail server.

                              B 2 Replies Last reply Reply Quote 0
                              • B
                                brynjar @girish last edited by

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • B
                                  brynjar @girish last edited by

                                  @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?

                                  girish 1 Reply Last reply Reply Quote 0
                                  • girish
                                    girish Staff @brynjar last edited by girish

                                    @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.com from 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

                                    B 1 Reply Last reply Reply Quote 0
                                    • B
                                      brynjar @girish last edited by

                                      @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>
                                      "

                                      girish 1 Reply Last reply Reply Quote 0
                                      • girish
                                        girish Staff @brynjar last edited by girish

                                        @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.

                                        B 1 Reply Last reply Reply Quote 0
                                        • B
                                          brynjar @girish last edited by

                                          @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.html

                                          curl 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.
                                          "

                                          girish 1 Reply Last reply Reply Quote 0
                                          • girish
                                            girish Staff @brynjar last edited by

                                            @brynjar curl -kv https://my.domain.com then (-k will accept self-signed cert)

                                            B 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post