Hello community,
I need some help with my VPS running Ubuntu 24.04. I’ve installed Nextcloud with Apache and MariaDB. Everything works fine, but when I use Certbot (version 3.0.1) to enable HTTPS, I get the following error in Firefox: "The page isn’t redirecting properly." My VPS is fully updated. Does anyone have an idea how to help me? Thanks in advance!
Welcome to the Let's Encrypt Community.
You should have been presented with a template when you made your post. We need you to answer all of those questions so that we have the information required to assist you. If you don't know the answer to a question, please indicate that in your response.
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. crt.sh | 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:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
2 Likes
My domain is : cloud.firebleu.online
I ran the following command : `
sudo apt install snapd
sudo snap install core; sudo snap refresh core
sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot
sudo certbot --apache
My Web server is apache2 : Server version: Apache/2.4.58 (Ubuntu)
Server built: 2024-10-02T12:40:51
My OS : Ubuntu 24.04
My hosting provider : Contabo
Yes I can login to root in a shell
I'm using a control panel to manage my site : I don't think so
The version of my client is : version 3.0.1
Hi @Firebleu,
Using the online tool Let's Debug yields these results
https://letsdebug.net/cloud.firebleu.online/2304617
BadRedirect
Error
Sending an ACME HTTP validation request to cloud.firebleu.online results in an unacceptable redirect. This is most likely a misconfiguration of your web server or your web application.
Too many (10) redirects, last redirect was to: https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
Trace:
@0ms: Making a request to http://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test (using initial IP 2606:4700:3034::6815:b36)
@0ms: Dialing 2606:4700:3034::6815:b36
@97ms: Server response: HTTP 301 Moved Permanently
@97ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@98ms: Dialing 2606:4700:3034::6815:b36
@236ms: Server response: HTTP 301 Moved Permanently
@236ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@236ms: Dialing 2606:4700:3034::6815:b36
@381ms: Server response: HTTP 301 Moved Permanently
@381ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@381ms: Dialing 2606:4700:3034::6815:b36
@512ms: Server response: HTTP 301 Moved Permanently
@512ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@512ms: Dialing 2606:4700:3034::6815:b36
@652ms: Server response: HTTP 301 Moved Permanently
@652ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@652ms: Dialing 2606:4700:3034::6815:b36
@784ms: Server response: HTTP 301 Moved Permanently
@784ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@784ms: Dialing 2606:4700:3034::6815:b36
@945ms: Server response: HTTP 301 Moved Permanently
@945ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@946ms: Dialing 2606:4700:3034::6815:b36
@1086ms: Server response: HTTP 301 Moved Permanently
@1086ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@1087ms: Dialing 2606:4700:3034::6815:b36
@1235ms: Server response: HTTP 301 Moved Permanently
@1235ms: Received redirect to https://cloud.firebleu.online/.well-known/acme-challenge/letsdebug-test
@1235ms: Dialing 2606:4700:3034::6815:b36
@1561ms: Server response: HTTP 301 Moved Permanently
Looks like an infinite redirect loop.
Also this Cloudflare WARNING:
CloudflareCDN
Warning
The domain cloud.firebleu.online is being served through Cloudflare CDN. Any Let's Encrypt certificate installed on the origin server will only encrypt traffic between the server and Cloudflare. It is strongly recommended that the SSL option 'Full SSL (strict)' be enabled.
https://support.cloudflare.com/hc/en-us/articles/200170416-What-do-the-SSL-options-mean-
2 Likes
Please note that it does not help with any software configuration to re-issue a perfectly fine certificate. It will only increase load on the Let's Encrypt infrastructure and can lead to you hitting rate limits.
Please show the output of the command:
sudo apachectl -t -D DUMP_VHOSTS
1 Like
Ok so I just set to full and now I can reach my website ! Tkanks !
2 Likes
You are welcome @Firebleu! 
Have a pleasant day! 
2 Likes
You shouldn't use Full as it opens you up to additional attack vectors. You will want to use Full (strict) so that your origin certificate is validated by Cloudflare.
4 Likes
Thanks !
4 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.