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. Hairpin NAT not working – could this be related to DNS changes I made for email delivery at my registrar?

Hairpin NAT not working – could this be related to DNS changes I made for email delivery at my registrar?

Scheduled Pinned Locked Moved Unsolved Support
6 Posts 3 Posters 229 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
      thoresson
      wrote on last edited by
      #1

      Hi!

      For a couple of hours now, both the Cloudron admin interface and the email services have been unavailable for me, but all apps seems to be running just fine.

      Just before this happened, I was trying to add some changes to the DNS for the same domain name as I use for my Cloudron to solve some mail delivery problems.

      When I ran

      cloudron-support --troubleshoot
      

      and got an error message about Hairpin NAT not working and that the admin domain could not be loaded.

      So I went into my registrars DNS configuration and removed the TXT entry I had added for my.<cloudron.domain>, even though I couldn't understand why that would have an impact on the admin interface or email services.

      But when I did, both admin interface and email became accessible again. Good. But I still get the Hairpin DNS error and FAIL for loading dashboard admin when troubleshooting from my servers terminal.

      Can someone explain what's going on here?

      1. How could SPF records have an impact on the services?
      2. And how could they become available again, yet cloudron-support claming there is a problem with Hairpin NAT?
      1 Reply Last reply
      1
      • humptydumptyH Offline
        humptydumptyH Offline
        humptydumpty
        wrote on last edited by humptydumpty
        #2

        Hairpinning is a feature in your router. I’m not sure if that’s a thing with a vps at a hosting provider.

        Go into your router and look for hairpin toggle.

        1 Reply Last reply
        1
        • J joseph marked this topic as a question on
        • T Offline
          T Offline
          thoresson
          wrote on last edited by
          #3

          Hmm. I understood the docs like it was a thing in the hosting firms routers. That makes it even more strange, since my router is the same before, during, and after I had this problem. 🙂

          humptydumptyH 2 Replies Last reply
          0
          • T thoresson

            Hmm. I understood the docs like it was a thing in the hosting firms routers. That makes it even more strange, since my router is the same before, during, and after I had this problem. 🙂

            humptydumptyH Offline
            humptydumptyH Offline
            humptydumpty
            wrote on last edited by
            #4

            @thoresson are you self hosting at home? If so, what router (brand/model) do you have?

            1 Reply Last reply
            1
            • T thoresson

              Hmm. I understood the docs like it was a thing in the hosting firms routers. That makes it even more strange, since my router is the same before, during, and after I had this problem. 🙂

              humptydumptyH Offline
              humptydumptyH Offline
              humptydumpty
              wrote on last edited by
              #5

              @thoresson also, have you opened up ports 80 and 443 in the router?

              You need to assign those ports to the server ip (both ipv4 and ipv6 if you have that).

              Then, activate dynamic dns in your cloudron dashboard to make sure it auto-updates when your ip changes.

              https://docs.cloudron.io/installation/home-server/

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

                Not sure which nameserver provider you are using, but I remember that back in the day it was possible to screw up the zonefile, rendering all DNS records broken. But generally try to put the TXT record back and then just try to resolve the dashboard domain using your nameserver explicitly (to avoid caching). This should work, if not, please contact your nameserver provider about that.

                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