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: https://julianstaudt.de
I ran this command: certbot -d julianstaudt.de (renewed and replaced my existing certificate)
It produced this output: If I try to access the webpage it generates a ssl handshake error followed by some redirect errors
My web server is (include version): nginx/1.10.3
The operating system my web server runs on is (include version): Debian GNU/Linux (9)
My hosting provider, if applicable, is:
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): if you mean cloudflare by that, yes
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you’re using Certbot): certbot 0.28.0
So basically all this started happening after I installed my new router (https://store.ui.com/products/udm-pro). The thing is that I am still using my old one (Fritz!Box 7590) to provide the internet access. I’ve disabled all features on the Fritz!Box and added the UDM as an exposed host. And ofc I’ve created the port forward rules on the new router. I can access the website fine when using my wan ip, but once I do https://:443 I get a ‘PR_END_OF_FILE_ERROR’. Once I use the domain, cloudflare shows up the ssl handshake error page followed by a redirect caused by too many 301 redirects (idk what causes them too)
Any help is appreciated