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. Support
  3. Let's Encrypt Issues - 2 Layer Sub Domains

Let's Encrypt Issues - 2 Layer Sub Domains

Scheduled Pinned Locked Moved Solved Support
letsencryptcertificates
7 Posts 2 Posters 1.3k Views 2 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.
  • J Offline
    J Offline
    JLX89
    wrote on last edited by girish
    #1

    Hello All,
    Has anyone been having issues between Cloudron and Let's Encrypt for domains that have two sub-domains, for example site-name.sub-domain.domain.tld? On initial provisioning of the app everything seems to be working smoothly, but if the app restarts or you change the location of the app, it starts generating the below error messages in Google Chrome and Firefox.

    Google Chrome

    This site can’t provide a secure connection
    site.sub.domain.tld uses an unsupported protocol.
    
    ERR_SSL_VERSION_OR_CIPHER_MISMATCH
    

    Firefox

    Secure Connection Failed
    
    An error occurred during a connection to site.sub.domain.tld. Cannot communicate securely with peer: no common encryption algorithm(s).
    
    Error code: SSL_ERROR_NO_CYPHER_OVERLAP
    
        The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
        Please contact the website owners to inform them of this problem.
    

    Any help with this would be greatly appreciate!

    Thank you,
    Justin

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

      Thanks, I have seen this issue in the past with Cloudflare. This is related to Cloudflare not issuing certificates properly. If you disable Cloudflare proxying and re-enable it, it sometimes starts working. If that doesn't work, just delete the subdomain entry and add it again manually inside Cloudflare.

      J 1 Reply Last reply
      0
      • J JLX89

        Hello All,
        Has anyone been having issues between Cloudron and Let's Encrypt for domains that have two sub-domains, for example site-name.sub-domain.domain.tld? On initial provisioning of the app everything seems to be working smoothly, but if the app restarts or you change the location of the app, it starts generating the below error messages in Google Chrome and Firefox.

        Google Chrome

        This site can’t provide a secure connection
        site.sub.domain.tld uses an unsupported protocol.
        
        ERR_SSL_VERSION_OR_CIPHER_MISMATCH
        

        Firefox

        Secure Connection Failed
        
        An error occurred during a connection to site.sub.domain.tld. Cannot communicate securely with peer: no common encryption algorithm(s).
        
        Error code: SSL_ERROR_NO_CYPHER_OVERLAP
        
            The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
            Please contact the website owners to inform them of this problem.
        

        Any help with this would be greatly appreciate!

        Thank you,
        Justin

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

        @JLX89 Which DNS backend are you using ? If it's wildcard, remember that *.domain.com only applies to one level. You have to set add a ..domain.com in the DNS for second level to work.

        J 1 Reply Last reply
        0
        • girishG girish

          @JLX89 Which DNS backend are you using ? If it's wildcard, remember that *.domain.com only applies to one level. You have to set add a ..domain.com in the DNS for second level to work.

          J Offline
          J Offline
          JLX89
          wrote on last edited by
          #3

          @girish We are using primarily Cloudflare.

          girishG 1 Reply Last reply
          0
          • J JLX89

            @girish We are using primarily Cloudflare.

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

            @JLX89 that should work out of the box. Do you see anything in the logs? Can you go to Domains -> Renew All Certs and see what it says in the logs?

            J 1 Reply Last reply
            0
            • girishG girish

              @JLX89 that should work out of the box. Do you see anything in the logs? Can you go to Domains -> Renew All Certs and see what it says in the logs?

              J Offline
              J Offline
              JLX89
              wrote on last edited by
              #5

              @girish I've reached out to support directly with the log files. Another interesting issue that just came up, if I view the logs directly when running the Domains > Renew All Certs task, I can view them. If I try to download the entire log, it's completely blank with no data.

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

                Thanks, I have seen this issue in the past with Cloudflare. This is related to Cloudflare not issuing certificates properly. If you disable Cloudflare proxying and re-enable it, it sometimes starts working. If that doesn't work, just delete the subdomain entry and add it again manually inside Cloudflare.

                J 1 Reply Last reply
                0
                • girishG girish

                  Thanks, I have seen this issue in the past with Cloudflare. This is related to Cloudflare not issuing certificates properly. If you disable Cloudflare proxying and re-enable it, it sometimes starts working. If that doesn't work, just delete the subdomain entry and add it again manually inside Cloudflare.

                  J Offline
                  J Offline
                  JLX89
                  wrote on last edited by
                  #7

                  @girish That did the trick, I appreciate it.

                  1 Reply Last reply
                  0
                  • girishG girish marked this topic as a question on
                  • girishG girish has marked this topic as solved 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