10 Apr 2024 |
lola | It's updated version https://github.com/89Q12/rusted-invidious | 14:30:58 |
@marioyd:matrix.yourdevice.ch | I am talking about the
`The video returned by YouTube isn't the requested one. (Android client) (VideoNotAvailableException)`
Issue | 14:31:05 |
@marioyd:matrix.yourdevice.ch | I don't run rusted Invidious. Does it mean there is no update for it yet | 14:33:24 |
Lomanic | marioYD: which invidious image and tag are you using? | 14:34:40 |
@marioyd:matrix.yourdevice.ch | In reply to @lomanic:matrix.org marioYD: which invidious image and tag are you using? quay.io/invidious/invidious:latest | 14:35:12 |
Lomanic | marioYD: At runtime, what is the version displayed in the footer? | 14:37:22 |
@marioyd:matrix.yourdevice.ch | In reply to @lomanic:matrix.org marioYD: At runtime, what is the version displayed in the footer? sorry but how do i find this out where do i see it, on browser accessing my instance? | 14:45:43 |
Nihilist OLD ACCOUNT !!!! | Bottom right corner on your instance pqge | 14:46:26 |
@marioyd:matrix.yourdevice.ch | Version: 2024.03.08-99a5e9c @ master | 14:46:27 |
Nihilist OLD ACCOUNT !!!! | * Bottom right corner on your instance page | 14:46:40 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @marioyd:matrix.yourdevice.ch Version: 2024.03.08-99a5e9c @ master That's definitely not the newest version. Update your containers, you're running a version that does not have the fix for the The video returned by YouTube isn't the requested one. (Android client) (VideoNotAvailableException) error. | 14:49:21 |
@marioyd:matrix.yourdevice.ch | In reply to @alexpewmaster:nope.chat That's definitely not the newest version. Update your containers, you're running a version that does not have the fix for the The video returned by YouTube isn't the requested one. (Android client) (VideoNotAvailableException) error. and how do I updated? using the latest tag | 14:50:06 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @marioyd:matrix.yourdevice.ch and how do I updated? using the latest tag Go to your directory where the docker-compose.yml file is and run docker compose pull | 14:51:29 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Using the latest tag doesn't mean that you're always running the newest version, you also have to frequently update for it to be the actual latest version | 14:52:52 |
@marioyd:matrix.yourdevice.ch | In reply to @alexpewmaster:nope.chat Using the latest tag doesn't mean that you're always running the newest version, you also have to frequently update for it to be the actual latest version ok got this | 14:53:15 |
@marioyd:matrix.yourdevice.ch | thanks for explanation | 14:53:21 |
@marioyd:matrix.yourdevice.ch | thought it automatically pulls newest version | 14:53:32 |
@marioyd:matrix.yourdevice.ch | not used to docker long | 14:53:38 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @marioyd:matrix.yourdevice.ch thought it automatically pulls newest version You could setup watchtower for this | 14:53:46 |
@marioyd:matrix.yourdevice.ch | updated and solved 🙏 | 14:53:59 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @marioyd:matrix.yourdevice.ch thought it automatically pulls newest version * You could setup watchtower for this (https://containrrr.dev/watchtower/) | 14:54:04 |
manwichmakesameal | You can use watchtower to auto-pull and notify. You can even have it restart the containers but personally, I don't like that. | 14:54:09 |
@marioyd:matrix.yourdevice.ch | just gotta run
docker run -d \
--name watchtower \
-v /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower
| 14:55:16 |
@marioyd:matrix.yourdevice.ch | and thats all? | 14:55:19 |
manwichmakesameal | I would use a compose file, but that's just me. | 14:55:34 |
manwichmakesameal | But yes, that would get a functioning container of watchtower. | 14:55:53 |
manwichmakesameal | It'll pull and auto-restart ALL containers by default though. | 14:56:09 |
manwichmakesameal | services:
watchtower:
image: containrrr/watchtower
container_name: watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
WATCHTOWER_MONITOR_ONLY: 'true'
WATCHTOWER_NOTIFICATIONS: email
WATCHTOWER_NOTIFICATION_EMAIL_FROM: nope
WATCHTOWER_NOTIFICATION_EMAIL_TO: nope
WATCHTOWER_NOTIFICATION_EMAIL_SERVER: nope
WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT: 587
WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER: nope
WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD: ${WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD}
WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG: nope
restart: unless-stopped
You can put all of the environment variables in an env file but that's my compose file for watchtower.
| 14:58:04 |
@marioyd:matrix.yourdevice.ch | okay thanks, will look into this. Sorry i dont check so much github issues and here, allthough i should, but i guess
2024-04-10 14:55:14 UTC [info] 500 GET /api/v1/comments/jNQXAC9IVRw 362.62ms
ist still because of the comment issue still making trouble thus showing unhealthy containers?
| 14:58:09 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | You can replace the health check with a different endpoint, for example: Replace http://127.0.0.1:3000/api/v1/comments/jNQXAC9IVRw with http://127.0.0.1:3000/api/v1/stats , then the container will show up as "healthy". | 15:00:42 |