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. Having trouble with setup and route53

Having trouble with setup and route53

Scheduled Pinned Locked Moved Unsolved Support
3 Posts 3 Posters 696 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.
    • T Offline
      T Offline
      tbroady
      wrote on last edited by
      #1

      I have a linux vps via lightsail, a domain, and DNS managed by route53. I set up an IAM user, got the keys, and went to do the cloudron setup, but it keeps telling me...

      "Domain nameservers are not set to Route53"

      but.... here they are.

      0_1537068995427_2018-09-15_23h35_46.png

      Am I doing something wrong?

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

        @tbroady That error occurs if your domain's nameservers do not match those in route53. Try this in on your PC/laptop:

        host -t NS <domain.com>

        The above should print the nameservers listed in route53. Is this the case? If so, can you run the above command in the Cloudron as well?

        You can also try running the above command after you do a systemctl restart unbound on the cloudron and see if that changes anything. Finally, if you see the logs of journalctl -fa -u box and then do the dns setup, it will give you a more detailed error on why the name servers are not matching.

        Thanks

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

          @tbroady do you have any update on this? Can we mark this as "solved"?

          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