Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved How to change domain from Wildcard to Gandi LiveDNS using Cloudron CLI?

    Support
    domains gandi
    3
    5
    272
    Loading More Posts
    • 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.
    • jdaviescoates
      jdaviescoates last edited by girish

      I've been a bit silly and moved my Dashboard Domain from one registrar to another without thinking about it properly and I now can't access my Dashboard.

      Is there was a way to change the domain from Wildcard to Gandi LiveDNS using Cloudron CLI?

      BTW, I just installed Cloudron CLI and got these warnings and errors:

      code_tjosef@josef-ThinkPad-T510:~$ sudo npm install -g cloudron
      [sudo] password for josef: 
      npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
      npm ERR! code EINTEGRITY
      npm ERR! sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w== integrity checksum failed when using sha512: wanted sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w== but got sha512-z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==. (0 bytes)
      npm WARN deprecated har-validator@5.1.5: this library is no longer supported
      /usr/local/bin/cloudron -> /usr/local/lib/node_modules/cloudron/bin/cloudron
      npm WARN notsup Unsupported engine for open@8.2.1: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"})
      npm WARN notsup Not compatible with your version of node/npm: open@8.2.1
      
      + cloudron@4.12.1
      added 12 packages from 10 contributors, removed 3 packages and updated 32 packages in 15.582s
      npm ERR! Callback called more than once.
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /root/.npm/_logs/2021-06-21T13_30_50_897Z-debug.log
      ext
      

      I use Cloudron with Gandi & Hetzner

      BrutalBirdie 1 Reply Last reply Reply Quote 0
      • BrutalBirdie
        BrutalBirdie Staff @jdaviescoates last edited by BrutalBirdie

        @jdaviescoates good question.

        My first initial thought was: "Can I do the initial DNS setup again in this case?"

        https://docs.cloudron.io/api.html#tag/Cloudron/paths/~1cloudron~1setup/post

        Maybe this can be done / fixed via the API?

        This solution is not user friendly tho and requires to have a API Key setup prior doing something wrong.


        curl -k -X POST -H 'Content-Type: application/json' --data '{"dnsConfig": {"provider":"gandi", "domain": "your.domain.tld", "config": "??? gandi specific config ???"}}' https://{HOST.NAME}/api/v1/cloudron/setup?access_token={$TOKEN}
        

        This is just what I hacked together without testing!

        Like my work? Consider donating a beer 🍻 Cheers!

        jdaviescoates 1 Reply Last reply Reply Quote 0
        • jdaviescoates
          jdaviescoates @BrutalBirdie last edited by

          @brutalbirdie thanks, in the end I was able to change it to Gandi LiveDNS within Gandi and then I edited my /etc/hosts/ to be albe to access my dashboard and then once in there edited the domain to change from Wildcard to Gandi LiveDNS and now I think I'm sorted 🙂

          I use Cloudron with Gandi & Hetzner

          BrutalBirdie 1 Reply Last reply Reply Quote 1
          • BrutalBirdie
            BrutalBirdie Staff @jdaviescoates last edited by

            @jdaviescoates That is also a solution 😄
            Good to read.

            Like my work? Consider donating a beer 🍻 Cheers!

            1 Reply Last reply Reply Quote 1
            • girish
              girish Staff last edited by

              The CLI has indeed no way to edit domains. What you did is the correct approach - make the dashboard available via the browser and then edit from the Domains view.

              (As for the CLI warnings, looks like we have to replace request module with superagent. Sigh, we actually used to use superagent before...)

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Powered by NodeBB