Add https://search.rabbit-company.com

[zigazajc007]

General

• [X] It is my instance.
• [X] I give the right to check.searx.space to check my instance (every 3 hours for the response times, every 24 hours for the other tests).

Bot protection

Yes, I have installed filtron (rules.json from searx-docker).

Source code URL

No response

Comment

No response

[zigazajc007]

I have just notice that additional https:// is added in the url by default.

[zigazajc007]

It seems that in docker-compose.yml file https:// needs to be removed.

[tiekoetter]

I can't connect to your instance.

ERR_CONNECTION_REFUSED

[zigazajc007]

I'm trying to solve error above. So I'm restarting the containers.

[tiekoetter]

Could you share your Morty config?

[zigazajc007]

Where is Morty config located? Inside Morty container?

[tiekoetter]

No I mean where you hook Morty into SearXNG.

[zigazajc007]

I have used default docker-compose.yml file.

[zigazajc007]

https://github.com/searxng/searxng-docker

[zigazajc007]

Images from Morty are working if I remove https// from the url.

[tiekoetter]

How did you configure Morty in your Webserver?

What do you want to use Morty for? If you only want an image proxy you can ignore morty and use the internal image proxy.

[tiekoetter]

https//

This is not a valid prefix why did you add it?

[zigazajc007]

The problem is that I didn't add that. It appeared there by default. I would need to take a nother look just to make sure everything is okay.

[tiekoetter]

What webserver are you using in front of your instance? Also please share how you have added Morty there.

[zigazajc007]

https://github.com/searxng/searxng-docker/blob/master/docker-compose.yaml

I have the same docker-compose.yml file. Morty is by default included there.

[tiekoetter]

ping @unixfox

[zigazajc007]

Morty seems to be working fine. But SearXNG sends wrong URL.

https://search.rabbit-company.com/morty/?mortyurl=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fthumb%2F3%2F34%2FIkesbunny.jpg%2F500px-Ikesbunny.jpg&mortyhash=b664ed5acbbaf1b0e5e2fbed9202c1ae4b7a81416909417f2306bd429f51b439

Morty has image located in the correct url.

But SearXNG ask for the image on wrong url:

https://https//search.rabbit-company.com/morty/?mortyurl=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fthumb%2F3%2F34%2FIkesbunny.jpg%2F500px-Ikesbunny.jpg&mortyhash=b664ed5acbbaf1b0e5e2fbed9202c1ae4b7a81416909417f2306bd429f51b439

Like this https// should be somehow removed. I don't know if this is possible thru config files or it's hard codded inside docker container.

[zigazajc007]

This problem has been temporarly "solved" by disabling Morty and image proxy.

[unixfox]

If you found a bug in searxng-docker then please create an issue there: https://github.com/searxng/searxng-docker/issues

[zigazajc007]

So my instance is good even without Morty?

[unixfox]

I don't think we ever refused an instance that is not using morty so I guess if you configured correctly your filtron rules we will add your instance.

[tiekoetter]

@zigazajc007 Have you tried using the integrated image proxy to at least get the images proxied?

Regardless I also see no problem adding your instance. Please confirm that you are ok with it.

[zigazajc007]

Morty was working and images was proxied. It's just that SearXNG instance tried to retreive images from the wrong url. When I have tried correct url manually it worked.

Yes, you can put this instance as public.

[return42]

@zigazajc007 please update your instance.

[zigazajc007]

@zigazajc007 please update your instance.

Updated

[unixfox]

Hello @zigazajc007,

This is a friendly reminder that your provider hetzner offer IPv6, it would be great if you could add IPv6 to your instance.

It may be not difficult at all, you may already have IPv6 connectivity on your server, all you need is to add a record AAAA in your DNS server.

Here is the documentation here: https://docs.hetzner.com/cloud/servers/primary-ips/primary-ip-configuration/

The future of the internet will thank you, see why here.

[zigazajc007]

Hello @zigazajc007,

This is a friendly reminder that your provider hetzner offer IPv6, it would be great if you could add IPv6 to your instance.

It may be not difficult at all, you may already have IPv6 connectivity on your server, all you need is to add a record AAAA in your DNS server.

Here is the documentation here: https://docs.hetzner.com/cloud/servers/primary-ips/primary-ip-configuration/

The future of the internet will thank you, see why here.

I'm not sure if it's as straightforward process as it seems.

Especially as SearXNG runs inside Docker and behind Nginx Proxy Manager.

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1606

So there are multiple parts that still might not have good IPv6 support.

[return42]

@zigazajc007 FYI your instance has not been updated for a while / its recommended to update regularly.

[zigazajc007]

@zigazajc007 FYI your instance has not been updated for a while / its recommended to update regularly.

Updated

[unixfox]

Please consider joining our Matrix room for public instance maintainers by joining our Matrix room: https://matrix.to/#/#searxng:matrix.org then pinging @\unixfox, @\dalf and @\mrpaulblack for asking to be invited to the Matrix room. We discuss troubles managing a public instance, sharing some advices (like how to protect against bots), announcing big changes in searxng and more.

[unixfox]

A new big change has been introduced 🎉!

Please read this documentation for how to proceed: https://gist.github.com/unixfox/4e22730769540fe5b9f1943a86439761

We are going to make mandatory this new parameter by 1st December 2023. Any instance that do not have this parameter enabled won't be allowed in the public list anymore.

We can make exceptions in case you really do not want to enable our bot limiter solution, but you will have to send us proofs: clearly stating how you detect bots, how you actively deal with them and also prove that it really works.

Feel free to ask here if you have any troubles setting up this new parameter.

[unixfox]

@zigazajc007 Important step above! The deadline has already passed, if you do not conform we will have to remove your instance by the end of the year.