Notices by nex (nex@fedi.transgender.ing), page 3

@jessew@mk.cpluspatch.com Anything?

@jessew@mk.cpluspatch.com give it time, one sec

@jessew@mk.cpluspatch.com It is fixed, you'll just have to wait for servers to stop backing off. Let me see if I can force my Synapse to push

@jessew@mk.cpluspatch.com if you leave it like this, it will eventually fix itself, but it could be two days before people start federating with you again

@jessew@mk.cpluspatch.com my server says the destination for you is supposed to be matrix.cpluspatch.dev:443, but a live resolution says your destination is actually cpluspatch.dev:443. You might wanna switch your well-known/matrix/server back (no idea what your setup looks like)

@jessew@mk.cpluspatch.com matrix.cpluspatch.dev

@jessew@mk.cpluspatch.comChecking if cpluspatch.dev is in the s2s cache. 'cpluspatch.dev' is not a valid IP[:port] literal. Proceeding with well-known resolution. Result for 'cpluspatch.dev' from well-known: 'cpluspatch.dev':443 ServerName object is now ServerName(server_name='cpluspatch.dev', sni=None, port=443, cache_until=1743380791.21113) well-known reported the server address as explicitly 'cpluspatch.dev':443 Final ServerName object: ServerName(server_name='cpluspatch.dev', sni=None, port=443, cache_until=1743380791.21113) Sending a request to https://cpluspatch.dev:443/_matrix/federation/v1/version (but connecting with SNI/Host: 'cpluspatch.dev') Response code: 200 Response headers: Headers({'server': 'Synapse/1.127.1', 'date': 'Sun, 30 Mar 2025 00:26:31 GMT', 'content-type': 'application/json', 'cache-control': 'no-cache, no-store, must-revalidate', 'access-control-allow-origin': '*', 'access-control-allow-methods': 'GET, HEAD, POST, PUT, DELETE, OPTIONS', 'access-control-allow-headers': 'X-Requested-With, Content-Type, Authorization, Date', 'access-control-expose-headers': 'Synapse-Trace-Id, Server', 'transfer-encoding': 'chunked', 'strict-transport-security': 'max-age=15552000; includeSubDomains', 'x-content-type-options': 'nosniff', 'permissions-policy': 'interest-cohort=()', 'vary': 'Accept-Encoding', 'content-encoding': 'gzip'}) Response text: '{"server":{"name":"Synapse","version":"1.127.1"}}' Response: {'server': {'name': 'Synapse', 'version': '1.127.1'}} Response successful!

@jessew@mk.cpluspatch.com what

@jessew@mk.cpluspatch.com looks like you aren't delegating properly?

@jessew@mk.cpluspatch.com do you port forward those though? your server reports that it federates on port 443

@jessew@mk.cpluspatch.com looks like https://49.13.76.117:443 is returning 503 for federation requests

@jessew@mk.cpluspatch.com I bet your reverse proxy is pointing at the wrong internal IP or port or smthn

@jessew@mk.cpluspatch.com well are you expecting to retrieve traffic on another port?

@jessew@mk.cpluspatch.com your entry point web server thingymajig

@jessew@mk.cpluspatch.com is your ingress misconfigured?

@jessew@mk.cpluspatch.com we're reading you loud and clear, something's going wrong on you receiving us

@jessew@mk.cpluspatch.com getting HTTP 503 trying to fetch events from you

@jessew@mk.cpluspatch.com you bAFFOON y ou are federating

@jessew@mk.cpluspatch.com @sodiboo@gaysex.cloud fym how I'm dyslexic as shit and you've given me an image blurrier than my vision after I forget to have breakfast 😭

@jessew@mk.cpluspatch.com @sodiboo@gaysex.cloud bitch i cannot