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. Setup Error - "queryNs ETIMEOUT"

Setup Error - "queryNs ETIMEOUT"

Scheduled Pinned Locked Moved Solved Support
installationdomains
24 Posts 6 Posters 1.9k Views 6 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.
  • nebulonN Offline
    nebulonN Offline
    nebulon
    Staff
    wrote on last edited by
    #14

    that seems to start then. So systemctl restart unbound still fails? If so not sure what the issue is then, we just install unbound from Ubuntu, this is not specific to Cloudron then unless you have changed the unbound configs maybe.

    You may also try, just to be sure to reinstall unbound and depending on ubuntu version also unbound-anchor:

    apt reinstall  unbound unbound-anchor
    
    1 Reply Last reply
    0
    • K Offline
      K Offline
      kk_cloudron
      wrote on last edited by
      #15

      Hello Nebulon,
      yes, the restart still fails. When I run the reinstall command, a message appears that two new packages are being installed: libunbound8 and unbound-anchor.
      So could this be the problem?

      If I have changed any configurations, I don't know how, because normally I don't access the server via ssh, but let cloudron manage everything. I only use ssh for disk adjustments or specific instructions from the Cloudron interface. 🤷 😌

      However. I have started the reinstallation and will wait and see. It is currently taking a while (approx. 5 minutes). The latest message is Setting up unbound (1.19.2-1ubuntu3.3) ...

      Thanks for the inputs so far !

      1 Reply Last reply
      0
      • K Offline
        K Offline
        kk_cloudron
        wrote on last edited by
        #16
        This post is deleted!
        1 Reply Last reply
        0
        • K Offline
          K Offline
          kk_cloudron
          wrote on last edited by
          #17

          Solved! Thanks a lot! (re)installation works.

          Do I have to pay attention to any follow-up measures? Or can I leave the administration to Cloudron again?

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

            Great. No further things should be required. Maybe some ubuntu dist-upgrade in the past didn't go as planned and something messed with the unbound installation. But glad it got solved.

            1 Reply Last reply
            0
            • potemkin_aiP Offline
              potemkin_aiP Offline
              potemkin_ai
              wrote on last edited by
              #19

              Got the same problem on vanilla Ubuntu 24.04, reinstall didn't help.
              status give all green, host command fails though:

              # host -t NS apple.com 127.0.0.150
              ;; communications error to 127.0.0.150#53: timed out
              Using domain server:
              Name: 127.0.0.150
              Address: 127.0.0.150#53
              Aliases:
              
              Host apple.com not found: 2(SERVFAIL)
              
              1 Reply Last reply
              0
              • J Offline
                J Offline
                joseph
                Staff
                wrote on last edited by joseph
                #20

                Have you tried with just vanilla Ubuntu 24.04 and without Cloudron? I suspect the problem is something network related since this works on all the VPS providers. Besides Cloudron configuration is just apt install unbound-server and the config file - https://git.cloudron.io/platform/box/-/tree/master/setup/start/unbound?ref_type=heads . Nothing else is done.

                potemkin_aiP 1 Reply Last reply
                0
                • J joseph

                  Have you tried with just vanilla Ubuntu 24.04 and without Cloudron? I suspect the problem is something network related since this works on all the VPS providers. Besides Cloudron configuration is just apt install unbound-server and the config file - https://git.cloudron.io/platform/box/-/tree/master/setup/start/unbound?ref_type=heads . Nothing else is done.

                  potemkin_aiP Offline
                  potemkin_aiP Offline
                  potemkin_ai
                  wrote on last edited by
                  #21

                  @joseph I can't uninstall cloudron, but plain host apple.com works perfectly fine!

                  1 Reply Last reply
                  0
                  • potemkin_aiP Offline
                    potemkin_aiP Offline
                    potemkin_ai
                    wrote on last edited by
                    #22

                    [4776:0] error: udp connect failed: Network is unreachable for 2001:500:2::c port 53 (len 28)
                    guess that's a reasonable error for the case when IPv6 is disabled?

                    do-ip6: no in config doesn't help thought...

                    1 Reply Last reply
                    0
                    • potemkin_aiP Offline
                      potemkin_aiP Offline
                      potemkin_ai
                      wrote on last edited by
                      #23

                      That is quite embarrassing... I am blocked at the setup process of fresh cloudron on a fresh ubuntu for a few hours...

                      And that is all due to # Unbound is used primarily for RBL queries (host 2.0.0.127.zen.spamhaus.org) - which is not quite true / right anymore as well?

                      1 Reply Last reply
                      0
                      • potemkin_aiP potemkin_ai referenced this topic on
                      • potemkin_aiP potemkin_ai referenced this topic on
                      • GengarG Offline
                        GengarG Offline
                        Gengar
                        wrote on last edited by Gengar
                        #24

                        @potemkin_ai & @kk_cloudron

                        On my side I was also having the issue "queryNs ETIMEOUT" , and it was because my outbound UDP port 53 was not open.

                        I just had to add it like that on my Hetzner Cloud Firewall :

                        image.png

                        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