New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random 504 error when viewing Subscriptions #144
Comments
Encountering this a lot myself. Also, most of the times the bell doesn't show notifications. |
Probably time to upgrade the DB server. The reason this is happening is because it's taking too long for the server to build a list of subscriptions, so the web server just times out. |
Why does it happen on video pages then? |
It still needs to pull number of notifications. I'm assuming it only 504s when you're logged in? If so, then the DB is probably overloaded. |
To clarify, it doesn't 504 on video pages, it just doesn't show the notifs at all sometimes - it didn't show any after 12 hours but it showed me unseen videos on the feed. |
Just bumped the DB by about 4x. Subscriptions now load almost instantly for me. If notifications are still not appearing, then we can continue to diagnose the problem, otherwise I'll probably consider this closed. |
Also before this is closed I would like to verify that notifications are also properly delivered. |
They are delivered properly now, got notifications after not opening invid for 9 hours. |
I still encounter this issue and can't go to my subscription for few days now. |
GauthierPLM: Are you getting a 504 error or something different? |
I had a 504 error yes. I had the issue while posting my previous comment, but the issue seems solved now, and the page respond almost instantly now. |
Everything appears to be working normally, I'm assuming it's working for you @Zero3K? If so, then I'll probably close this for now. |
Yes, its working fine for me. |
Great! Feel free to reopen this or create a new issue if it starts happening again. |
I am getting a random 504 error when viewing the Subscriptions page.
The text was updated successfully, but these errors were encountered: