[New instance] https://invidious.incogniweb.net

viaguy commented 4 months ago

URL

https://invidious.incogniweb.net/

Mandatory checks

[X] Instance has a domain name
[X] Instance is served over HTTPS
[X] Statistics (/api/v1/stats) are enabled
[X] Instance is properly configured (including the mandatory post install configuration)
[X] Instance has an automatic hourly restart setup of Invidious
[X] If dash, proxy + download is enabled (default settings), the instance has unlimited traffic/bandwidth or close to unlimited (100TB minimum)
[X] Instance is not running any kind of analytics

Maintainer chart

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

Host country

United States

Man in the Middle

No response

Source code URL

No response

Additional information

The instance is served by Nginx and supports all the sweet new HTTP protocols. http3check.net results

The instance banner is a link to my site homepage that lists the other open source front ends I host. On the page is also a link that allows users to donate to help support server costs if they wish. I don't think this violates rule 12 on the public instance rules, since its not for profit and I'm not selling anything. But I should mention it anyway for the sake of transparency.

Currently, dash and proxy are disabled by default (but still available for users to enable) due to bandwidth limitations. I am working on upgrading the available bandwidth on my VPS plan as I would really prefer to enable dash and proxy for all by default. Though it may not be possible for me to afford 100TB+ of bandwidth per month without donation support.

I'm using the default captcha shipped with invidious (captcha_enabled: true)

The instance is using my own implementation of IPv6 rotation to avoid youtube blocking, by leveraging RFC 8981 Temporary Address Extensions and the net.ipv6.conf.eth0.use_tempaddr=2 linux kernel setting. This causes applications to make outgoing v6 connections from the randomly generated address instead of the static IPv6 address unless otherwise specified. I also have modified the expire time of temporary addresses to limit their preferred lifetime to 1 hour, for more frequent address changes.

As I have my system configured: Nginx front end listens for connections on IPv4 & the static IPv6 address of the server. The Invidious backend makes outgoing connections from the dynamic IPv6 privacy address.

github-actions[bot] commented 4 months ago

Domain not detected in the title, please edit the title by correcting it like this: Issue title example: [New instance] https://myinstance.com

github-actions[bot] commented 4 months ago

Hello! Your instance has been added to our monitoring system:

uptime robot: https://stats.uptimerobot.com/89VnzSKAn/796735713
updown: https://updown.io/2o5g

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.

Please consider joining the Matrix room for public instance maintainers by joining our Matrix room: https://matrix.to/#/#invidious:matrix.org then pinging @ unixfox, @ TheFrenchGhosty and @ SamantazFox for asking to be invited to the Matrix room. We discuss troubles managing a public instance, sharing some advices and more.

perennialtech commented 3 months ago

@viaguy Apologies for the delay in reviewing your instance.

I've taken a look and the instance uptime looks good. Video playback is working perfectly with your custom IPv6 rotation implementation. Nice work on this.

The announcements you've posted about instance downtime are also appreciated. As a suggestion, it could be helpful to set up a dedicated status page for your various services.

One thing to note, even though you have max-age=31536000; includeSubDomains; preload set in your HSTS header for invidious.incogniweb.net, your instance is not actually being preloaded by browsers. This is because the HSTS header needs to be set on your root domain incogniweb.net as well in order for preloading to work properly. You can find more information about this at hstspreload.org.

In any case, your instance looks great overall and ready to be added to the official instance list.

iv-org / documentation