By Jeff Noel
Hey guys,
I’m just trying to figure out what are the remaining steps for a graceful transition between my old web host and my new droplet.
Here’s what I’ve done so far:
- Setup my droplet to target my subdomain (do.mydomain.com)
- Also used Certbot automatic setup at when I first launched the server to issue certificates for this subdomain.
- Copied my Wordpress DB and files.
- Updated config files and php.ini.
- Tested that everything works fine through
do.mydomain.com - Installed OLS plugin on the new Wordpress instance and setup everything
So that’s the base setup. Now I began the migration but after struggling with certbot, I had no choice to stop for today ( Error creating new order :: too many failed authorizations recently: ). I’d like for everything to go well tomorrow then I try again.
I seem to be lost when it comes to make sure my droplet is ready for the main domain name (leaving do.mydomain.com for just mydomain.com).
I never used certbot before this droplet. Never setup a web server beforehand to be honest. Moving from a CPanel installation that will stay alive on the other host just because it’s cheaper than a licence and my emails are using CPanel forwarding features.
So what I done so far (all on the droplet):
- Changed
homeandsiteurlin wp_options in the DB formydomain.cominstead ofdo.mydomain.com. - Added listeners for
www.mydomain.comandmydomain.comto my OLS admin panel (edited the ones already there fordo.mydomain.comand just added the two domain names above). - Edited my Domain Registrar A Record for
mydomain.comto point to my droplet IP’s address. - Ran
certbot certonly, specifying “Places files in webroot” (which is the same and only webroot as do.mydomain.com,/var/www/html/). Specified the domain name mydomain.com a few times, kept failing, so I specified the domain namesmydomain.com, do.mydomain.comand it gave me the “Expand certificate” option, which I selected. Finally got the “Too many failed authorizations” error which is where I’m at now.
For the time being I changed back my A Record for my main domain name back to my old web host since I’m having about 100 concurrent visitors all the time…
I really need the switch to be seamless and the certificate thing fixed. Any tips for tomorrow ? Anything I forget ? Thanks in advance for your help.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi,
You probably just hit the certbot rate limit due to frequent requests, please add --dry-run parameter when you are doing certbot test.
Here’s an no interactive example when you want to expand the domain.
certbot certonly --non-interactive --agree-tos -m supportexample.com --webroot -w /var/www/html/ -d example.com -d do.exmaple.com -d www.example.com --expand --dry-run
Once you see output like below, then you can run the certbot command again without --dry-run
IMPORTANT NOTES:
- The dry run was successful.
Remember to restart the web server to reload certificate.
service lsws restart
If challenge failed again, please share the output here.
Hope it helps.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.