-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
504 Gateway Time-out, The server didn't respond in time. #173
Comments
I can confirm that it is happening for me. I thought it was fixed. |
It's a problem that occurs when the load reaches a certain threshold. So it's not so much permanently fixed as the server is upgraded to handle the increased usage. |
@omarroth i getting same error when i try open https://invidio.us/feed/subscriptions |
Me too. |
I think it's also an issue that the site doesn't have proper error pages:
I know some errors (like 404) do have their own pages, but I think all but the worst errors should be caught before the user sees them. |
Any idea of what the associated costs would be with upgrading the server to handle it? |
Right now I'm looking into optimizing rather than upgrading, but if/when I were to upgrade, it would probably be about a ~$20 increase. |
I just upgraded the server, and now am able to access my feed. If others find the same, then we can probably close this for now. I'm still looking into optimizing it as much as I can, but in the short-term this appears to be fixed. |
Looks fixed on my end, even though it still takes 20-odd seconds to load. Also made a separate issue for proper error pages, instead of burying it here. |
I don't see why the index Another marginal gain in query speed would be to store all video ID's as 64-bit integers. The id stores a variant of b64 characters - together these characters add up to 66 bits. But YouTube just doesn't care about the last 2 bits, so all of these open the same video: Channel IDs could be similarly shortened, although they are 132 bits long, and I don't know whether they ignore any bits or not. |
Thank you! That definitely helps a lot. The comment about video IDs is interesting, but unfortunately the examples provided (except the first) return a |
Yeah, if you query them, they don't return anything, but if you open them on Youtube, they redirect to the first link. (This seems like a separate issue that needs to be fixed?) |
Opening the links on YouTube results in a Unfortunately, I'm still encountering this issue, if there's any other suggestions I would be very eager to hear them. |
I'm pushing out 35e63fa right now which should speed up subscriptions significantly, and we can hopefully close this. There's some more info on how it works in yesterday's release. I expect the migration to take ~1.5 hours. Everything except subscriptions should still be available during this time. Thanks everyone. EDIT: Migration should be complete. I'd recommend folks check their feed to make sure everything is working properly. Of note is that since the feed is cached, it may take a bit to update, even if there are notifications for new videos. I'd like to fix that as well, and if feeds are now displaying properly, then I'll close this in favor of #148. |
Just checked and the issue seems to be corrected. Much faster response. I had previously adjusted my settings to only show unseen notifications, so I reset it so that it shows everything with 25 results in the feed. First attempt was successful, super fast response, so I adjusted the results to 50 and then 100 videos in the feed. I ran 3 attempts per setting (25, 50, and 100) and recorded the results below. Response Times:
|
I'd be very interested to investigate, would you mind opening a new issue? |
It seems no one has encountered this for about a month, so I think I'll close this. If anyone encounters this again feel free to open a new issue, or I'll be happy to reopen. |
now i'm having this issue when checking out my subscriptions |
Anyone else getting that message when trying to access their subscriptions?
The text was updated successfully, but these errors were encountered: