Cloudflare is redirecting my website to https

0

Hi there,

I just setup a static jekyll website, hosted on Amazon S3, I have a number of them on there setup the same.

Anyway, the url is

http://www.djabstraction.com

For some reason this seems to work in a browser the first time, then when you restart the browser and attempt to go there again, Cloudflare starts sending back a redirect to https.

How do I stop this? I don't believe I've set anything up for this to happen.

I should add that the long amazon url still works as expected, it's just my domain name that's being redirected

http://www.djabstraction.com.s3-website-eu-west-1.amazonaws.com/

Nick.

preguntada hace 3 años453 visualizaciones
7 Respuestas
0

goldenmonkey wrote:
Hi there,

I just setup a static jekyll website, hosted on Amazon S3, I have a number of them on there setup the same.

Anyway, the url is

http://www.djabstraction.com

For some reason this seems to work in a browser the first time, then when you restart the browser and attempt to go there again, Cloudflare starts sending back a redirect to https.

How do I stop this? I don't believe I've set anything up for this to happen.

I should add that the long amazon url still works as expected, it's just my domain name that's being redirected

http://www.djabstraction.com.s3-website-eu-west-1.amazonaws.com/

Nick.
goldenmonkey wrote:
Hi there,

I just setup a static jekyll website, hosted on Amazon S3, I have a number of them on there setup the same.

Anyway, the url is

http://www.djabstraction.com

For some reason this seems to work in a browser the first time, then when you restart the browser and attempt to go there again, Cloudflare starts sending back a redirect to https.

How do I stop this? I don't believe I've set anything up for this to happen.

I should add that the long amazon url still works as expected, it's just my domain name that's being redirected

http://www.djabstraction.com.s3-website-eu-west-1.amazonaws.com/

Nick.
Okay not sure if I should have done this or not, but I added this to the bucket redirect configuration in S3,

[
{
"Condition": {
"KeyPrefixEquals": "https:///"
},
"Redirect": {
"ReplaceKeyWith": "http://"
}
}
]

it now works.

Edited by: goldenmonkey on Mar 20, 2021 12:29 PM

respondido hace 3 años
0

Okay, it was working, now it's gone again...

Any ideas how to resolve this?

respondido hace 3 años
0

it's now giving me a 403 and what looks like an IIS server error?? It's probably not IIS, but that's the only place I remember seeing that style of error, screenshot attached.

respondido hace 3 años
0

Update: Contacted 123 reg, got them looking at the DNS side of things, but in the meantime, the site is literally coming up and down on its own accord,

Wasn't working like 30 mins ago. Then started working, no changes to anything, went away from my PC for a while, came back, still working, all good, then goto instagram and back again, and boom, it's down again with the server error.

Attached a screenshot of what I'm seeing in the browser now, a whole bunch of permanent redirects for some unknown reason, all coming from IIS! Are S3 websites hosted using IIS??

Edited by: goldenmonkey on Mar 20, 2021 2:32 PM

respondido hace 3 años
0

Another screenshot of a ping of www.djabstraction.com, and then the CNAME that should be mapping to. Looks like it's jumping back and forth S3 and some unknown web server somewhere.

respondido hace 3 años
0

Okay so the day after all that, everything seems to have finally stabilised. I believe it was actually caused by an ancient DNS record, as I owned this domain years ago, and then purchased it again just recently. I removed the bodge https redirect I put into the S3 bucket properties too. So nothing but a little time was the actual solution.

respondido hace 3 años
0

Okay so the day after all that, everything seems to have finally stabilised. I believe it was actually caused by an ancient DNS record, as I owned this domain years ago, and then purchased it again just recently. I removed the bodge https redirect I put into the S3 bucket properties too. So nothing but a little time was the actual solution.

respondido hace 3 años

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Pautas para responder preguntas