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. [Bug] Maxed out DNS Requests with no Backoff or Retries

[Bug] Maxed out DNS Requests with no Backoff or Retries

Scheduled Pinned Locked Moved Solved Support
dnsnamecheap
6 Posts 2 Posters 835 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.
  • T Offline
    T Offline
    thetomester13
    App Dev
    wrote on last edited by girish
    #1

    Hey Cloudron team!

    I just migrated my Cloudron to a new server and had some issues around updating DNS entries to the new IP address. Specifically I use Namecheap, but either way, from the logs below we can see there is logic that can probably be optimized. I have about 40 apps or so installed on my box, so if a DNS provider has any rate limiting on their API, it can cause issues when doing a complete DNS migration/update. See log below for what I was seeing:

    Jan 06 11:21:41box:dns registerLocation: Get error. retryable: true. Too many requests

    In this case, I would expect Cloudron to gracefully register this error (assuming we're getting a legitimate 429 status code from the DNS API), and retry with exponential backoffs until all queries are completed. Instead, this failed on all 3 of my domains since the first one has a lot of apps, and therefore DNS entries, to complete successfully.

    A few related thoughts:

    1. I love Cloudron! The migration as a whole was pretty smooth even given this DNS hiccup. I just went into my Namecheap dashboard and updated them all manually 🤷 not ideal, but not the end of the world. Besides that the upgrade process went without a hitch. Thanks for all that you do to help make it so!
    2. I was hoping to register this bug in your Cloudron Gitlab instance but I don't think I have permissions for that, even when I was logged in? I hope this is the right place to report this issue.
    3. The reason I moved servers is due to Cloudron 7.6.2 needing AVX support. I personally think that such a large dependency should have been introduced in a major version (ie 8.0.0) so that users like myself wouldn't be 'stranded' on a random version like 7.6.1 and not able to receive any updates at all (including on the apps, because of an issue reported in a separate thread on the forum here).
    1 Reply Last reply
    1
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @thetomester13 this is the right place to report bugs. GitLab is primarily used for development and we create issues there after verifying if reports are bugs.

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

        https://www.namecheap.com/support/knowledgebase/article.aspx/9739/63/api-faq/#z says "Our general API calls restriction is 50/min, 700/hour, and 8000/day across the whole key." . I guess we can slow down the namecheap request rate.

        1 Reply Last reply
        2
        • T Offline
          T Offline
          thetomester13
          App Dev
          wrote on last edited by
          #4

          Thanks @girish!

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

            I have fixed this for next release.

            1 Reply Last reply
            2
            • girishG girish marked this topic as a question on
            • girishG girish has marked this topic as solved on
            • T Offline
              T Offline
              thetomester13
              App Dev
              wrote on last edited by
              #6

              🙌

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