search

immers-space / guppe

Federated social groups with ActivityPub, NodeJS, Express, and Mongodb
https://a.gup.pe
GNU Affero General Public License v3.0
192 stars 16 forks source link

a.gup.pe inexplicidly unreachable #65

Closed BeeFox-sys closed 1 year ago

BeeFox-sys commented 1 year ago

Akkoma, a fork of pleroma, does not seem to recieve any activities from guppe accounts, boosts and follow responses do not seem to work. I can send them fine and they say "Follow Request Sent" as all pending requests do, however a response is never recieved.

This is the only thing in my logs about guppe

journalctl -u pleroma | grep "gup.pe"
mix[8345]: 21:05:40.576 [warning] Can't find LRDD template in "https://a.gup.pe/.well-known/host-meta": {:ok, %Tesla.Env{__client__: %Tesla.Client{adapter: nil, fun: nil, post: [], pre: [{Tesla.Middleware.FollowRedirects, :call, [[]]}]}, __module__: Tesla, body: "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<title>Error</title>\n</head>\n<body>\n<pre>Cannot GET /.well-known/host-meta</pre>\n</body>\n</html>\n", headers: [{"x-powered-by", "Express"}, {"content-security-policy", "default-src 'none'"}, {"x-content-type-options", "nosniff"}, {"content-type", "text/html; charset=utf-8"}, {"content-length", "160"}, {"date", "Sun, 13 Nov 2022 10:05:40 GMT"}, {"connection", "keep-alive"}, {"keep-alive", "timeout=5"}], method: :get, opts: [adapter: [name: MyFinch, pool_timeout: 5000, receive_timeout: 5000]], query: [], status: 404, url: "https://a.gup.pe/.well-known/host-meta"}}

My instance is myfriendsare.gay, and i have put a call out for other akkoma instances to check if they have it working. all other instances accept and respond to follows, as well as return boosts, so i am unsure of the issues.

BeeFox-sys commented 1 year ago

ok it seems to just be my instance

BeeFox-sys commented 1 year ago

My instance seems to believe a.gup.pe is unreachable, is there anything in your logs to indicate if this is an issue on your end or mine? i can ping a.gup.pe with zero issues, but it does say that .well-known/host-meta is unreachable so it could be related to that?

BeeFox-sys commented 1 year ago

my instance believed a.gup.pe was dead and had stopped federating with it

BeeFox-sys commented 10 months ago

solution for future folks: reseting the unreachable_since field in the instances table resolved my specific issue