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. Logging into Cloudron with OpenID Fails After Update to 7.7.0

Logging into Cloudron with OpenID Fails After Update to 7.7.0

Scheduled Pinned Locked Moved Solved Support
21 Posts 3 Posters 761 Views 3 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.
  • P Offline
    P Offline
    pathab
    wrote on last edited by
    #11

    Ok, I have now deleted the DNS setting, deactivated the IPv6 setting and restarted the server. Now OpenID no longer works for all apps and https://my.domain.com/.well-known/openid-configuration is no longer accessible.
    But now I was able to perform a completely fresh installation of Surfer. However, the login via OpenID does not work there either.
    grafik.png

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #12

      If you open a webterminal into any app, can you curl -v https://my.yourdomain.com/.well-known/openid-configuration if not, does the DNS resolve correctly? If yes, I guess it is also a hairpinning issue then.

      1 Reply Last reply
      0
      • P Offline
        P Offline
        pathab
        wrote on last edited by
        #13

        Yes, the IP is resolved correctly. But without response. Could it be that this nginx route is no longer working properly?

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

          @pathab does curl -4 -v https://my.yourdomain.com/.well-known/openid-configuration work? This forces IPv4. Maybe some caching issue somewhere is causing a IPv6 query.

          1 Reply Last reply
          0
          • P Offline
            P Offline
            pathab
            wrote on last edited by
            #15

            Unfortunately, it's the same story.

            girishG 1 Reply Last reply
            0
            • P pathab

              Unfortunately, it's the same story.

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

              @pathab what is the output? also, does the curl not work only on the server or from anywhere?

              1 Reply Last reply
              0
              • P Offline
                P Offline
                pathab
                wrote on last edited by
                #17

                the output is the same everywhere

                *   Trying xxx.xxx.xxx.xxx:443...
                * connect to xxx.xxx.xxx.xxx port 443 failed: Connection timed out
                * Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out
                * Closing connection 0
                curl: (28) Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out
                
                girishG 1 Reply Last reply
                0
                • P pathab

                  the output is the same everywhere

                  *   Trying xxx.xxx.xxx.xxx:443...
                  * connect to xxx.xxx.xxx.xxx port 443 failed: Connection timed out
                  * Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out
                  * Closing connection 0
                  curl: (28) Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out
                  
                  girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by girish
                  #18

                  @pathab are you hosting at home? If so, https://docs.cloudron.io/troubleshooting/#hairpin-nat is the most likely issue. Your network has no mechanism to reach itself via public IP.

                  But, before we go into this, another test. Can you try to curl that URL from another network altogether ? Say via your mobile phone network or equivalent? Does that work ?

                  1 Reply Last reply
                  0
                  • P Offline
                    P Offline
                    pathab
                    wrote on last edited by
                    #19

                    It seems like you're right and the new modem is the problem, sorry I forgot to mention that - didn't expect that to be the cause. (Because cloudron has been running very smoothly for over a year now).
                    Well, I have now moved the server to a VPS. Everything seems to be working there now. I will try to get my cloudron home server up and running again at a later date. Thank you very much for your time and support!

                    1 Reply Last reply
                    1
                    • P Offline
                      P Offline
                      pathab
                      wrote on last edited by
                      #20

                      btw. I just love how easy it is to transfer cloudron to a new server!

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

                        @pathab ah nice, great you found the root cause!

                        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