Problems with none WWW and with WWW

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: beansincup.se

https://www.beansincup.se/ works fine but when you try to visit http://beansincup.se/ the certificate wont work. What is wrong? Do I need to add another certificate for beansincup.se/. I have several sites and I never hade any problems with this.

Thanks!

1 Like

If you go on httpS://beansincup.se it works.

You just have to add a redirect from http://beansincup.se to https://beansincup.se

3 Likes

There is a bit more to it.
The "www" works but the apex fails.
[there is no cert issued for the apex]

5 Likes

Yep. My browsers betrayed me. I don't know why they autoredirect that.

2 Likes

How can I find a solution for this? Should I add letsencrypt in root domain beansincup.se? Im using linode and easyengine

Yes, you need your cert to have both beansincup.se and www.beansincup.se

I don't know how you do that in EasyEngine. It looks like it should be setup by EE per their docs here. Maybe ask them if not sure.

One thing that may have prevented it from working is failure connecting to http://beansincup.se. That should be working before an HTTP challenge will work

curl -I beansincup.se

HTTP/1.1 503 Service Temporarily Unavailable
Server: nginx
Date: Wed, 23 Mar 2022 14:01:50 GMT
Content-Type: text/html
Content-Length: 206
Connection: keep-alive
3 Likes

When I try to add letsencrypt on just beansincup.se it says the website dont exists. "Could not find the site you wish to run site info command on."

How should I fix the "HTTP/1.1 503 Service Temporarily Unavailable"? I have never seen this problem before with letsencrypt and our setup.

1 Like

I think you should visit the EasyEngine forum. They are more familiar with how it works than we are.

Your domain beansincup.se exists and we can see it from the public internet with both http and https. I don't know why EE would say it does not exist.

Your '503 Service' error is when trying to connect using HTTP. It has nothing to do with your certs or Let's Encrypt.

4 Likes

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