[New instance] invidious.flokinet.to

[zehkaFlokinet]

URL

invidious.flokinet.to

Mandatory checks

• Instance has a domain name
• Instance is served over HTTPS
• Statistics (/api/v1/stats) are enabled

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

Romania, Europe

Man in the Middle

Voxility, but read "Additionnal informations" section first

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

Additionnal informations

If the Voxility DDoS Filter is considered a MITM is the topic of a currently ongoing discussion in the projects matrix room.

We do not run any analytics, that's why the three "Analytics" boxes are not checked.

[TheFrenchGhosty]

Added to: https://stats.uptimerobot.com/89VnzSKAn/790271084

[unixfox]

I approve the instance request to be added.

For me, as long as it's not a protection on the layer 7 it's fine.

[SamantazFox]

@zehkaFlokinet I don't see any trackers on your site. Why did you tick the 3 checkboxes related to analytics?

[zehkaFlokinet]

I checked them because github reports 5/8 tasks done if they are not checked and i didn't know if breaks any integrations if not all tasks are marked done

[unixfox]

Don't worry with "tasks done". Can you uncheck the unnecessary items?

[zehkaFlokinet]

Done

[zehkaFlokinet]

If I'm not mistaken the month of uptime test time for this instance has passed. Unfortunately there were two small downtimes of 16 Minutes in total, but i would consider 99.963% of uptime as within the 90% limit.
I hope this instance meets your other requirements

[TheFrenchGhosty]

@zehkaFlokinet Yes, it's fine.

Can you please confirm that:

• You have an hourly instance restart setup
• The instance is ready to join the official instance list

[zehkaFlokinet]

I can't find any docs regarding the hourly restart, should i add a timer to restart the invidious service every hour?
Except that everything is ready for the official list

[TheFrenchGhosty]

I can't find any docs regarding the hourly restart

https://docs.invidious.io/Installation.md#post-install-configuration

"Because of various issues Invidious must be restarted often, at least once a day, ideally every hours."

Yes, you should definitely add something to restart it.

(I'm adding it as a "mandatory check" in the template: #195 )

[zehkaFlokinet]

Restart is now configured, we are all set

[TheFrenchGhosty]

@zehkaFlokinet Perfect! Thanks for hosting Invidious :)

[unixfox]

@zehkaFlokinet

Please double-check that you have configured hmac_key in the config file or INVIDIOUS_CONFIG then restart the instance.

You must set a random generated value for the parameter hmac_key:! On Linux, you can generate it using the command pwgen 20 1.

[unixfox]

Please consider joining our 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.

[unixfox]

@zehkaFlokinet

Hello, your instance is affected by the issue: iv-org/invidious#3822

Please have a look for a temporary solution: iv-org/invidious#3822 (comment)

We urge you to keep an eye on your instance as youtube is constantly trying to block invidious.

[zehkaFlokinet]

Hello, as already discussed on matrix we applied a workaround and have plans in case that is not sufficient

[zehkaFlokinet]

If there are future notifications please ping me on matrix as github somehow does not notify me in this thread

[unixfox]

Hello @zehkaFlokinet,

Last warning before we remove your instance. (First warning was given on matrix)

It has not been updated for a long time (the version is from August 2023).

[zehkaFlokinet]

Hey, the updater tool broke and claimed the instance up to date while it wasn't. I'have built a new updater tool and our instance is now up-to-date again and should update again