Hi,
I had a couple of people mention they were getting an error trying to access a link I posted in c/fountainpens. One of the users (@gemelen@mammut.moe) created a traffic dump of trying to access the link using curl. He posted his results on this Opensuse paste bin.
He added this:
I guess Cloudflare prevents some web clients (like embedded viewer for a Mastodon mobile app) and some networks (like mine Uruguayan Internet provider) - I could open the feddit.online and see your post there in a desktop browser, but being forbidden to access from a mobile or via curl.
George


@Jerry
To clear this out: curl _may_ work even in that particular case with a provided user-agent and other things, if necessary. But the most importantly, it demonstrated that the Cloudflare is in front of your resource.
Originally, the URL that was shared by @Unattributed is “https://feddit.online/c/fountainpens/p/1803832/why-fountain-pens”, so it was attempted to visit from the mobile (either Tusky or Pachli app - Mastodon clients for Android, and from mobile Vivaldi).
Thus I (and accidentally other person) replied that it’s unreachable through these methods. On the other hand, it could be opened from a desktop browser (desktop version of Vivaldi specifically).
Where that URL came? Likely, copied from the browser’s address bar, I would assume. But that’s a question to @Unattributed
Yes, Cloudflare has tools to detect bot traffic, which include curl and similar utilities. It absolutely stands in front of the server.
But if the correct URL cannot be opened by a mobile client, then there’s a problem. Then I’d need the details.
The firewall is trying to only allow traffic from either web browsers, other ActivityPub servers, or mobile applications. It’s designed to block traffic from anywhere else.
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…
I upgraded the server to 1.7 the day it was released. It was released yesterday, July 3rd. This morning I updated it to 1.7.1, which was released today. Your post was made before the upgrade to 1.7
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…
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.worldportion was removed. I think this is a bug that Rimu will need to look at…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.