# Switch to a differnt IP address / machine **URL:** \ **Category:** Help\ **Created:** [June 16, 2019, 9:14am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940 "2019-06-16T09:14:54Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![leolux](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/leolux/32/32489_2.png) [@leolux](https://community.letsencrypt.org/u/leolux)\ **Post date:** [June 16, 2019, 9:14am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940/1 "2019-06-16T09:14:54Z")
Is it possible to generate the certificate one machine and use it there for a while and to switch to a new machine with a different IP address later on (by changing the A-record for the domain name)? Can I just copy the config files of letsencrypt to the new machine? I ran this command: certbot certonly --webroot -w /var/www/example -d [example.com](http://example.com) ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [June 16, 2019, 9:16am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940/2 "2019-06-16T09:16:10Z")
Yes, the IP address used doesn’t matter to Let’s Encrypt. Just the hostname or hostnames. If those will be equal in the “new” situation, all should be fine. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [June 16, 2019, 9:21am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940/3 "2019-06-16T09:21:51Z")
Hi @leolux > [@leolux](#): > > Can I just copy the config files of letsencrypt to the new machine? I don't know. Have both machines exact the same setup? Same OS, same patches? There are symlinks you have to "copy". Normally, it's better to install a new Certbot, then create a new certificate. ---
**Author:** ![leolux](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/leolux/32/32489_2.png) [@leolux](https://community.letsencrypt.org/u/leolux)\ **Post date:** [June 16, 2019, 9:24am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940/4 "2019-06-16T09:24:49Z")
Almost 🙂 The machines are virtual machines which are generated automatically running the same operating system. But the specs are different. Some machines have more CPU power. ---
**Author:** ![leolux](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/leolux/32/32489_2.png) [@leolux](https://community.letsencrypt.org/u/leolux)\ **Post date:** [June 16, 2019, 9:28am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940/5 "2019-06-16T09:28:24Z")
Does the new certificate invalidate the “old” ceritifcate which already exists for the same domain? ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [June 16, 2019, 10:07am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940/6 "2019-06-16T10:07:03Z")
> [@leolux](#): > > Does the new certificate invalidate the “old” ceritifcate No. Created certificate are permanent and read-only. But don't revoke certificates if the private key is safe. And check rate limits. Perhaps read some basics: > **[How It Works - Let's Encrypt](https://letsencrypt.org/how-it-works/)** > > The objective of Let’s Encrypt and the ACME protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention. This is accomplished by running a certificate... and > **[Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)** > > Let’s Encrypt provides rate limits to ensure fair usage by as many people as possible. We believe these rate limits are high enough to work for most people by default. We’ve also designed them so renewing a certificate almost never hits a... ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [July 16, 2019, 10:07am UTC](https://community.letsencrypt.org/t/switch-to-a-differnt-ip-address-machine/95940/7 "2019-07-16T10:07:08Z")
Closed on July 16, 2019, 10:07am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.