How can we test without using our production domain name?


#1

I was testing my server setup by using an xip.io domain, and it was working, but eventually the let’s encrypt client complained that I’d made too many requests for xip.io.

Then I tried to test using my AWS Public DNS, but let’s encrypt forbids AWS domain names.

So bloody hell, how am I supposed to test my whole server setup with let’s encrypt without taking down my production server so I can use my production domain name?


#2

Nevermind, I found the info about using the staging environment: https://letsencrypt.org/docs/staging-environment/

Might be good to put this link in the various certbot quickstart docs like https://certbot.eff.org/#ubuntutrusty-apache. Anyone who’s just getting started will probably need to know about the staging env at some point.


#3

without taking down my production server so I can use my production domain name?

aside from using Staging, you can also just proxy the /.well-known directory to letsencrypt running on another port. it’s not clear that one can do that, but it’s possible. another alternative is to use url redirects (acme will follow it)


#4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.