[bug?] Federation not working completely, missing some status on threads, other instances might not be able to find mine #576
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#576
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
Docker
Extra details
Ubuntu server on a vps, docker installation following the official docs.
Version
latest
PostgreSQL version
14
What were you trying to do?
No response
What did you expect to happen?
No response
What actually happened?
Some instances fail to find my instance at all, or the status another account boosts, remote follows are given just a generic error. Can't migrate account from another instance to the new one.
Logs
No response
Severity
I can manage
Have you searched for this issue?
you... uh... gonna give more details here?
there is sweet diddly heck all that we can actually do here
I'm not too sure what else is there to say, is not that it doesn't work or my end, the error is given from other instances, where they can't find my instance, mention users, remote follow or migrate.
The instance itself is usable and works, but it doesn't seem to be federating properly.
This is the log file docker returns.
if nothing is failing on your instance, then here would not be the correct place to raise your issue - we cannot fix external issues unless we know something is failing our side
the fediverse is not centralised by design, and uses various implementations that are not all controlled from the same place. this means that we cannot fix issues that occur externally
if you are a brand new instance, you may need to wait a few hours for external instances to discover you and fetch your public key
otherwise, please raise the issues to the projects from which the errors originate
your webserver is hecked. you are using the webroot method of letsencrypt HTTPS verification and people cannot webfinger you
see https://ak.lavenderfield.xyz/.well-known/webfinger/?resource=acct:junkyard
this should not happen. this path should not be handled by nginx
please rectify your nginx config