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 Restore. Problem with Bunny DNS

Cloudron Restore. Problem with Bunny DNS

Scheduled Pinned Locked Moved Unsolved Support
bunny dnsrestore
6 Posts 3 Posters 795 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.
  • matix131997M Offline
    matix131997M Offline
    matix131997
    wrote on last edited by
    #1

    Hello I am reporting a problem with restoring a server from a backup. During the restore it is throwing an Bunny API error.

    Zrzut ekranu 2024-06-22 150034.png

    2024-06-22T13:00:16.775Z box:dns registerLocation: Get error. retryable: true. getaddrinfo EAI_AGAIN api.bunny.net
    2024-06-22T13:00:16.778Z box:provision restoreTask: error. BoxError: getaddrinfo EAI_AGAIN api.bunny.net at registerLocation (/home/yellowtent/box/src/dns.js:226:15) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /home/yellowtent/box/src/dns.js:264:13 at async promiseRetry (/home/yellowtent/box/src/process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /home/yellowtent/box/src/dns.js:264:13 at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20) at async Object.registerLocations (/home/yellowtent/box/src/dns.js:255:9) at async restoreTask (/home/yellowtent/box/src/provision.js:186:13) {reason: 'Network Error', details: {} }
    
    
    1 Reply Last reply
    1
    • matix131997M Offline
      matix131997M Offline
      matix131997
      wrote on last edited by matix131997
      #2

      This is a very strange situation... OVH firewall is to blame.....

      ovh.PNG

      Now I don't know how I'm supposed to set it up correctly myself 😕 So far in most of the hosting without a problem

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

        Cloudron configures the server side firewall already, so you might as well just disable the OVH one if possible or allow everything.

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

          @matix131997 It seems DNS lookup of api.bunny.net is failing on the server.

          Check if a) unbound is running under Services and b) Does host api.bunny.net work on the server ?

          1 Reply Last reply
          0
          • girishG girish marked this topic as a question on
          • matix131997M Offline
            matix131997M Offline
            matix131997
            wrote on last edited by
            #5

            I did another firewall test today. OVH's firewall is working strangely. I set the rule differently and it worked for an hour - there was limited access to SSH, and the rest worked. After an hour, everything stopped working.

            Why did I want to do this?
            Generally I wanted to restrict port 22 to a given IP address - VPN, having additional security with a key. I wanted to from the iptables level but I am aware that Cloudron manages and is hard to restrict.

            Well, unless you add an option e.g.: in the Network tab item to add IP addresses to ports 22 to iptables.

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

              Sorry, but I am not following how name resolution is dependent on port 22. Name resolution uses UDP port 52 and is completely different from SSH which is TCP port 22 .

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