I have set up the site https://ag-labs-poker.netlify.app/ to be accessible from a subdomain that I own, poker.ag-labs.io. The main domain is registered to another netlify site and works as expected, all hits on http are redirected to https.
However on the new site accessible from the subdomain there is no automatic redirect from http to https, is this something I have missed on the netlify side or on the side where I purchased the domain?
Hey @AG-Labs,
Could you please share the Netlify URL where you’re seeing HTTP? Sounds like maybe there was an problem provisioning or extending your SSL certificate, as we do force HTTPS on all connections. Thanks!
Hi Jen
The site fails to load when navigating to http://poker.ag-labs.com/
It does redirect on the netlify own domain http://ag-labs-poker.netlify.app
Hey there! Have you followed the prompts in the Netlify UI to correctly configure DNS for this domain?
Not using Netlify DNS? Check this out. Otherwise, give this a spin!
I believe so, I added the c name for the subdomain, attached the Netlify dns setup here.
Looking in GoDaddy I cannot add records because “the name servers aren’t managed by us” but I can add forwarding with masking if that is the only way to do this.
Hi, @AG-Labs. I see the redirect when I test:
$ curl -svo /dev/null http://poker.ag-labs.io/
* Trying 167.172.221.254...
* TCP_NODELAY set
* Connected to poker.ag-labs.io (167.172.221.254) port 80 (#0)
> GET / HTTP/1.1
> Host: poker.ag-labs.io
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Cache-Control: public, max-age=0, must-revalidate
< Content-Length: 41
< Content-Type: text/plain
< Date: Tue, 08 Sep 2020 08:15:06 GMT
< Location: https://poker.ag-labs.io/
< Age: 0
< Connection: keep-alive
< Server: Netlify
< X-NF-Request-ID: 3918bb66-571e-4b9f-894f-6b61341ad058-242712
<
{ [41 bytes data]
* Connection #0 to host poker.ag-labs.io left intact
* Closing connection 0
If you are still seeing failing redirects, we need to be able to track the HTTP response with this issue. The simplest way to do this is to send us the x-nf-request-id header which we send with every HTTP response.
There more information about this header here:
If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:
Thank you Luke
Tested that curl command and got the same response.
Tested a different machine on the URL and it worked, might have messed up my local machine in some way.
Sorry for wasting your time.