I was having some issues with Invidious the other day, which I resolved. However, I came across this tidbit of info that I’d never seen before when I first deployed it:
Post-install configuration:
Highly recommended
Because of various issues, Invidious must be restarted often, at least once a day, ideally every hour.
https://docs.invidious.io/installation/#windows
Anyone else observing this weird restart schedule?
That line predates invidious-companion. When the player and signature handling still lived in the main process, a periodic kick was the honest workaround, and the docs never really caught up after companion split it out.
What I’d push back on is the blind hourly restart, because it hides exactly the failure you just had. A companion image sitting a version behind shows up as things half-working, and a scheduled restart makes that go away for an hour at a time, so you never trace it. If you’re going to script something, script a check instead: hit an endpoint that actually plays a video, restart only when that fails, and log it when it does. Then a restart tells you something happened.
Small thing that would have caught your case:
docker compose pullwith no service name pulls all three, anddocker compose imagesprints the digests you’re actually running.That makes sense. I’ll see what I can come up with. Thanks for the guidance.
I haven’t used this tool specifically, but anything involving Youtube is always going to be an uphill battle. In the instance of a video downloader like Channeltube, you frequently need to feed it fresh cookies to make sure Youtube doesn’t flag it as a bot. I assume this is a similar situation.
The requirements also list ‘‘2gb if you restart frequently’’ so there might be a memory leak issue, or the way it’s setup means the RAM usage will increase in perpetuity.
I would just script a task to restart the docker container every hour. Shouldn’t be too much a hassle, you’re unlikely to ever notice since it shouldn’t take more than a few seconds. I would track its RAM usage over a few days too. See if there’s something fishy happening. Something like Beszel will let you track your docker socket, so usage per container. Preferably left on read only imo.
I would just script a task to restart the docker container every hour. Shouldn’t be too much a hassle.
Yeah, I was thinking about that. A script fired by a cron every hour. I do have the occasional, rare issue with Invidious. So, I’m wondering if indeed I need more restarts. It couldn’t hurt.
What kind of issues have you had? How did you resolve them?
Well, it was quite simple and I feel a bit embarrassed. LOL When I ran an update, I thought it updated all three components: Invideous itself, the companion app, and the database. However, only the Invidious and database updated leaving the companion app for whatever reason out of the loop. So after fumbling around and doing a little reading, I just so happened to look at Portainer which has a green checkmark beside the container signifying it’s the current version. The companion app had an orange checkmark. So I updated again, and Jack’s a doughnut, Bob’s your uncle. But during my reading I came across the ‘reboot hourly’ admonishment that I don’t believe I’ve seen before. Long story short, everything is fine now.
Oh, I’ve been there! lol Yeah, you sometimes don’t expect to have to update an entire stack, not just one thing. Possible the companion app image was just released later and it wasn’t on you either. :P
But yeah, give the cron job a try. I’d be curious to try it out myself! In theory your webinstance shouldn’t cut out unless you click on something the exact moment the container is resetting.
In theory your webinstance shouldn’t cut out unless you click on something the exact moment the container is resetting
Most of what I use Invidious for is inspiration and some tutorials such as this I’m trying to learn:
The guy makes me want to snap the neck of my bass in half.
Fuck yeah! This slaps. Brb while I get my headphones to listen to it again.
Yeah, if that doesn’t move you then you’re dead. LOL
I’d be surprised if most people running invidious for private use are following that advice. I’ve been on the master branch for a while and it gets updated fairly often. For my instance, I haven’t seen any reason to restart the service more often.
I haven’t seen any reason to restart the service more often.
Alright. Cool.
I stopped using Invidious a couple years ago, when I found out about FreeTube. I do have to update FreeT pretty often. I’ll put Invidious back on my list. Thanks for bringing it back to my attention.
Thanks for bringing it back to my attention.
You’re welcome. I think they’ve made pretty decent strides especially with the companion app and the fact that YT is relentless in trying to circumvent frontends.
Seems like there’s a FreeTube update every week or so. Cat and Mouse games, but what YT doesn’t realize is that Invidious and Freetube are the Cats and YT is the mouse to be consumed.
A friend of mine a while back was showing me some drums he was thinking about getting, and he had a YT video pulled up on his phone to show me of the drum kit in action. Two unskipable pre-rolls, one skippable pre-roll, the actual video, halfway through the video, another skippable ad. Jebus, how does anyone even put up with that? The ads were absolute bullshit too. One, as I remember, was this nurse advocating the use of Vicks Vapor Rub on your member to enhance the girth and length. I shit you not. I was like, who sees this and slathers Vicks Vapo Rub on your twigs n’ berries? Wow! That’s gotta burn. Damn sure would make mine run hide.
I wouldn’t want to ‘yuck someone else’s yum’. AND please please please NO VICK’S on DICKS! I haven’t used YT direct in quite some time. Thanks for the anecdote encouraging us all to continue avoidance.
I haven’t had to adjust or look at my invidious instance configs in a long time, but I do remember that in their docker instructions and I think I configured my container to restart hourly (or maybe I made it every other hour? Daily?). I’ve had no problems with my invidious instance in a long time, but that may have nothing to do with frequent restarts.
I think thats what I’ll do. Write a script, fired by a cron, to restart all three containers hourly and see how that goes. As I said further down, or up where ever this comment lands, that I do, on rare occasions, have issues with it. So, restarting couldn’t really hurt I wouldn’t think.
