this post was submitted on 31 May 2022
0 points (NaN% liked)
Lemmy Support
4652 readers
1 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Found out just now what the problem was.
I am writing this to help others: the federation was active in that instance but it was also marked as a private instance. This gave no problems in using it until the update (probably because it is restarted and re-run Docker).
I removed the federation from the config file leaving only the private instance and it restarted immediately.