Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: my.brownhanky.com
I ran this command:
It produced this output:
My web server is (include version): nginx open-resty 1.2
The operating system my web server runs on is (include version): Ubuntu 14.4
My hosting provider, if applicable, is: self
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): none
When I test and develop, I set change my local copy of /etc/hosts to point my domain to a different server.
Ever since we started using Let’s Encrypt, this strategy fails. I have to hammer my way through browser warnings.
I call this “staging” but it’s not clear to me you mean the same thing when you talk of staging.
How can I have a valid cert for a domain which really is in production but also for my own (live on the net) test/dev?
Thanks fro any advice…