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. Can't change expired domain name of an app

Can't change expired domain name of an app

Scheduled Pinned Locked Moved Solved Support
9 Posts 2 Posters 1.6k Views 2 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.
  • C Offline
    C Offline
    ctrl
    wrote on last edited by ctrl
    #1

    Hey all,

    I used to use a domain which expired but is still listed in the domain configuration section and is in use by an app. Currently the app does not start for obvious reasons. Also I'm not able to change the domain name of that app. At least it is not possible from the GUI.

    Which steps would you propose to migrate an app to a a new domain name in a scenario as described above?

    Cheers

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

      First change the DNS provider of that domain in the Cloudron dashboard to no-op and then you should be able to change the domain of that app again.

      C 1 Reply Last reply
      0
      • nebulonN nebulon

        First change the DNS provider of that domain in the Cloudron dashboard to no-op and then you should be able to change the domain of that app again.

        C Offline
        C Offline
        ctrl
        wrote on last edited by ctrl
        #3

        Thanks a lot for your quick reply. I tried just that, but the button to save the changes in the app config is still greyed out.

        nebulonN 1 Reply Last reply
        0
        • C ctrl

          Thanks a lot for your quick reply. I tried just that, but the button to save the changes in the app config is still greyed out.

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

          @ctrl are you referring to the location/domain change form and the save button there? Can you try to change the subdomain part as well just to see if you hit some form state/validation issue?

          C 1 Reply Last reply
          0
          • nebulonN nebulon

            @ctrl are you referring to the location/domain change form and the save button there? Can you try to change the subdomain part as well just to see if you hit some form state/validation issue?

            C Offline
            C Offline
            ctrl
            wrote on last edited by
            #5

            @nebulon Yes, I'm talking about the location form. Neither changing the subdomain field nor selecting another valid TLD from the dropdown allows me to save a new location.

            I just checked the form on another app. It works as long as an app is tied to a valid domain.

            nebulonN 1 Reply Last reply
            0
            • C ctrl

              @nebulon Yes, I'm talking about the location form. Neither changing the subdomain field nor selecting another valid TLD from the dropdown allows me to save a new location.

              I just checked the form on another app. It works as long as an app is tied to a valid domain.

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

              @ctrl looks like a bug. Would it be possible for you to allow us to take a direct look by enabling remote SSH support for us and send us a mail to support@cloudron.io with your dashboard domain?

              C 1 Reply Last reply
              0
              • nebulonN nebulon

                @ctrl looks like a bug. Would it be possible for you to allow us to take a direct look by enabling remote SSH support for us and send us a mail to support@cloudron.io with your dashboard domain?

                C Offline
                C Offline
                ctrl
                wrote on last edited by ctrl
                #7

                @nebulon Sure, I just created a ticket with a reference to this thread.

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

                  To update here, the root case was that nginx was not succeeding to reload, since that old domain had for some reason a custom wildcard certificate configured. That certificate didn't exist anymore on the disk as such so nginx would refuse to reload. That in turn aborted the apptask to change the location before it changes the location, so kind of a deadlock situation there, since Letsencrypt could also not be used, because that domain was not pointing to that Cloudron anymore.

                  I have fixed it now by clearing the error marker for that app in the database and change the location directly. Will have to see how we can possibly have a better workaround in the future for such edge cases.

                  C 1 Reply Last reply
                  1
                  • nebulonN nebulon

                    To update here, the root case was that nginx was not succeeding to reload, since that old domain had for some reason a custom wildcard certificate configured. That certificate didn't exist anymore on the disk as such so nginx would refuse to reload. That in turn aborted the apptask to change the location before it changes the location, so kind of a deadlock situation there, since Letsencrypt could also not be used, because that domain was not pointing to that Cloudron anymore.

                    I have fixed it now by clearing the error marker for that app in the database and change the location directly. Will have to see how we can possibly have a better workaround in the future for such edge cases.

                    C Offline
                    C Offline
                    ctrl
                    wrote on last edited by
                    #9

                    @nebulon Thanks a lot for your quick support. It works now.

                    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