Micro.blog

manton
manton

Just merged in 3 pull requests from @vincent. Good week for bug fixes. 🎉

issimonwoods
issimonwoods

@manton Is it still useful to report bugs on GitHub?

In reply to
cdevroe
cdevroe

@manton Side note: webmentions still aren't working. I know you said it was HTTPS error but I don't have SSL on my blog (I should correct that). But I never had HTTPS in my settings on M.b - So I am wondering why the issue started?

manton
manton

@cdevroe If I remember correctly, the error about SSL is actually internal to your blog. Micro.blog is not trying to connect with SSL, but something on the WordPress side is trying to use SSL and failing.

cdevroe
cdevroe

@manton OH. Weird. OK. Setting aside a few minutes to see if I can figure out what is happening. Sorry.

cdevroe
cdevroe

@manton Forgive my ignorance, does M.b call cdevroe.com/wp-json/w... and include a source and target POST vars?

cdevroe
cdevroe

@manton When I run cURL against micro.blog or cdevroe.com I do not get a certificate has expired message. So I'm trying to find out what URL the Webmention plugin is calling that is throwing that error.

cdevroe
cdevroe

@manton spelunking into my access.log is revealing some very interesting things.

Off topic, but examples: - 👋 Micro.blog's 500 requests to my site today. :) I like it. - 👋 To the roughly 200 calls from Fever (didn't realize that was still a thing) - 👋 Petalsearch dot com for trying many webmentions for random page numbers? Their bot sends webmentions instead of just content scraping? - 👋 91.149.244.147 for the 1,100 calls to the WordPress XML RPC API today ??

Sadly, nothing that tells me what URL is failing and nothing in error.log.

cdevroe
cdevroe

@manton Super happy to see the hundreds of calls per day from NetNewsWire. 🥰

(Sorry for the mention spam. Just working through this. I really want webmentions from M.b working again.)

cdevroe
cdevroe

@manton So I sent a message to the creator of the plugin also, gave him all the information, and even he said he doesn't know why that is an error now. None of this process seems to require HTTPs. I don't know what is going on. :(

manton
manton

@cdevroe I'm going to send you an email with the details of what Micro.blog is doing. The error is definitely coming from your server. My new theory is that maybe an old SSL cert is cached and so your server can't connect back to Micro.blog.

cdevroe
cdevroe

@manton OK. Will look. I spent about 2 hours spelunking.