Post by @chainq@mastodon.social
Messing with an experimental #littlefedi instance (behind a public IP HTTPS proxy), and it seems I'm successful in federating with a bunch of servers, but I consistently just get 401s from mastodon.social itself, for example when I try to search for my own handle here. Anyone with an idea what am I holding wrong, or is this normal?
Sadly, @littlefedi_official's documentation is quite vague on what is actually needed to make this work, or how to debug when it doesn't.
1 like
@chainq@mastodon.social @littlefedi_official@littleone.littlefedi.social I run a vanilla, OOTB #LittleFedi on Ubuntu using Caddy as the reverse proxy. What is your OS and RP ? I follow a few accounts on mastodon.social with no issues. I presume the 401 errors come from the LF log file ?
sudo journalctl -u littlefedi -f
@andyc @littlefedi_official I'm using Raspberry OS on a Pi 4, and the latest LittleFedi binary. The reverse proxy is my public IP Apache 2 setup, which the RPi has a tunnel to, on a Hetzner VPS. But the proxy works, for a lot of other things (the LittleFedi instance is just a VHost). Yes, the 401 comes from the log, f.ex:
16:35:12.136 WARN webui: remote account not found username=chainq@mastodon.social error=fetch actor https://mastodon.social/users/chainq: fetch https://mastodon.social/users/chainq: status 401
@chainq @littlefedi_official Maybe failing signature? Not sure why this would only be happening with mastodon.social (or how to fix it), but might be a breadcrumb: https://swicg.github.io/activitypub-http-signature/#how-to-verify-a-signature
Maybe @stefano can verify even if he doesn't have time to troubleshoot.
Quick questions:
Are you using an IPv6 only setup? Or dual stack?
Do you get the same 401 errors with other instances (e.g. aus.social)?