Event JSON
{
"id": "1a016cfac640d0f3eb6cae99ff56de3a5db0e7c20909d7378113856a8f2b22f0",
"pubkey": "b4046d87a208cde1034cd7b777b035d1fcce1575a8aa16b44bc2a66ab0fd7361",
"created_at": 1756903564,
"kind": 1,
"tags": [
[
"t",
"nginx"
],
[
"t",
"internet"
],
[
"t",
"networkengineering"
],
[
"t",
"network"
],
[
"t",
"ipv6"
],
[
"proxy",
"https://mastodon.online/@macberg/115140431998378550",
"web"
],
[
"proxy",
"https://mastodon.online/users/macberg/statuses/115140431998378550",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.online/users/macberg/statuses/115140431998378550",
"pink.momostr"
],
[
"-"
]
],
"content": "Any network engineers who can shed some light on if an nginx 403 error can come from a site refusing IPv4 connections? The site in question (readanybook.com) works when used from an IPv6 enabled network and that's the only difference I can see.\n#nginx #network #NetworkEngineering #internet #IPv6",
"sig": "272e5c224100b4da7bc62e5dda0208e4533cbc06d30c1e681c4a19cc321b4d9723db781f767b44d036e62dde6466113db54356ec217d951c98ff5670996baf5d"
}