hmm...
@kosinus Is @king@castling.club lacking webfinger or something? I can't seem to get my instance to recognize its existence.
@KS You’re not the first one to report that! But I just know thought of checking the access log, and noticed some instances are querying differently. I’ll fix it later today and will let you know!
@KS Could you try this again for me? I made a change that I think should fix this.
@king@castling.club
@KS You're opening this link exactly? https://castling.club/.well-known/webfinger?resource=king@castling.club
That'd be interesting. The CA is Let's Encrypt, which should be trusted by all browsers and servers by now. Could you show me details on the SSL error?
@kosinus I would, but now the link works fine, I blame flaky plane wifi.
I can't do any serious debugging on my phone a few miles up in the air, so it'll be a bit before I can try to figure out what's up myself, sorry
@KS Oh, haha, have a safe journey! Let me know when you have time and motivation.
What I've been able to find so far, through access logs, is that your instance is getting response served like it's a web browser. E.g., /@king redirects, instead of serving the JSON it should. So I'm wondering if the Accept header is not getting through? Looking at Mastodon code, it should work, also for the version you're running.
@kosinus yeah, nothing appears to have changed
Interestingly, if I try to navigate to /.well-known/webfinger?resource=king@castling.club manually I get an SSL error.