[New instance] iv.duti.dev

[acheong08]

URL

https://iv.duti.dev

Mandatory checks

• Instance has a domain name
• Instance is served over HTTPS
• Statistics (/api/v1/stats) are enabled
• Instance is properly configured (including the mandatory post install configuration)
• Instance has an automatic hourly restart setup of Invidious
• If dash, proxy + download is enabled (default settings), the instance has unlimited traffic/bandwidth or close to unlimited (100TB minimum)
• Instance is not running any kind of analytics, including external scripts of any kind
• If using Cloudflare or any other DDoS protection service, settings are configured to allow uptime monitoring. Cloudflare users can consult this guide

Maintainer chart

• Ensure that my instance is up to date (less than one month old)
• Ensure a proper uptime of my instance (around 90%)

Rules for public instances

• I agree to follow the rules for public instances

Host country

United Kingdom/Germany

Man in the Middle

No response

Source code URL

https://github.com/acheong08/invidious/

Your matrix username

acheong0

Additional information

Instance has been running for over a year at this point for personal use. Saw that the list of working instances is diminishing so felt like I should contribute a bit.

Currently running on 16GB of RAM and an 11th gen i7 CPU so traffic shouldn't kill the instance.

[github-actions]

Hello! Your instance has been added to our monitoring system: https://updown.io/ajl0
You need to wait 30 days before we add your instance, this is to evaluate that your instance will keep a good uptime for one month.

Make sure you double checked all the mandatory checks or this will slow down the process of adding your instance!

Please consult these two important tutorials:

• Escaping the YouTube block (403 errors in playback): https://docs.invidious.io/ipv6-rotator/

• Improving the performance and the stability of your public instance: https://docs.invidious.io/improve-public-instance/

It is highly recommended to follow these tutorials because it will allow the instance to stay stable and performant over the long term.

[acheong08]

Hmm not sure why the uptime tracker is getting a 502 when I can visit it just fine.

Edit: ipv6 wasn't working. fixed.

[unixfox]

Hello, since October a lot has happened. YouTube is cracking down heavily on 3rd party softwares using their unofficial API like Invidious.

This mean that once your instance will be added to the public list, there is a very high chance it will stop working after a day. It's possible that your instance may survive this blockage if you are running it on a residential IP address because YouTube seems to be more kind towards residential IPs. We don't exactly know at what limit they consider banning the IP address.

Currently, the counter-measures employed by the existing instances are rotating the IP address every hour, as of right now there is no guidance regarding that so you will need the knowledge in this field to keep your instance running.

Do you still want to run a public instance?

[unixfox]

Closing due to lack of replies.

[acheong08]

Oops I missed the message. YouTube has gotten a lot more aggressive such that most large instances don't work anymore so I don't think listing is a good idea.