Skip to main content


Error 500 /network


why do I have error 500 in /network , my friendica instance worked fine for a few days, and today when I go to /network , I recive this error , in the web browser I have the error, I also cleaned the cash .

Fedilab works on my Android, I can access (My friends Conversation)

Thanks

!Friendica Support #Friendica

in reply to ༄𝔫𝕖𝚖ƴ᥉༄

@🦋༄𝔫𝕖𝚖ƴ᥉༄🦋 Without any log files, like error_log from your web server or friendica.log no one help you here. So please post log messages that came during the 500 error.

Friendica Support reshared this.

in reply to ༄𝔫𝕖𝚖ƴ᥉༄

@nemys I had the same in the past sometimes, especially when sorting by activity. Reducing the number of posts per page in the settings helped or loading the network with "network?channel=created".
in reply to Phil

@Phil
Thanks Phil
I had infinite scroll, I deselected, I set it to 25 but the problem remain
@Phil
in reply to ༄𝔫𝕖𝚖ƴ᥉༄

@Phil @Michael Vogel @Roland Häder
It works now, as suggested @Phil , reducing the number of posts, I had to set it to 10 , Not many but it works now . Thanks....
in reply to Roland Häder

@Roland Häder @Michael Vogel @Phil
I tried to raise memory limit to 512, leaving the friendica settings as default but it didn't work
in reply to Roland Häder

@Roland Häder @Michael Vogel @Phil
I raised memory limit to 512, in the User /Number of items displayed per page: I put 25. For now it works, if it gives me problems I now know how to solve it. In the admin panel I left it at 10.
in reply to ༄𝔫𝕖𝚖ƴ᥉༄

@nemys @Michael Vogel @Roland Häder
I'm using 10, too.
Perhaps there's a way to prevent this issue or at least show some error instead of the HTTP 500?
When I had this issue, I contacted the admin of my instance as well, but it was not reproducible on his side. It seems to be somehow related to the specific content of the own network and disappears after a while.
in reply to Phil

Yep. Same experience here. Me and another user on my node had the same issue some time ago. It was caused by one single post. Every time that post had to be loaded via front end the corresponding PHP-FPM process ran out of memory. After I deleted the post via admin panel everything was working again.