this post was submitted on 24 Jul 2026
19 points (95.2% liked)

Selfhosted

60910 readers
1038 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

  8. 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] mike_wooskey@lemmy.thewooskeys.com 2 points 12 hours ago (1 children)

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.

[โ€“] irmadlad@lemmy.world 2 points 12 hours ago

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.