4 ms·
While I'm in general not a fan of wildcard certificates, yours doesn't work for the bare domain: https://i.imgur.com/uKVK5xd.png https://i.imgur.com/uKVK5xd.png
by dijit 5y ago
While I'm in general not a fan of wildcard certificates, yours doesn't work for the bare domain: https://i.imgur.com/uKVK5xd.png https://i.imgur.com/uKVK5xd.png
I was hitting it plaintext first, so a simple redirect to some subdomain instead of a bare redirect to https would probably work fine.
- marginalia_nu 5y agoHmm, curious behavior. I'm not getting that in any of the browsers I can run. Maybe some safari-specific interpretation? I don't trust letsencrypt and I don't want to give them or anyone else a list of which subdomains I use.
- timvdalen 5y agoI can at least reproduce it in Chrome, for what it's worth. Perhaps you have the redirect to www cached?
- marginalia_nu 5y agoOn an Apple or another OS?
- seszett 5y agoI can reproduce it even just with curl on Linux. The certificate is only for "*.marginalia.nu", which simply doesn't cover "marginalia.nu". It should give the same error on any platform and browser, unless their SSL implementation is broken. Some browsers try to be smart and insert www automatically though.
- Ronsenshi 5y agoI would recommend getting certificate which includes root domain and wildcard subdomains to cover all bases.
- jffry 5y agoThe cert I am seeing [1] does include both the wildcard subdomain AND the apex domain [1] https://crt.sh/?id=6125359537 https://crt.sh/?id=6125359537
- seszett 5y agoThat's not the certificate I get served though (this one is from 5 february, the one served is from 25 january) do you actually get this certificate on https://marginalia.nu https://marginalia.nu?
- jffry 5y agoI misunderstood what URL we were talking about. What I am seeing: https://marginalia.nu https://marginalia.nu = https://crt.sh/?id=6046506678 https://crt.sh/?id=6046506678 (includes wildcard but NOT apex) https://search.marginalia.nu https://search.marginalia.nu = https://crt.sh/?id=6125359537 https://crt.sh/?id=6125359537 (includes both wildcard and apex)
- marginalia_nu 5y agoAh, I see what's happening. search.marginalia.nu goes through cloudflare which does its creepy MITM thing and re-encrypts on its end; the others do not.
- wizzwizz4 5y agoWhy does marginalia.nu use Cloudflare? Have you been hit by DDOSs? I can't think how a search engine would benefit from Cloudflare caching things.
- marginalia_nu 5y agoYeah, It's 100% about bot mitigation. I got hit pretty bad by some botnet a while back, saw 10-15 searches/second. Can't have nice things on the Internet I guess. Don't really understand their motive either. Maybe they thought I was cloud hosted or used some expensive API to do searches and were attempting to rack up big bills or something.
- input_sh 5y agoIt's simple, your cert points to *.domain.tld, domain.tld doesn't have a subdomain, <anything>.domain.tld does. You should expand it to include both domain.tld and *.domain.tld.
- jffry 5y agoIt seems like a bad cert is being served at the redirect; the LE cert at https://search.marginalia.nu https://search.marginalia.nu DOES have both the wildcard and apex domain See https://news.ycombinator.com/item?id=30301015 https://news.ycombinator.com/item?id=30301015
- MonaroVXR 5y ago> .domain.tld Oof, I'm not sure if I would do that. Since "" stands for all sub domains.
- jffry 5y agoThere may be some type of caching problem. When I visit https://marginalia.nu https://marginalia.nu directly, I'm served with this cert, which does not include the apex domain: https://crt.sh/?id=6046506678 https://crt.sh/?id=6046506678 When I visit https://search.marginalia.nu https://search.marginalia.nu I'm served with this different cert, which does include both wildcard and apex: https://crt.sh/?id=6125359537 https://crt.sh/?id=6125359537
- deleted 5y ago[deleted]