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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
have you checked in the invidious logs for error messages? without your configs or logs, all we can do is guess about likely issues
What's invidious?
open source youtube website
What about using NewPipe instead?
I have ReVanced on my phone, STN on my TVs, and uBlock+SponsorBlock on my PCs. I was looking for an alternative that I could run on a server and would replace the various different apps I'm using. TubeArchivist ended up working perfectly for me; your mileage may vary.
Newpipe is a smartphone app, Invidious is a web frontend. I use the former but comparing the two are like apples and oranges. Clearly OP had their mind set on a web install.
NewPipe is an android app, invidious is a selfhosted service accessed through a website.
They are quite different to blindly suggested the other.
I use invidous to embed videos in my rss feeder.
Also the requests to YouTube are made from the server instead of the device.
I used Invidious for about a year and it was a constant string of bugs. Every release was a risk and quite often updates would get lost or the database would explode in size and consume all the drive space. Its not a project I currently use or recommend until it stabilises.
I decided to give up on it. Looking through the docs, they recommend that due to "reasons," it should be restarted at least daily, preferably hourly. I don't know if they have a memory leak or some other issue, but that was reason enough for me not to use it.
I installed TubeArchivist, and it suits my needs much better. Not only do I get an archive of my favorite channels, but when a new video is released, it gets automatically downloaded to my NAS and I can play it locally without worrying about buffering on my painfully slow internet connection.
What are the logs of the container? What are the logs from the browser? What are the responses from the network requests?
The specs of the machine tell us nothing to even start knowing what's wrong.