Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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.
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.
Most of what I use Invidious for is inspiration and some tutorials such as this I'm trying to learn:
12-string BASS
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