The Popular is enabled popular_enabled: true

But displays no videos: https://ytb.trom.tf/feed/popular

This isn't a bug, you have nobody registered on your instance (see usage.users.total from https://ytb.trom.tf/api/v1/stats) so Invidious can't generate a list of popular channel from registered users. See this file for the actual implementation of the code of the popular page: https://github.com/iv-org/invidious/blob/master/src/invidious/jobs/pull_popular_videos_job.cr

Bump still important feature.

Still relevant but it will soon be fixed.

Reopening as the PR is not yet merged.

Can you check if this PR solve the issue: https://github.com/iv-org/invidious/pull/2255?

Still an important modification to be done for big clusters.

Still important but it is soon going to be resolved thanks to the recent IPv6 support in k3s.

Still happen.

Bump

Searx is usually run behind a reverse proxy, so you must configure your reverse proxy to forward the given client IP address by cloudflare to Searx.

In no way, this is Searx fault.

@frasersdev Created an issue instead

Discussed in https://github.com/searx/searx/discussions/2913

<div type='discussions-op-text'>

^{Originally posted by frasersdev July 29, 2021} Hi,

Brand new install shows a google images engine crash. A lot (but not all) of the public instances show the same thing.

Actual error is an index error.

is this a known issue or is there configuration I need to tweak?

</div>

/remove-lifecycle stale

We recommend using postgres 10 instead.

On Chrome (Vivaldi) with searx as default engine, a query in the address or query field opens the searx page but with an empty search field

in testing on https://test.invidious.io, along with #2277 and #2217

NB: I had to do some minor changes to make it work

Feel free to modify my PR according to #2277. You can modify the code of my branch by cloning my github repo.

No I didn’t, could captchas be the reason for that behavior ?

Probably, every public instances have anticaptcha enabled due to the very likely possibility of generating way more traffic than usual.

Did you setup an anticaptcha system on invidious?

Extracted/formatted the interesting part of the error message. Looks like a youtube change:

Missing hash key: "url" (KeyError)
 from /usr/share/crystal/src/hash.cr:1030:9 in '[]'
 from src/invidious/comments.cr:576:71 in 'content_to_comment_html'
 from src/invidious/comments.cr:539:43 in 'parse_content'
 from src/invidious/comments.cr:149:69 in 'fetch_youtube_comments'
 from src/invidious.cr:2079:18 in '->'
 from lib/kemal/src/kemal/route.cr:13:9 in '->'

That's why #2217 is here but there still some remaining bugs to find.

We will probably need android embed too in order to solve the throttling issues and directly decrypt the encrypted video streams.

Related to https://github.com/iv-org/invidious/issues/2189#issuecomment-887253427, we will need to manipulate the context.

Firstly thanks for a great project.

Is your feature request related to a problem? Please describe. This relates to the entire application stack, not just the searx project. Not sure where to place such an item.

Filtron doesn't support ipv6. https://github.com/asciimoo/filtron/issues/19

My hosting setup uses nginx revproxy (+ optionally varnish) as a frontend and application / webservers as a back end. ipv4 terminate on the rev proxy the backend is pure ipv6 there's firewalls etc between everything along the way.

based on your architecture https://searx.github.io/searx/admin/architecture.html I was expecting searx to fit in well. however the lack of ipv6 support of filtron meant that the nginx frontend couldn't communicate with the backend.

Describe the solution you'd like filtron should support ipv6 as its an internet technology.

Describe alternatives you've considered I think I can do a lot of what filtron is doing directly in nginx. it supports rate limiting and responses based on user agent.
This makes me wonder if filtron can be dropped entirely from your application stack. Thats the path I'm going to take anyway since filtron is a no go for me. varnish will be useful for the static content too.

Additional context not sure what you'd need but happy to provide more info. All the other components can operate with ipv4 or ipv6. I have nginx connecting directly to searx on an ipv6:8888 and its working well.

Closing as one issue on the filtron github repo is enough. Even if filtron was designed to protect searx, searx the program itself doesn't need filtron to function so this enhancement has nothing to do on this github repo.

@unixfox It could work for master yes, but not for PRs sadly. If it's done this way PRs shouldn't be build on Nightly.

We can have both. Ran on PRs and master, I think that's fine. I don't see any issues. We would be testing the working code and the future improvements to the code.

Is CI able to restart itself when Nightly update?

I don't think so, so in my opinion it's pointless to have a build on nightly since it will only be the nightly of the day of the last commit.

(I maybe don't get the point of this PR though, but from what I understand you want CI to build on 1.0.0/1.1.0/Nightly)

An easy fix would be to use cron in order to build invidious with nightly every day.