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. Domain registry not working

Domain registry not working

Scheduled Pinned Locked Moved Solved Support
namecheapdomains
14 Posts 3 Posters 2.5k 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.
  • Z ZeZaung

    @girish Happy holidays!

    Good news for us here, at least hwen it comes to this particular domain. There was a rogue MX entry in our DNS configuration that was preventing cloudron from registering all the records through the API/Cloudron GUI.

    However, we are now facing a more dire situation which is based on self signed certificate on our dashboard. I will write a new support ticket request. We're worried.

    Z Offline
    Z Offline
    ZeZaung
    wrote on last edited by
    #4

    I take that back

    I'm troubleshooting an application once I got the domain registered with cloudron. I've since deleted the DNS records propogated by cloudron from within namecheap after uninstalling from cloudron via Domains GUI.

    However now when I try to reinstall the domain I get the same error as above. Why is it so difficult to get this going? What am I doing wrong here?

    Z 1 Reply Last reply
    0
    • Z ZeZaung

      I take that back

      I'm troubleshooting an application once I got the domain registered with cloudron. I've since deleted the DNS records propogated by cloudron from within namecheap after uninstalling from cloudron via Domains GUI.

      However now when I try to reinstall the domain I get the same error as above. Why is it so difficult to get this going? What am I doing wrong here?

      Z Offline
      Z Offline
      ZeZaung
      wrote on last edited by
      #5

      I should also add, we've tested with other domains under our control, and haven't had any issues getting DNS configuration automatically propogated with the Cloudron GUI

      nebulonN 1 Reply Last reply
      0
      • Z ZeZaung

        I should also add, we've tested with other domains under our control, and haven't had any issues getting DNS configuration automatically propogated with the Cloudron GUI

        nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #6

        @zezaung could be a bug in our code then. If you want us to take a direct look at the issue, please enable remote SSH support and send us a mail with your dashboard domain to support@cloudron.io

        Z 1 Reply Last reply
        0
        • nebulonN nebulon

          @zezaung could be a bug in our code then. If you want us to take a direct look at the issue, please enable remote SSH support and send us a mail with your dashboard domain to support@cloudron.io

          Z Offline
          Z Offline
          ZeZaung
          wrote on last edited by
          #7

          @nebulon

          Hi there

          The situation has evolved. I copied over the DNS records of another domain (one that works correctly) to the domain that doesn't work correctly, and then set up the domain through the GUI to bypass the errors seen in the screenshot in the OP.

          Now the domain works as intended, however not entirely: www.the-domain.org doesn't work, but the-domain.org works. The A record for @ and www are different from one another. I'm not sure what's misconfigured. What would be hte best way to troubleshoot that in particular? Remote SSH or namecheap itself?

          nebulonN 1 Reply Last reply
          0
          • Z ZeZaung

            @nebulon

            Hi there

            The situation has evolved. I copied over the DNS records of another domain (one that works correctly) to the domain that doesn't work correctly, and then set up the domain through the GUI to bypass the errors seen in the screenshot in the OP.

            Now the domain works as intended, however not entirely: www.the-domain.org doesn't work, but the-domain.org works. The A record for @ and www are different from one another. I'm not sure what's misconfigured. What would be hte best way to troubleshoot that in particular? Remote SSH or namecheap itself?

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #8

            @zezaung just to be clear, the www subdomain is not automatically managed by Cloudron, this has to be set explicitly as a subdomain of an app or an alias for an app. Only then Cloudron will setup the A record for it.

            Generally remote SSH should be good enough for us to evaluate and inspect the situation you are facing.

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

              @ZeZaung Did you get this sorted out?

              Z 1 Reply Last reply
              0
              • girishG girish

                @ZeZaung Did you get this sorted out?

                Z Offline
                Z Offline
                ZeZaung
                wrote on last edited by
                #10

                @girish Hi
                Thanks for checking in. No, we haven't. I explicitly went into namecheap's advanced DNS settings and added www manually, but to no avail.

                girishG 1 Reply Last reply
                0
                • Z ZeZaung

                  @girish Hi
                  Thanks for checking in. No, we haven't. I explicitly went into namecheap's advanced DNS settings and added www manually, but to no avail.

                  girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #11

                  @zezaung Do you think you can enable SSH and write to us at support@cloudron.io ? Also, is the issue now that namecheap is not working or that www subdomain not working or both?

                  Z 1 Reply Last reply
                  0
                  • girishG girish

                    @zezaung Do you think you can enable SSH and write to us at support@cloudron.io ? Also, is the issue now that namecheap is not working or that www subdomain not working or both?

                    Z Offline
                    Z Offline
                    ZeZaung
                    wrote on last edited by
                    #12

                    @girish It's www- not working on a particular application. I will write to support. namecheap overall does work, we're talking about a single domain

                    girishG 1 Reply Last reply
                    0
                    • Z ZeZaung

                      @girish It's www- not working on a particular application. I will write to support. namecheap overall does work, we're talking about a single domain

                      girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote on last edited by
                      #13

                      @zezaung ah ok, would love to debug that. One thing is that apart from adding www DNS entry, you also have to add it as a redirect in Cloudron UI - https://docs.cloudron.io/apps/#redirections

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

                        Adding a redirection made things work.

                        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