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. Bug in adding new domain

Bug in adding new domain

Scheduled Pinned Locked Moved Solved Support
domainswildcard
19 Posts 4 Posters 2.5k Views 4 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.
    • potemkin_aiP Offline
      potemkin_aiP Offline
      potemkin_ai
      wrote on last edited by girish
      #1

      I'm getting

      Configuration error: Domain resolves to ["177.21.86.255"] instead of IPv4 177.21.86.255
      

      When adding a new domain via wildcard.

      Seems like a bug in converting JSON to the numeric value?

      potemkin_aiP girishG 2 Replies Last reply
      0
      • potemkin_aiP potemkin_ai

        I'm getting

        Configuration error: Domain resolves to ["177.21.86.255"] instead of IPv4 177.21.86.255
        

        When adding a new domain via wildcard.

        Seems like a bug in converting JSON to the numeric value?

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

        @potemkin_ai in the log files, after I tried DNS reconfiguration:

        isChangeSynced: app.subdomain.mydomain.com (A) was resolved to 177.21.86.255 at NS ns3207.hexonet.net (177.21.86.255). Expecting 177.21.86.255. Match false
        Jun 17 19:48:12 box:dns/waitfordns waitForDns: app.subdomain.mydomain.com at ns ns3207.hexonet.net: not done
        

        IP address & domain name are changed.

        v7.2.4 (Ubuntu 18.04.5 LTS)

        It looks like DNS is quite broken in this release?

        potemkin_aiP 1 Reply Last reply
        0
        • potemkin_aiP potemkin_ai

          @potemkin_ai in the log files, after I tried DNS reconfiguration:

          isChangeSynced: app.subdomain.mydomain.com (A) was resolved to 177.21.86.255 at NS ns3207.hexonet.net (177.21.86.255). Expecting 177.21.86.255. Match false
          Jun 17 19:48:12 box:dns/waitfordns waitForDns: app.subdomain.mydomain.com at ns ns3207.hexonet.net: not done
          

          IP address & domain name are changed.

          v7.2.4 (Ubuntu 18.04.5 LTS)

          It looks like DNS is quite broken in this release?

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

          @potemkin_ai blocked here; app reconfiguration lead to an infinite

          Configuring - Waiting for DNS propagation
          
          1 Reply Last reply
          0
          • nebulonN nebulon marked this topic as a question on
          • potemkin_aiP Offline
            potemkin_aiP Offline
            potemkin_ai
            wrote on last edited by
            #4

            @nebulon , thanks for checking this thread, but it looks more like a bug to me, not a question, or am I missing something?

            jdaviescoatesJ girishG 2 Replies Last reply
            0
            • potemkin_aiP potemkin_ai

              @nebulon , thanks for checking this thread, but it looks more like a bug to me, not a question, or am I missing something?

              jdaviescoatesJ Offline
              jdaviescoatesJ Offline
              jdaviescoates
              wrote on last edited by
              #5

              @potemkin_ai said in Bug in adding new domain:

              it looks more like a bug to me, not a question, or am I missing something?

              I think they mark them as a question just so they get the 'unsolved' badge and as a way to keep track of issues that need solving (and so they can be marked as 'solved' once the problem has been sorted).

              I use Cloudron with Gandi & Hetzner

              potemkin_aiP 1 Reply Last reply
              1
              • jdaviescoatesJ jdaviescoates

                @potemkin_ai said in Bug in adding new domain:

                it looks more like a bug to me, not a question, or am I missing something?

                I think they mark them as a question just so they get the 'unsolved' badge and as a way to keep track of issues that need solving (and so they can be marked as 'solved' once the problem has been sorted).

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

                @jdaviescoates thank you, I hope so!

                1 Reply Last reply
                0
                • potemkin_aiP potemkin_ai

                  I'm getting

                  Configuration error: Domain resolves to ["177.21.86.255"] instead of IPv4 177.21.86.255
                  

                  When adding a new domain via wildcard.

                  Seems like a bug in converting JSON to the numeric value?

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

                  @potemkin_ai I tried this now and it works fine for my test subdomain atleast.

                  000b2855-a864-48d5-ba4a-9f5f187b94b3-image.png

                  Configuration error: Domain resolves to ["177.21.86.255"] instead of IPv4 177.21.86.255

                  Curiously, this log is actually saying that the setup is correct but somehow still fails. The first value is a json of length 1.

                  1 Reply Last reply
                  0
                  • potemkin_aiP potemkin_ai

                    @nebulon , thanks for checking this thread, but it looks more like a bug to me, not a question, or am I missing something?

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

                    @potemkin_ai Can you please try host cloudrontestdns.yourdomain.com 127.0.0.1 on your machine?

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

                      I feel I am missing something obvious here. The code in question is:

                      const ipv4 = await sysinfo.getServerIPv4();
                      if (ipv4Result.length !== 1 || ipv4 !== ipv4Result[0]) throw new BoxError(BoxError.EXTERNAL_ERROR, `Domain resolves to ${JSON.stringify(ipv4Result)} instead of IPv4 ${ipv4}`);
                      

                      Per the logs atleast , 177.21.86.255 is the server IP and the DNS resolved to [ "177.21.86.255" ]. Not seeing why the check fails....

                      potemkin_aiP 1 Reply Last reply
                      0
                      • girishG girish

                        @potemkin_ai Can you please try host cloudrontestdns.yourdomain.com 127.0.0.1 on your machine?

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

                        @girish sure:

                        host cloudrontestdns.tst.mydomain.com 127.0.0.1
                        Using domain server:
                        Name: 127.0.0.1
                        Address: 127.0.0.1#53
                        Aliases: 
                        
                        cloudrontestdns.tst.mydomain.com has address 177.21.86.255
                        
                        1 Reply Last reply
                        0
                        • girishG girish

                          I feel I am missing something obvious here. The code in question is:

                          const ipv4 = await sysinfo.getServerIPv4();
                          if (ipv4Result.length !== 1 || ipv4 !== ipv4Result[0]) throw new BoxError(BoxError.EXTERNAL_ERROR, `Domain resolves to ${JSON.stringify(ipv4Result)} instead of IPv4 ${ipv4}`);
                          

                          Per the logs atleast , 177.21.86.255 is the server IP and the DNS resolved to [ "177.21.86.255" ]. Not seeing why the check fails....

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

                          @girish I'm not very good in negative logic, as it's usually quite a resource intensive task for my brains, so I would just rewrite it to something more 'positive' 🙂

                          if (ipv4Result.length == 1 && ipv4 !== ipv4Result[0]) {do some logic};
                          else throw new BoxError(BoxError.EXTERNAL_ERROR, `Domain resolves to ${JSON.stringify(ipv4Result)} instead of IPv4 ${ipv4}`);
                          

                          But the error message confuses me as well, as it's says that two similar things are not similar; my only idea is some weird data conversion coming from a weak JS data typing?

                          girishG nebulonN 2 Replies Last reply
                          0
                          • potemkin_aiP potemkin_ai

                            @girish I'm not very good in negative logic, as it's usually quite a resource intensive task for my brains, so I would just rewrite it to something more 'positive' 🙂

                            if (ipv4Result.length == 1 && ipv4 !== ipv4Result[0]) {do some logic};
                            else throw new BoxError(BoxError.EXTERNAL_ERROR, `Domain resolves to ${JSON.stringify(ipv4Result)} instead of IPv4 ${ipv4}`);
                            

                            But the error message confuses me as well, as it's says that two similar things are not similar; my only idea is some weird data conversion coming from a weak JS data typing?

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

                            @potemkin_ai Do you think you can send me your real domain name to support@cloudron.io ? Let me test with my local unbound as to what is happening.

                            1 Reply Last reply
                            0
                            • potemkin_aiP potemkin_ai

                              @girish I'm not very good in negative logic, as it's usually quite a resource intensive task for my brains, so I would just rewrite it to something more 'positive' 🙂

                              if (ipv4Result.length == 1 && ipv4 !== ipv4Result[0]) {do some logic};
                              else throw new BoxError(BoxError.EXTERNAL_ERROR, `Domain resolves to ${JSON.stringify(ipv4Result)} instead of IPv4 ${ipv4}`);
                              

                              But the error message confuses me as well, as it's says that two similar things are not similar; my only idea is some weird data conversion coming from a weak JS data typing?

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

                              @potemkin_ai is it possible that the ipv4Result delivers more than one result in your case? As @girish it might be helpful to expose your real domain in question to us by sending to support@cloudron.io

                              Or you can put some console.log() traces in that code section if you want to debug this on your own a bit.

                              girishG 1 Reply Last reply
                              0
                              • nebulonN nebulon

                                @potemkin_ai is it possible that the ipv4Result delivers more than one result in your case? As @girish it might be helpful to expose your real domain in question to us by sending to support@cloudron.io

                                Or you can put some console.log() traces in that code section if you want to debug this on your own a bit.

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

                                @nebulon User contacted us on support but the error message on support is quite different from the one that is reported here.

                                potemkin_aiP 1 Reply Last reply
                                1
                                • girishG girish

                                  @nebulon User contacted us on support but the error message on support is quite different from the one that is reported here.

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

                                  thank you, @girish , @nebulon , it was indeed an issue on my side - the problem was caused by an automatic IP address detection confusion and the numbers were quite close, so I didn't notice that, indeed.

                                  As a feature request, probably, it might make sense to add to the error message an offer to check an IP address auto-detection in Network settings, for the future-me-s?

                                  girishG 1 Reply Last reply
                                  0
                                  • potemkin_aiP potemkin_ai

                                    thank you, @girish , @nebulon , it was indeed an issue on my side - the problem was caused by an automatic IP address detection confusion and the numbers were quite close, so I didn't notice that, indeed.

                                    As a feature request, probably, it might make sense to add to the error message an offer to check an IP address auto-detection in Network settings, for the future-me-s?

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

                                    @potemkin_ai I replied to you on support, I think what you want is https://docs.cloudron.io/networking/#ipv4 . The static or network interface configuration, if I understood your setup correctly. Whatever IP you provide here is what will be used to configure and test the DNS.

                                    potemkin_aiP 1 Reply Last reply
                                    0
                                    • girishG girish

                                      @potemkin_ai I replied to you on support, I think what you want is https://docs.cloudron.io/networking/#ipv4 . The static or network interface configuration, if I understood your setup correctly. Whatever IP you provide here is what will be used to configure and test the DNS.

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

                                      @girish I fixed the problem - indeed with static IP; what I'm saying, it's that it might be worth to mention a possible reason in the error message of the IPs mismatch, offering person to go and check if his IP address was auto-detected correctly.

                                      Does it makes sense?

                                      girishG 1 Reply Last reply
                                      1
                                      • potemkin_aiP potemkin_ai

                                        @girish I fixed the problem - indeed with static IP; what I'm saying, it's that it might be worth to mention a possible reason in the error message of the IPs mismatch, offering person to go and check if his IP address was auto-detected correctly.

                                        Does it makes sense?

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

                                        @potemkin_ai Ah got it, I think it would have helped if it said "IP xxx in DNS does not match auto-detected IP yyy". I have created an internal task for that.

                                        potemkin_aiP 1 Reply Last reply
                                        2
                                        • girishG girish has marked this topic as solved on
                                        • girishG girish

                                          @potemkin_ai Ah got it, I think it would have helped if it said "IP xxx in DNS does not match auto-detected IP yyy". I have created an internal task for that.

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

                                          @girish thank you! And thank you again for your prompt help!

                                          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