Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New instance] inv.oikei.net #495

Closed
8 of 11 tasks
notyuuko opened this issue Jan 23, 2024 · 4 comments
Closed
8 of 11 tasks

[New instance] inv.oikei.net #495

notyuuko opened this issue Jan 23, 2024 · 4 comments
Assignees
Labels
instance-add passed-checks Passed the required manual checks for a public instance passed-uptime Uptime good after 30 days

Comments

@notyuuko
Copy link

URL

https://inv.oikei.net

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)

Maintainer chart

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

Host country

Germany

Man in the Middle

No response

Source code URL

No response

Analytics

  • They are GDPR/CCPA compliant
  • This is stated in your Privacy Policy
  • You have provided the source code's URL in the dedicated field above

Additional information

I havent set up the ipv6 rotator yet.

Copy link

Hello! Your instance has been added to our monitoring system: https://stats.uptimerobot.com/89VnzSKAn/796235506
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:

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.

@github-actions github-actions bot added the wait-30-days Wait 30 days good uptime label Jan 23, 2024
@perennialtech
Copy link
Collaborator

@notyuuko Any update on setting up the IPv6 rotator?

A few other things:

  • Your instance a bit out of date at the moment (2024.02.19-e8a36985, whereas the latest version is 2024.03.08-99a5e9c). If you're using Docker, you can use something like Watchtower to automatically update Invidious to the latest image.
  • While it's not required, you may also want to remove the X-XSS-Protection header, since it's been deprecated for a while now and no modern browser supports it.

Other than that, your instance looks fine to added to the list.

@perennialtech perennialtech added the passed-uptime Uptime good after 30 days label Mar 16, 2024
@notyuuko
Copy link
Author

notyuuko commented Mar 16, 2024

@notyuuko Any update on setting up the IPv6 rotator?|

yep, i set it up on the instance already

Your instance a bit out of date at the moment

updated it to latest

While it's not required, you may also want to remove the X-XSS-Protection header

thanks for the notice, disabled it

thanks

@github-actions github-actions bot removed the wait-30-days Wait 30 days good uptime label Mar 16, 2024
@unixfox unixfox reopened this Mar 16, 2024
@perennialtech perennialtech added the passed-checks Passed the required manual checks for a public instance label Mar 20, 2024
@perennialtech
Copy link
Collaborator

@notyuuko I've added your instance to the list, but you should still address a couple other things:

  • You haven't actually disabled the X-XSS-Protection header entirely. Instead, you're setting the header twice, once with 1; mode=block and the other with 0. Since you're using nginx, you might find the more_clear_headers directive, part of the ngx_headers_more module, useful.
  • You should also enable HTTP/2 and HTTP/3 on your instance to improve its performance.
  • If you haven't already, see the Improve your public instance performance and stability page on the Invidious docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
instance-add passed-checks Passed the required manual checks for a public instance passed-uptime Uptime good after 30 days
Projects
None yet
Development

No branches or pull requests

4 participants