So, that should have resolved the issue, but it’s probably best to do another post in a group with the domain as part of the name…

When did we upgrade to 1.7? Rimu says this issue was fixed in 1.7, but I can’t tell if the original post was made before or after the upgrade…

Actually, there is an issue open on this already…

https://codeberg.org/rimu/pyfedi/issues/1831

Okay, that was a duplicate… The original issue was filed here: https://codeberg.org/rimu/pyfedi/issues/1809

Rimu has acknowledged it.

I think I see the issue… Looking at the post from mastodon.social this is what comes through:

@gemelen@mammut.moe was seeing the post as above: from Mastodon… Apparently when the message was federated to the rest the FediVerse the generated URL is wrong. The @lemmy.world portion was removed. I think this is a bug that Rimu will need to look at…

Not surprising… I’m sure CloudFlare is working overtime to block these ridiculous bots. I’ve seen my analytics provider is blocking tons of bots every day, even low volume sites like mine are getting hit with hundreds of bot requests.

I’ve just asked gemelen if he can join us to answer your questions.

I was thinking about what you said regarding curl (originally in your deleted post): would setting the user agent have had any effect? I seem to recall having done that in the past for some specific script I wrote (but that was over 15 years ago, so my memory may be shot).

Makes sense that if the URL was wrong in the first place, then the whole thing would fail with a 404 or 403.

gemelen did say that when he tried it from his desktop it worked — hence the reason he suspected it was an issue between cloudflare and his mobile carrier, as he mentions in the quote above.

If you don’t get a response to a pm, you could go to c/piefed_meta or c/piefed_help - most of the admins will be watching those communities.

That was a backup plan in my book. Just want to see if there is a way to avoid that. (Although with the way Federation works it might be the best option.)

No problem - was just wondering if I was trying to do stuff during a maintenance window. I was suspecting that you were doing a snapshot of your database (at 12am), then bringing the system back online while a backup ran against the snapshot…only to have to bring the database back down to remove the snapshot (at 1am).

What I thought was strange was that the client side wasn’t in a maintenance mode…