Too many redirects: Setting up lets encrypted!


(Static Craft) #1

Hello,

I have successfully setup SSL on my website but the webpage will no longer load now and it carrys on redirecting from port 80 to 443, I do not know how to fix this. Can any of you come up with some sort of a solution or anything for me to fix this.

https://techuno.co.uk/

Thanks and I hope to hear back soon!
Steven


(Felix Freiberger) #2

When requesting GET https://techuno.co.uk/, your server replies with a redirect to Location: https://Techuno.co.uk/.

I find it strange that there is a capital T in the redirect. Is there any chance the domain in app.yml is Techuno.co.uk? If so, change it to techuno.co.uk and rebuild.


(Static Craft) #3

Well I did the Hostname as that, I am going to do that change, I’ll keep you up to date.


(Static Craft) #4

Well I have attempted this and have failed, I changed the name from Techuno.co.uk on the hostname in app.yml to techuno.co.uk, now I get this error

Skip register account key
[Sun Jan 8 13:50:13 UTC 2017] Single domain=‘techuno.co.uk
[Sun Jan 8 13:50:13 UTC 2017] Verify each domain
[Sun Jan 8 13:50:13 UTC 2017] Getting webroot for domain=‘techuno.co.uk
[Sun Jan 8 13:50:13 UTC 2017] Getting token for domain=‘techuno.co.uk
[Sun Jan 8 13:50:18 UTC 2017] techuno.co.uk is already verified, skip.
[Sun Jan 8 13:50:18 UTC 2017] techuno.co.uk is already verified, skip http-01.
[Sun Jan 8 13:50:18 UTC 2017] techuno.co.uk is already verified, skip http-01.
[Sun Jan 8 13:50:18 UTC 2017] Verify finished, start to sign.
[Sun Jan 8 13:50:23 UTC 2017] Sign failed: “detail”:"Error creating new cert :: Too many certificates already issued for exact set of domains: techuno.co.uk"
Error loading file ca.cer
139933278566040:error:02001002:system library:fopen:No such file or directory:bss_file.c:175:fopen(‘ca.cer’,‘r’)
139933278566040:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:178:
139933278566040:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:by_file.c:253:

Thanks
Steven


(Felix Freiberger) #5

Argh, not good. Let’s Encrypt won’t issue a new certificate for you because too many have been issued already within this week. :frowning:


(Static Craft) #6

Oh so would it be possible to change my VPS IP so then it would be like a new server?


(Felix Freiberger) #7

No, this keys on the domain.


(Static Craft) #8

Oh so I’ll have to wait a week then?


(Felix Freiberger) #9

Unluckily, I think the answer is yes.


(Static Craft) #10

Well thanks for all of your help you’ve been of great assistance I’ll get back to you in a week then :slight_smile:


(Static Craft) #11

Hey dude, just read this on let’s encrypt

We also have a Duplicate Certificate limit of 5 certificates per week. A certificate is considered a duplicate of an earlier certificate if they contain the exact same set of hostnames, ignoring capitalization and ordering of hostnames. For instance, if you requested a certificate for the names [www.example.com, example.com], you could request four more certificates for [www.example.com, example.com] during the week. If you changed the set of names by adding [blog.example.com], you would be able to request additional certificates.

Does this mean if I add www to the front of my website it will work or would it have to be some thing different.
Thanks
Steven


(Felix Freiberger) #12

I’m not quite sure how the rate limits currently work, this may be a good question for https://community.letsencrypt.org/ :slight_smile:


(Static Craft) #13

I’ll give it a try :slight_smile:


(Static Craft) #14

Wow it works, thanks for all of your help.