15:49 <concernedPixel> hey there ppl! i thought this might be a good way to get in contact about an issue i have. i tried to view nouveau.freedesktop.org, but it seems those DNS records point towards a CNN site? could someone check on that? or is someone maybe already on it?

15:50 <concernedPixel> both my private recursor and 1.1.1.1 give four IPs in 151.101.0.0/16

15:54 <colinmarc> that's because there's a CDN in front

15:54 <colinmarc> https://api.fastly.com/public-ip-list

15:54 <colinmarc> 151.101.0.0/16 is in that list

15:54 <colinmarc> what makes you think it's a CNN site?

15:56 <concernedPixel> are you able to view the correct site? seems the CDN is mixing up the http requests then.

15:56 <concernedPixel> https://imgur.com/a/ifDbyLu

15:56 <concernedPixel> at least mixing it up on my end

15:58 <concernedPixel> also i am surprised to see a CDN IP for this subdomain, as FDOs A record returns a single answer with 131.252.210.176

15:58 <colinmarc> hm, my browser doesn't seem to mind the cert, let me grab my laptop and check it out (we did just change how certs are provisioned for it)

15:59 <concernedPixel> (my suprise here being: CDN for subdomain but not for main homepage?)

15:59 <colinmarc> it's partially rolled out, yeah

16:00 <colinmarc> or actually the fdo main page is not in scope

16:00 <colinmarc> just anything that's part of gitlab pages

16:02 <concernedPixel> that may be the case. but from your prev response i guess you are able to actually view the correct webpage of nouveau.fdo? because i dont just get a wrong cert but an actual fastly error message (sorry, had to wrangle with ff for a sec here)

16:02 <concernedPixel> now i get:

16:03 <concernedPixel> Requested host does not match any Subject Alternative Names (SANs) on TLS certificate [43181836e5d4fb555611adc1019534b3518f0849600ebc5311cdbe45923b0735] in use with this connection. Visit https://www.fastly.com/documentation/guides/concepts/errors/#routing-errors for more information.

16:03 <concernedPixel> which is weird...

16:05 <colinmarc> weird. yeah it loads fine for me and I also get a good cert:... (full message at <https://matrix.org/oftc/media/v1/media/download/ATVfjqTulppNUI-_ZJq7N_SXfVH7tmoBdOYP9J9LDWIY8SbvVEJ1ou3STIImh8pWq4l96kD0mYvi3hInYNUxEvhCeWTsveOwAG1hdHJpeC5vcmcvTE9wZElQV0ZJV2RXaWNobVp4ZkZHUXBQ>)

16:05 <colinmarc> flush your browser cache?

16:05 <concernedPixel> i just downloaded chromium to check. same error

16:09 <colinmarc> how about curl? try... (full message at <https://matrix.org/oftc/media/v1/media/download/Ab37UdEnotNeaqz0kJCbT-jCqvAyMLBrTmfluG9kAvozts_PoxoHRXFIHTKhAq2QIq9VGddXJYXtS7xAZl8_TzdCeWTs929QAG1hdHJpeC5vcmcvU1dVSHNoanlhb1NnYmlUZVpmSHVFTGxV>)

16:09 <colinmarc> (that's pinning the fastly ip)

16:09 <colinmarc> are you running a local resolver that's caching the old ip?

16:12 <colinmarc> <concernedPixel> "Requested host does not match..." <- that error is for domain fronting detection. very odd

16:12 <concernedPixel> ok, intresting. after checking stuff again, it seems to work again. i curled earlier and got also an invalid certificate error.

16:13 <concernedPixel> now chrome ff and curl do give me the correct content

16:13 <concernedPixel> i suspect it was a f** up by fastly

16:14 <concernedPixel> > are you running a local resolver that's caching the old ip?

16:14 <concernedPixel> i checked local and 1.1.1.1

16:14 <concernedPixel> both returned the same ips

16:15 <colinmarc> glad it's working!

16:15 <concernedPixel> sorry for the fuss :D have a nice day

17:13 <FreeBDSM> hello. Why don't desktop entries support envs?