[New instance] invidious.catspeed.cc

[mooleshacat]

URL

https://invidious.catspeed.cc (CA)

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

Canada

Man in the Middle

No response

Source code URL

https://github.com/catspeed-cc/invidious

Your matrix username

@mooleshacat:matrix.org

Additional information

• clone of iv-org/invidious
• revert iv-org/invidious@d9df90b
• added an http-proxy patch.
• added separate donate link for catspeed.cc
• added link to FreeTube config help page
• instance uses vpn rotator script & po_token script

confirmed playback is working 👍

[github-actions]

Hello! Your instance has been added to our monitoring system: https://updown.io/cr5y
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.

[mooleshacat]

Thanks, bot 👍

Just an additional note; I set up the http3-ytproxy but did not notice the setup was failing. Playback worked for me but not someone else.

I removed http3-ytproxy from configuration and playback is now working. This must have been some configuration issue on my part.

[mooleshacat]

Someone on the matrix was able to figure out what the diff was (pun intended)

I can confirm that by applying this patch I can once again browse videos. Someone was critical of it saying it was a minor change and it couldn't fix it, but it did fix it. I had a problem loading any video on any IP even with a VPN.

fix-please-login.patch

Apparently it is a revert of iv-org/invidious@d9df90b

It worked for me, as well as at least 1 other person.

[mooleshacat]

Everything is working again 👍 I have my vpn rotator and po-token scripts completed.

I had to go back to the start, clone iv-org/invidious and revert iv-org/invidious@d9df90b then add an http-proxy patch.

[mooleshacat]

I have an IPV6 outage. My IPV4 is working though. If it is possible, it'd be nice to monitor the IPV4 instead.

[unixfox]

If you have an IPv6 record then it's going to be monitored. If you do not then it's not going to be monitored. Simple as that.

Same goes for IPv4.

Both protocols are monitored if they are available.

[mooleshacat]

Ok perfect.

I sorted connectivity issues out

[unixfox]

Hello, we had to remove your instance due to being down since a few days. Please get back to us once it is fixed and we will add it back again.