Netlify hosting with external Custom domain name issues

[luke]

Hi, @dev-mathiasmortelman. I checked both mathiasmortelmans.com and www.mathiasmortelmans.com and both are working when I test:

$ curl --compressed -svo /dev/null https://www.mathiasmortelmans.com/  2>&1 | egrep '^(<|>)'
> GET / HTTP/2
> Host: www.mathiasmortelmans.com
> user-agent: curl/7.79.1
> accept: */*
> accept-encoding: deflate, gzip
>
< HTTP/2 200
< age: 0
< cache-control: public, max-age=0, must-revalidate
< content-encoding: gzip
< content-type: text/html; charset=UTF-8
< date: Tue, 21 Jun 2022 05:54:05 GMT
< etag: "4fb62e3017c9c2070bc7e8e3a6cc4a48-ssl-df"
< server: Netlify
< strict-transport-security: max-age=31536000
< vary: Accept-Encoding
< x-bb-except: Cookie=__prerender_bypass,__next_preview_data
< x-nf-request-id: 01G62D6FX6CNJ1F5TTSP7BK0NY
<

$ curl --compressed -svo /dev/null https://mathiasmortelmans.com/  2>&1 | egrep '^(<|>)'
> GET / HTTP/2
> Host: mathiasmortelmans.com
> user-agent: curl/7.79.1
> accept: */*
> accept-encoding: deflate, gzip
>
< HTTP/2 301
< age: 0
< cache-control: public, max-age=0, must-revalidate
< content-type: text/plain
< date: Tue, 21 Jun 2022 05:54:14 GMT
< location: https://www.mathiasmortelmans.com/
< server: Netlify
< strict-transport-security: max-age=31536000
< x-bb-except: Cookie=__prerender_bypass,__next_preview_data
< x-nf-request-id: 01G62D6RD136MKDV9XCE90X4FB
< content-length: 49
<

If there is some URL not working for you, would you please send us the x-nf-request-id header for the incorrect response?

There more information about this header here:

[Support Guide] Netlify Support asked for the 'x-nf-request-id' header? What is it and how do I find it?

Last reviewed by Netlify Support staff August 2023 What is the x-nf-request-id header? Web servers and web browsers communicate using a protocol called HTTP - which stands for “HyperText Transfer Protocol”. Both web browsers and web servers use a feature called headers as part of this protocol. The headers that web browsers send are called “request headers” because the browser in making an “HTTP request”. The web servers headers are called “response headers” because web servers send an “HTTP …

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:

• the complete URL requested
• the IP address for the system making the request
• the IP address for the CDN node that responded
• the day and time of the request (with the timezone the time is in)

In the two responses above the headers were 01G62D6FX6CNJ1F5TTSP7BK0NY and 01G62D6RD136MKDV9XCE90X4FB. That information will help us to debug this issue.