Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved DO DNS Issue: TTL must be > 30

    Support
    domains digitalocean
    3
    7
    389
    Loading More Posts
    • 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.
    • girish
      girish Staff last edited by girish

      We have had several reports about DO DNS integration not working. It seems they changed the API all of a sudden to have a min value of 30.

      To fix this issue temporarily: Change the DNS provider to manual. We are making a 4.1.4 release with the fix. 4.1.4 is now released.

      1 Reply Last reply Reply Quote 1
      • d19dotca
        d19dotca last edited by d19dotca

        Just came to look into this, was bad timing as I was just in the middle of changing from wildcard to DigitalOcean in the dropdown menu and then ran into this issue you mentioned about the record TTL being greater than 30. Had just bough the $30 Cloudron subscription too. Hoping for a quick fix. 🙂

        --
        Dustin Dauncey
        www.d19.ca

        1 Reply Last reply Reply Quote 0
        • girish
          girish Staff last edited by

          @dustinddotca An alternate fix is:

          1. edit /home/yellowtent/box/src/dns/digitalocean.js and change the line "ttl: 1" (around line 114) to "ttl: 30"
          2. systemctl restart box

          Then you can use the DO DNS provider.

          1 Reply Last reply Reply Quote 1
          • d19dotca
            d19dotca last edited by

            Oh perfect, that's a good workaround. Thank you for the quick fix! Hopefully that won't interfere with anything when 4.1.4 is released. 🙂 But if not, it's an easy fix again. I appreciate the help.

            --
            Dustin Dauncey
            www.d19.ca

            1 Reply Last reply Reply Quote 0
            • girish
              girish Staff last edited by

              We already pushed out 4.1.4 with the same fix as above but it might take a week to get released to all. Thanks 🙂

              1 Reply Last reply Reply Quote 0
              • murgero
                murgero App Dev last edited by

                Change log in 4.1.4 (according to the Admin UI) does NOT reflect this change btw.

                --
                https://urgero.org
                ~ Professional Nerd. Freelance Programmer. ~
                Matrix: @murgero:urgero.org

                1 Reply Last reply Reply Quote 0
                • girish
                  girish Staff last edited by

                  Indeed, missed that. Just making a blog post for 4.1 release which will include it.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Powered by NodeBB