Closed vsatmydynipnet closed 1 year ago
Ah I found https://github.com/NicolasConstant/sengi/issues/343 looks the same. I will try the solution.
As mentioned in https://github.com/NicolasConstant/sengi/issues/343 :
Copy from there:
Solved! Connecting to the database with psql and running:
refresh materialized view instances;
fixed the problem. Thanks to @saper for help troubleshooting and for the solution!
Hi,
I have accounts on 2 instances, both running 4.x.
Sengi still works fine on mastodon.DOMAIN1, things still works as expected.
On my other instance I get errors when trying to click on a post:
Http failure response for https://mastodon.DOMAIN2/api/v1/instance: 500 OK
When I click on the profile link of the poster I get "account couldn't be found." The Instance works fine with Fedilab on LineageOS and also with "The Desk" on Linux. Instance is a more private one, having registrations, profile dir and unauthorized access to public timeline disabled. Thats the most difference between the 2 instances as I see.