[New instance] inv.thepixora.com

[mv12star]

URL

https://inv.thepixora.com

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

Netherlands Canada

Man in the Middle

CloudFlare (reverse proxy)

Source code URL

(Not modified)

Additional information

• Deployed 29th Dec 2025
• Uptime (for tracking the next 30 days): https://inv.thepixora.com/uptime
• Source code not modified
• Proxying disabled for the foreseeable future (cloudflare TOS)

[github-actions]

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

[unixfox]

Hello,

Please read the comments including this one and after this one: #625 (comment)

Once done. Please confirm you have anti bot protection and rotating proxy.

Thanks.

[mv12star]

@unixfox

• Comments read.
• AI bots are currently being blocked with Cloudflare, however I do not wish to use a PoW-based or other invasive captcha system like Turnstile, Anubis, or go-away. My server can handle large amounts of traffic without any issues, including bot traffic.
• I also have an IP rotating solution implemented.

Thank you.

[unixfox]

You need to implement a verification page with tools like anubis, go away, or cloudflare verification page itself.

Because the traffic from bots you are going to receive will be high enough for youtube to almost instantly block each of your rotated IP. This might not be an issue for the first few months but it will definitively be one after a couple of months that your instance is in the list.

Moreover, I can see that the videoplayback features are reduced compared to the Invidious default ones. I'm unable to use DASH and so get high quality videos. I'm reluctant on adding your instance because of that. Youtube is moving fast and there is a chance that non DASH videoplayback will stop working at some point, and with your instance too in this case.

Are you aware that you can host companion on a separate domain/server: https://github.com/iv-org/invidious-companion/wiki/Setup-Invidious-companion-on-a-separate-subdomain-server? This way you can host companion without cloudflare enabled and not breaking their TOS.

[mv12star]

Hey @unixfox ,
I am not really liking the path this is taking.

Invidious is an open source project and has several different selfhosting options available. Hence, the admin of each instance should be the once deciding their own config, not the project maintainers.

You need to implement a verification page with tools like anubis, go away, or cloudflare verification page itself.
[bot traffic] might not be an issue for the first few months but it will definitively be one after a couple of months that your instance is in the list.

Your comment almost looks like you are saying "add DASH, proxy videos, and add a bot protection". And what if I do not want to add it? In the end, it is up to me. Adding all these measures without even having a decent userbase, sounds pretty pointless to me.

Moreover, I can see that the videoplayback features are reduced compared to the Invidious default ones. I'm unable to use DASH and so get high quality videos. I'm reluctant on adding your instance because of that.

If you are reluctant to add my instance, then don't add it, but the only thing I can call that decision is selfish. Nowhere in the docs does it say "if you do not use X config, your instance will be rejected". Prove me wrong. The only requirements are the mandatory checks above, and a 30 day uptime.

So please reconsider your previous comment, and let me handle my instance configuration according to my own views.

Thank you.

[unixfox]

Like I said to Nescape7 in this comment: #625 (comment)

Well it's quite simple, if your instance works, we keep it on the list. If your instance stop working, we remove it.
Up to you to manage it so that it keeps working. I'm only warning you on the possible outcomes.

I'm not trying to wind down your arguments, we both want that your instance perform well under load and when being visited by many visitors.

By my previous message, I'm sharing suggestions based on my experience managing all the public Invidious instances and managing https://yewtu.be. I very well know that without any antibot, your instance will stop working after a month or earlier than that. We had such case of a few recent Invidious instances, example: #625 (comment)

But if you really want to go without an antibot, you can. Be aware of the consequences that I have explained.

About non DASH usage only (so only 360p), well even if it's not in the rules (because we didn't think of that), you do not offer a good experience to your users with only 360p. This is why I'm complaining about this restriction and offering suggestions (companion on a separate domain).

Moreover, you are taking a huge risk because YouTube is moving to a future video streaming called SABR so based on my experience, your instance could stop working altogether because YouTube could decide to remove 360p only quality since they have their new video streaming feature now.

All in all, yes if you pass the 30 days period, your instance is eligible to be added and kept in the list as long as it keeps working.

---

The rules are quite outdated, they date back before it was very difficult to host a public Invidious instance, so please take into account that things have vastly changed and that I'm not saying things for nothing.

[EnvixityB02]

oh hey an instance that works in yattee! thank you!

[mv12star]

@unixfox The instance has been fixed and video playback works again, it now supports DASH usage :)

Uptime nearly 100% as you can check here https://updown.io/y3lz and here https://stats.uptimerobot.com/Ou96B6HA1B. It has been up for 60 days now.

Feel free to add my instance to the public list. I have read the rules and I think I comply with all of them.

Note about rule 14: A visual or JS-based antibot/captcha is currently not in use, but I have configured measures against malicious bot activity through the cloudflare WAF, with a ruleset that I shared in Matrix.