Fijxu/invidious
4
4
Fork 2
Code Issues 21 Pull requests Projects Releases Packages 1 Wiki Activity Actions

[Bug] Invidous has been restarting for about an hour now. Is this normal? #67

New issue
Closed
opened 2025-01-06 00:53:11 -03:00 by ddboy · 1 comment
ddboy commented 2025-01-06 00:53:11 -03:00
Copy link

<!-Invidious has been restarting for a hour now and the only backend that works currently is Backend 1-
BEFORE TRYING TO REPORT A BUG:

-->

Describe the bug

Whenever I open Invidious, it gives me a 503 Service Unavailable Error and the only available backend is backend 1, but videos are unplayable through that backend due to this error "Error while communicating with Invidious companion: connect timed out.

Steps to Reproduce

Steps to reproduce the behavior:
  1. Go to 'https://docs.invidious.io'
  2. Click on 'General'
  3. Scroll down to 'Instances, click it, and press inv.nadeko.net'
  4. See error

Logs

I pressed inspect on the page and got this error on all backends, except backend 1, "Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable)"

Additional context

**<!-Invidious has been restarting for a hour now and the only backend that works currently is Backend 1-** BEFORE TRYING TO REPORT A BUG: --> **Describe the bug** <!-- " -->Whenever I open Invidious, it gives me a 503 Service Unavailable Error and the only available backend is backend 1, but videos are unplayable through that backend due to this error "Error while communicating with Invidious companion: connect timed out. **Steps to Reproduce** <!-- -->Steps to reproduce the behavior: 1. Go to 'https://docs.invidious.io' 2. Click on 'General' 3. Scroll down to 'Instances, click it, and press inv.nadeko.net' 4. See error **Logs** <!-- -->I pressed inspect on the page and got this error on all backends, except backend 1, "Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable)" **Additional context** <!-- Add any other context about the problem here. - Browser (if applicable): Microsoft Edge. - OS (if applicable): Windows. -->
Fijxu commented 2025-01-06 01:57:02 -03:00
Owner
Copy link

fixed. Podman networking works differently from docker making haproxy not to detect invidious containers when it was restarted. I will need to find a way to deal with this :b

fixed. Podman networking works differently from docker making haproxy not to detect invidious containers when it was restarted. I will need to find a way to deal with this :b
Fijxu closed this issue 2025-01-06 01:57:02 -03:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
history-testing
testingbuh
testing3
testing2
testing
xdxdxd
experimental
test
external-proxy
debug
test123
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Fijxu/invidious#67
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?