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
  • Brite
  • 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 - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Openid-configuration url timeout

Openid-configuration url timeout

Scheduled Pinned Locked Moved Solved Support
oidcwell-known
14 Posts 4 Posters 201 Views 5 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.
  • T Offline
    T Offline
    TLeM4
    wrote last edited by
    #5

    There are multiple restart here:

    Apr 17 15:24:56 v2202511123714403001 nginx[95120]: 2026/04/17 15:24:56 [error] 95120#95120: *20887 connect() failed (111: Connection refused) while connecting to upstream, client: 82.64.140.175, server: my.mydomain.fr, request: "GET /api/v1/apps?access_token=t3-AwZD9PcPP8maoMtd-M9NsXkI920wppSYuXzK6qfc HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/apps?access_token=t3-AwZD9PcPP8maoMtd-M9NsXkI920wppSYuXzK6qfc", host: "my.mydomain.fr", referrer: "https://my.mydomain.fr/"
    Apr 17 15:24:56 v2202511123714403001 nginx[95120]: 2026/04/17 15:24:56 [error] 95120#95120: *20887 connect() failed (111: Connection refused) while connecting to upstream, client: 82.64.140.175, server: my.mydomain.fr, request: "GET /api/v1/cloudron/status HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/cloudron/status", host: "my.mydomain.fr", referrer: "https://my.mydomain.fr/"
    Apr 17 15:26:37 v2202511123714403001 nginx[97591]: 2026/04/17 15:26:37 [error] 97591#97591: *21376 connect() failed (111: Connection refused) while connecting to upstream, client: 82.64.140.175, server: my.mydomain.fr, request: "GET /api/v1/apps?access_token=t3-AwZD9PcPP8maoMtd-M9NsXkI920wppSYuXzK6qfc HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/apps?access_token=t3-AwZD9PcPP8maoMtd-M9NsXkI920wppSYuXzK6qfc", host: "my.mydomain.fr", referrer: "https://my.mydomain.fr/"
    Apr 17 15:26:37 v2202511123714403001 nginx[97591]: 2026/04/17 15:26:37 [error] 97591#97591: *21376 connect() failed (111: Connection refused) while connecting to upstream, client: 82.64.140.175, server: my.mydomain.fr, request: "GET /api/v1/cloudron/status HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/cloudron/status", host: "my.mydomain.fr", referrer: "https://my.mydomain.fr/"
    
    1 Reply Last reply
    0
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by james
      #6

      Hello @tlem4
      I don't think I will be able to assist here much further.
      Please write a mail to support@cloudron.io and enable remote-support on your server.

      1 Reply Last reply
      0
      • jamesJ Offline
        jamesJ Offline
        james
        Staff
        wrote last edited by
        #7

        Hello @tlem4
        Another user is also running into this issue, so there is something going on.

        1 Reply Last reply
        0
        • jamesJ james referenced this topic
        • nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote last edited by
          #8

          I was able to look at the logs, and I can see those occasional timeouts, but there is nothing further to match this to anything related as far as I can tell. Unless there is some temporary occasional network routing issue where we end up with timeouts, all I can think of that the system might be under heavy load in brief moments (below 1min) causing such a timeout.

          1 Reply Last reply
          0
          • T Offline
            T Offline
            TLeM4
            wrote last edited by TLeM4
            #9

            Hi @nebulon ,
            Thanks for investigation, but I'm sorry i don't think it's the explanation.
            On friday we were able to reproduce the behavior just by going to the "/.well-known/openid-configuration" from our browsers but also from the server itself with wget, excluding any external network issue.
            Your troubleshooting report tool also report same issue with some other path, the openid path is only the best one to see the issue.
            The explanation of occasional timeouts is probably because the server has not many users and many apps do not require re-login or other path that has issue.

            Finally, even if heavy load is the explanation, we do not change our habits, so were does it come from ? How to avoid that ? All the server load statistics are very good, and i made some test few minutes ago the url just always timeout even locally with wget.

            edit: # wget http://127.0.0.1/ is timeouting too

            1 Reply Last reply
            1
            • jamesJ james referenced this topic
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote last edited by
              #10

              @tlem4 I am able to reproduce it. Making a fix .

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

                Fixed in https://git.cloudron.io/platform/box/-/commit/8251b4d0c7af80d93f637820d4828ad58c9ff173

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

                  @tlem4 you can patch src/nginxconfig.ejs alone and that should be enough. systemctl restart box will regenerate the actual nginx configs and it will work now. Thanks for reporting!

                  1 Reply Last reply
                  0
                  • girishG girish has marked this topic as solved
                  • T TLeM4 has marked this topic as solved
                  • T Offline
                    T Offline
                    TLeM4
                    wrote last edited by
                    #13

                    Hi @girish
                    Thanks for the fix, /.well-known/openid-configuration is now working well.

                    However, troubleshooting tool still report some random issue (ran 4 times, worked only the first time):

                    # cloudron-support --troubleshoot
                    Vendor: netcup Product: KVM Server
                    Linux: 6.8.0-110-generic
                    Ubuntu: noble 24.04
                    Execution environment: kvm
                    Processor: AMD EPYC 9645 96-Core Processor
                    BIOS pc-i440fx-9.2  CPU @ 2.0GHz x 10
                    RAM: 24602244KB
                    Disk: /dev/vda3       789G
                    [OK]	node version is correct
                    [OK]	IPv6 is enabled and public IPv6 address is working
                    [OK]	docker is running
                    [OK]	docker version is correct
                    [OK]	MySQL is running
                    [OK]	netplan is good
                    [OK]	DNS is resolving via systemd-resolved
                    [OK]	unbound is running
                    [OK]	nginx is running
                    [OK]	dashboard cert is valid
                    [FAIL]	Could not load dashboard website with loopback check
                    
                    1 Reply Last reply
                    0
                    • girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote last edited by
                      #14

                      @tlem4 The dashboard issue is related to the latest ubuntu kernel having a regression. You are running 110 which has a bug . See https://forum.cloudron.io/topic/15265/unusable-application/39

                      1 Reply Last reply
                      1

                      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                      With your input, this post could be even better 💗

                      Register Login
                      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