3 ms·
Happened to me with http. Once you successfully connect to the https endpoint, HTTP Strict Transport Security kicks in and you no-longer see it. just fyi.
by asteadman 11y ago
Happened to me with http. Once you successfully connect to the https endpoint, HTTP Strict Transport Security kicks in and you no-longer see it. just fyi.
- tixocloud 11y agoAny thoughts/ideas on how to fix this?
- asteadman 11y agoSomewhere in your config there's a 301 redirect (UHOH!) to localhost, either as a cloudflare page rule or a misconfiguration on your origin server. If you use chrome you can remove HSTS for your domain here: chrome://net-internals/#hsts , this should at least allow you to replicate the problem (just don't visit the https version or it'll be enabled again.) $ curl -v orchestrahq.com * About to connect() to orchestrahq.com port 80 (#0) * Trying 104.27.137.19... connected > GET / HTTP/1.1 > User-Agent: curl/7.22.0 (i686-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3 > Host: orchestrahq.com > Accept: */* > < HTTP/1.1 301 Moved Permanently < Date: Wed, 06 Apr 2016 14:09:23 GMT < Content-Type: text/html; charset=utf-8 < Transfer-Encoding: chunked < Connection: keep-alive < Set-Cookie: xxx < X-Frame-Options: SAMEORIGIN < Location: https://127.0.0.1:8008/ < P3P: CP="ALL DSP COR PSAa PSDa OUR NOR ONL UNI COM NAV" < X-Content-Type-Options: nosniff < Server: cloudflare-nginx < CF-RAY: 28f5d13940ba0719-SJC
- tixocloud 10y agoThanks very much. Hopefully, it's been fixed.