Also tfw every time I search for solutions I get SEO spam articles - even on kagi. Most of the articles never help, and are for end users anyways. :aa:
I love how generative text bots just spit out 200x the amount of (WRONG) configuration and make it hell to find something written by a human, or even more, correct.
@thegreatape I am attempting to deal with the spam issue too on all fronts. If you click on the shield icon to the right of the link you can quickly block the site. Do it long enough and it might stop the worst offenders.
Kagi apparently tries to downrank content farms based on excessive ads already so it might be enough.
@thegreatape usually dns doesn't really involve ssl certs because its not very secure :blabcat: so maybe try some of the dig tools and see what those say?
firefox and some use some dns over http thing now, but i don't know much about that one.
@icedquinn I'm not 100% sure even. The TL;DR is: Sometime last night a sites SSL setup just went :blobcatghost: and traffic has been dead to this link for hours.
I already tried just renewing certbot and praying, but that didn't work. Now I see there's some edge certificate thing on cloudflare, which adds in a new variable that I've never messed with before.
I've gotten multiple different errors no less as I've tried fixing it. I'm beginning to suspect something is wrong with the DNS now, since all of a sudden the errors I'm getting are saying the A record can't be found :aniwhat: but it was clearly finding it 5 minutes ago.
Basically I've been on a wild goose chase, sifting through multiple http errors, trying to determine what the root cause is.
@icedquinn I figured it out... the domain got suspended by the registry 🫠. This is a first, I should have started from the bottom and went up in the first place for troubleshooting. I am still learning. and up to no good :devilish: