-
Notifications
You must be signed in to change notification settings - Fork 337
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Nginx instead of Caddy #15
Comments
Good day. I think this link has a good example of how to use nginx instead of Caddy. |
The link doesn't direct to anything EDIT: link has been fixed by @return42 |
Forgive me, this was the first time I've used the "link" feature on github website. nginx:
container_name: nginx
image: lscr.io/linuxserver/nginx:latest
ports:
- 80:80
- 443:443
volumes:
- ./config:/config
restart: on-failure and using this nginx config
|
Hi, did you change the filtron's rules.json to disable protection according to issue #63? Does this mean that along with #14, we lose both morty and filtron protection? |
You dont need filtron and morty anymore. We switched our stack to using the limiter plugin in SearXNG core and the image_proxy feature also in SearXNG core. Our stack now consists of SearXNG, redis and any reverse proxy. Can you leave a quick comment if the nginx config worked for you, so I can close the issue? Thanks :D @pleasehelp111 I edited #15 (comment) so there are proper coding blocks... Hope that is ok 👍 |
Thanks @pleasehelp111 @mrpaulblack . Unfortunately, I was not able to use searxng with nginx successfully by:
I'm sorry I cannot provide more information, as nothing was in the docker log. |
@extremelyonline try this NGINX config configured to work with the SWAG docker container:
|
you dont even need to use the container IP. You can use the container name and docker will automatically resolve the name to the container IP 👍 So for example if you named you SearXNG container |
Since OP is using SWAG, this suggestion will only work if the SearXNG container is running on the same docker network as SWAG and will require the addition of this line to their proxy conf:
|
Got it working now! I was having a DNS issue. I changed the SWAG subdomain.conf template to match the searxng container. Haven't tested the subfolder method. |
You can use mines, It takes about 5 mins to setup and you have a fully working harden search engine for public and private use. With A+ Ratings already bulit-in for you to check your instance for security audits... https://github.com/WhateverItWorks/my-SearXNG-Docker-Compose |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Is there an easy way to use Nginx?
The text was updated successfully, but these errors were encountered: