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. Cloudron account seems not to be connected correctly

Cloudron account seems not to be connected correctly

Scheduled Pinned Locked Moved Solved Support
cloudflare
9 Posts 3 Posters 1.3k Views 4 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.
  • O Offline
    O Offline
    opensourced
    wrote on last edited by girish
    #1

    I have this issue now on at least 2 Cloudron instances that were working correctly for a long time.

    Now, when I want to install a new app from the store, It asks me for the Cloudron login. When provided, this request results in a timeout. However when i check in the settings, I see the correctly linked account. Also on the Cloudron-console, everything looks correct. How can i fix that?

    Thanks!

    1 Reply Last reply
    0
    • necrevistonnezrN Offline
      necrevistonnezrN Offline
      necrevistonnezr
      wrote on last edited by necrevistonnezr
      #2

      Check: Browser? Adblocker? DNS-Filter?

      1 Reply Last reply
      0
      • O Offline
        O Offline
        opensourced
        wrote on last edited by
        #3

        None of those seem to be the issue...
        Its the POST request to https://my.instance.com/api/v1/appstore/register_cloudron that results in a 424:

        status "Failed Dependency"
        message "Timeout of 30000ms exceeded"

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

          We saw this yesterday when Cloudflare DNS was used on one of @BrutalBirdie 's instances. Are you using Cloudflare DNS?

          1 Reply Last reply
          2
          • girishG girish marked this topic as a question on
          • O Offline
            O Offline
            opensourced
            wrote on last edited by
            #5

            yes i do.. this is likely the same issue then..

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

              The issue was that Clouflare API was down, I think it is working again though by now. At least https://www.cloudflarestatus.com/ does not report the issue anymore. Does it work by now?

              1 Reply Last reply
              0
              • O Offline
                O Offline
                opensourced
                wrote on last edited by
                #7

                I actually still have this issue. The instance is also not able to renew the certs, however on the vm DNS resolution seems to work correctly. There is a support ticket via Email open. Once I solve it, I can give a update here.

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

                  Wasn't the initial issue related to installing apps and not renewing certs? Maybe this is a different issue then.

                  1 Reply Last reply
                  0
                  • O Offline
                    O Offline
                    opensourced
                    wrote on last edited by
                    #9

                    Hi, I just wanted to follow up on this. We found the relating issue in this case which resulted in several different problems. In that case, it was bug in a firmware update on a firewall and not related to Cloudron and can be marked as resolved. Thank you anyway for your help.

                    1 Reply Last reply
                    1
                    • nebulonN nebulon 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