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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. FreeScout
  3. Connection could not be established with host mail.domain.com [Connection timed out #110]

Connection could not be established with host mail.domain.com [Connection timed out #110]

Scheduled Pinned Locked Moved Solved FreeScout
43 Posts 6 Posters 1.5k Views 6 Watching
  • 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.
  • girishG girish

    Can you try openssl s_client -connect <mailsever>:993 -crlf from web terminal of FS? Does it connect?

    bmannB Offline
    bmannB Offline
    bmann
    wrote on last edited by
    #32

    @girish said in Connection could not be established with host mail.domain.com [Connection timed out #110]:

    openssl s_client -connect <mailsever>:993 -crlf

    Since I'm using the localhost settings that HD said, I used this (note host name and alt port):

    openssl s_client -connect mail:9393 -crlf

    Got this response:

    CONNECTED(00000003)
    40A74365227F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:354:
    ---
    no peer certificate available
    ---
    No client certificate CA names sent
    ---
    SSL handshake has read 5 bytes and written 293 bytes
    Verification: OK
    ---
    New, (NONE), Cipher is (NONE)
    Secure Renegotiation IS NOT supported
    Compression: NONE
    Expansion: NONE
    No ALPN negotiated
    Early data was not sent
    Verify return code: 0 (ok)
    ---
    
    1 Reply Last reply
    0
    • nebulonN Away
      nebulonN Away
      nebulon
      Staff
      wrote on last edited by nebulon
      #33

      Is it possible that there is port typo? It would be 9993 not 9393. So tripple 9

      humptydumptyH 1 Reply Last reply
      0
      • nebulonN nebulon

        Is it possible that there is port typo? It would be 9993 not 9393. So tripple 9

        humptydumptyH Offline
        humptydumptyH Offline
        humptydumpty
        wrote on last edited by humptydumpty
        #34

        @nebulon I've been using it as 9393, and that's how Girish has it also in the screenshots he sent me during our troubleshooting. Sending and fetching are working with 9393.

        Edit: I'll try reverting to the original settings soon to test with v8.2.3.

        1 Reply Last reply
        0
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by girish
          #35

          9393 is the internal IMAP port that does not offer TLS. But my original question was to connect to the external endpoint which is the correct way to configure FreeScout. openssl s_client -connect <mailsever>:993 -crlf where mailserver is my.domain.com (whatever the mail server domain is)

          There are updated screenshots at https://docs.cloudron.io/apps/freescout/#cloudron-mailbox on how to connect.

          bmannB 1 Reply Last reply
          0
          • girishG girish

            9393 is the internal IMAP port that does not offer TLS. But my original question was to connect to the external endpoint which is the correct way to configure FreeScout. openssl s_client -connect <mailsever>:993 -crlf where mailserver is my.domain.com (whatever the mail server domain is)

            There are updated screenshots at https://docs.cloudron.io/apps/freescout/#cloudron-mailbox on how to connect.

            bmannB Offline
            bmannB Offline
            bmann
            wrote on last edited by
            #36

            @girish

            CONNECTED(00000003)
            depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
            verify return:1
            depth=1 C = US, O = Let's Encrypt, CN = E6
            verify return:1
            depth=0 CN = *.commonscomputer.com
            verify return:1
            ---
            Certificate chain
             0 s:CN = *.commonscomputer.com
               i:C = US, O = Let's Encrypt, CN = E6
               a:PKEY: id-ecPublicKey, 384 (bit); sigalg: ecdsa-with-SHA384
               v:NotBefore: Dec  9 07:12:07 2024 GMT; NotAfter: Mar  9 07:12:06 2025 GMT
             1 s:C = US, O = Let's Encrypt, CN = E6
               i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
               a:PKEY: id-ecPublicKey, 384 (bit); sigalg: RSA-SHA256
               v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
            ---
            Server certificate
            
            (several more screenfuls of certs and things)
            
            read R BLOCK
            * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN] Dovecot (Ubuntu) ready.
            
            girishG 1 Reply Last reply
            1
            • bmannB bmann

              @girish

              CONNECTED(00000003)
              depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
              verify return:1
              depth=1 C = US, O = Let's Encrypt, CN = E6
              verify return:1
              depth=0 CN = *.commonscomputer.com
              verify return:1
              ---
              Certificate chain
               0 s:CN = *.commonscomputer.com
                 i:C = US, O = Let's Encrypt, CN = E6
                 a:PKEY: id-ecPublicKey, 384 (bit); sigalg: ecdsa-with-SHA384
                 v:NotBefore: Dec  9 07:12:07 2024 GMT; NotAfter: Mar  9 07:12:06 2025 GMT
               1 s:C = US, O = Let's Encrypt, CN = E6
                 i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
                 a:PKEY: id-ecPublicKey, 384 (bit); sigalg: RSA-SHA256
                 v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
              ---
              Server certificate
              
              (several more screenfuls of certs and things)
              
              read R BLOCK
              * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN] Dovecot (Ubuntu) ready.
              
              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #37

              @bmann perfect. Simply use that domain/port to configure FS

              humptydumptyH 1 Reply Last reply
              1
              • girishG girish

                @bmann perfect. Simply use that domain/port to configure FS

                humptydumptyH Offline
                humptydumptyH Offline
                humptydumpty
                wrote on last edited by
                #38

                @girish It looks like FS is working fine with v.8.2.3 using the proper settings shown in the docs. Thanks for the prompt fixes!

                1 Reply Last reply
                1
                • humptydumptyH Offline
                  humptydumptyH Offline
                  humptydumpty
                  wrote on last edited by humptydumpty
                  #39

                  @girish I forgot to ask, are these still the best settings to use or can we set an encryption now?

                  I'm using Mailgun SMTP.

                  Manage > Settings > Mail Settings

                  27f59042-75fd-49cb-b473-e2bd696cb23d-image.png

                  girishG 1 Reply Last reply
                  0
                  • humptydumptyH humptydumpty

                    @girish I forgot to ask, are these still the best settings to use or can we set an encryption now?

                    I'm using Mailgun SMTP.

                    Manage > Settings > Mail Settings

                    27f59042-75fd-49cb-b473-e2bd696cb23d-image.png

                    girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #40

                    @humptydumpty said in Connection could not be established with host mail.domain.com [Connection timed out #110]:

                    @girish I forgot to ask, are these still the best settings to use or can we set an encryption now?

                    Your screenshot is still using the internal connection. The internal connection doesn't need any encryption since they don't leave the server. I don't expect the values to change but those values are still internal/cloudron implementation detail. I suggest using the settings as in the docs at https://docs.cloudron.io/apps/freescout/#cloudron-mailbox . Those use STARTTLS (SMTP) and SSL (IMAP)

                    humptydumptyH 1 Reply Last reply
                    0
                    • girishG girish

                      @humptydumpty said in Connection could not be established with host mail.domain.com [Connection timed out #110]:

                      @girish I forgot to ask, are these still the best settings to use or can we set an encryption now?

                      Your screenshot is still using the internal connection. The internal connection doesn't need any encryption since they don't leave the server. I don't expect the values to change but those values are still internal/cloudron implementation detail. I suggest using the settings as in the docs at https://docs.cloudron.io/apps/freescout/#cloudron-mailbox . Those use STARTTLS (SMTP) and SSL (IMAP)

                      humptydumptyH Offline
                      humptydumptyH Offline
                      humptydumpty
                      wrote on last edited by humptydumpty
                      #41

                      @girish I'm referring to the app mail settings, not the mailbox. You can find that under: Manage > Settings > Mail Settings

                      What if my FS and mailserver aren't on the same server. What app mail settings should I use? The docs don't cover the above settings page; only shows the mailbox set up.

                      As for the mailboxes, I set up them up as shown in the docs, using SSL and STARTTLS and they're working fine with v8.2.3. 👍

                      P.S. I noticed my emails from InvoiceNinja went to the spam folder because something was off, but it looks like v8.2.3 fixed that too.

                      girishG 1 Reply Last reply
                      1
                      • humptydumptyH humptydumpty

                        @girish I'm referring to the app mail settings, not the mailbox. You can find that under: Manage > Settings > Mail Settings

                        What if my FS and mailserver aren't on the same server. What app mail settings should I use? The docs don't cover the above settings page; only shows the mailbox set up.

                        As for the mailboxes, I set up them up as shown in the docs, using SSL and STARTTLS and they're working fine with v8.2.3. 👍

                        P.S. I noticed my emails from InvoiceNinja went to the spam folder because something was off, but it looks like v8.2.3 fixed that too.

                        girishG Offline
                        girishG Offline
                        girish
                        Staff
                        wrote on last edited by
                        #42

                        @humptydumpty ah, I am blind 😄 sorry, the settings are correct then. Those are autoconfigured by the package. There is no security issue since the connection is entirely internal.

                        To answer the rest, think of it like this:

                        • Manage > Settings > Mail Settings - This is auto-configured by the app . I think FS sends this for password reset, invite , system email etc. All this goes internally from app to the internal mail server conection. Cloudron mail server will then deliver the email based on your Mail -> Domain -> Outbound settings (in Cloudron dashboard). This is how the email of all apps is auto-configured. the packaging logic will overwrite/change these values automatically as needed (like if we change how internal stuff works).

                        • Mailbox - FS can be configured to fetch emails from anywhere (gmail, outlook, etc). In that context, using Cloudron mail is just a special case. This is why we encourage to use the normal Cloudron mail credentials here. The packaging logic does not (and in a general way cannot) touch these values. These credentials won't change since this is how everyone is accessing Cloudron Email.

                        humptydumptyH 1 Reply Last reply
                        1
                        • girishG girish

                          @humptydumpty ah, I am blind 😄 sorry, the settings are correct then. Those are autoconfigured by the package. There is no security issue since the connection is entirely internal.

                          To answer the rest, think of it like this:

                          • Manage > Settings > Mail Settings - This is auto-configured by the app . I think FS sends this for password reset, invite , system email etc. All this goes internally from app to the internal mail server conection. Cloudron mail server will then deliver the email based on your Mail -> Domain -> Outbound settings (in Cloudron dashboard). This is how the email of all apps is auto-configured. the packaging logic will overwrite/change these values automatically as needed (like if we change how internal stuff works).

                          • Mailbox - FS can be configured to fetch emails from anywhere (gmail, outlook, etc). In that context, using Cloudron mail is just a special case. This is why we encourage to use the normal Cloudron mail credentials here. The packaging logic does not (and in a general way cannot) touch these values. These credentials won't change since this is how everyone is accessing Cloudron Email.

                          humptydumptyH Offline
                          humptydumptyH Offline
                          humptydumpty
                          wrote on last edited by
                          #43

                          @girish Great. Thanks for the clarification!

                          1 Reply Last reply
                          0
                          • bmannB bmann referenced this topic on
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Bookmarks
                          • Search