moving a domain between servers #485

New Issue

adam · 2025-12-29T01:26:02+01:00

adam commented

2025-12-29 01:26:02 +01:00

Originally created by @ghost on GitHub (Jul 26, 2020).

I'm using dehydrated on two servers. I would like to move a domain hosted from server A, to server B. From the documentation, its not clear if its enough to just move the 'certs/domain' and 'archive/domain' directories along with the domains.txt entry. The two servers use different let's encrypt accounts.

Could you please add some notes about moving domains or a general note about the portability of dehydrated controlled domains.

Thank you.

Originally created by @ghost on GitHub (Jul 26, 2020). I'm using dehydrated on two servers. I would like to move a domain hosted from server A, to server B. From the documentation, its not clear if its enough to just move the 'certs/domain' and 'archive/domain' directories along with the domains.txt entry. The two servers use different let's encrypt accounts. Could you please add some notes about moving domains or a general note about the portability of dehydrated controlled domains. Thank you.

adam closed this issue

2025-12-29 01:26:02 +01:00

adam commented

2025-12-29 01:26:03 +01:00

@lukas2511 commented on GitHub (Jul 26, 2020):

You just copy your configuration, entries from domains.txt and the parts of the certs subdirectory you want to move, that's all. I don't understand what the problem is. Dehydrated doesn't "manage" any domains, it just queries ACME APIs for certificates and provides required validation tokens.

@lukas2511 commented on GitHub (Jul 26, 2020): You just copy your configuration, entries from domains.txt and the parts of the certs subdirectory you want to move, that's all. I don't understand what the problem is. Dehydrated doesn't "manage" any domains, it just queries ACME APIs for certificates and provides required validation tokens.

adam commented

2025-12-29 01:26:03 +01:00

@txr13 commented on GitHub (Jul 26, 2020):

Further to what @lukas2511 said...

Dehydrated does not “control” domains, even for the purposes of issuing certificates. You mentioned that the two servers use different LE accounts, which makes me think you may be under the impression that dehydrated sort of “ties” domains to LE accounts. That doesn’t happen with LE certificate issuance—any LE account can request any certificate for any domain at any time. Therefore there is no need for any “migration” process—copying the relevant configuration (and optionally any existing certificates) is sufficient.

@txr13 commented on GitHub (Jul 26, 2020): Further to what @lukas2511 said... Dehydrated does not “control” domains, even for the purposes of issuing certificates. You mentioned that the two servers use different LE accounts, which makes me think you may be under the impression that dehydrated sort of “ties” domains to LE accounts. That doesn’t happen with LE certificate issuance—any LE account can request any certificate for any domain at any time. Therefore there is no need for any “migration” process—copying the relevant configuration (and optionally any existing certificates) is sufficient.

adam commented

2025-12-29 01:26:04 +01:00

@ghost commented on GitHub (Jul 26, 2020):

Maybe "control" was not the right word to use.

Thank you @txr13, you answered my question in full.

@ghost commented on GitHub (Jul 26, 2020): Maybe "control" was not the right word to use. Thank you @txr13, you answered my question in full.

adam referenced this issue

2025-12-29 01:29:39 +01:00

[PR #485] [CLOSED] fixed "sed: invalid option -- 'E'" #850

Sign in to join this conversation.