-
Notifications
You must be signed in to change notification settings - Fork 67
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
installing searx with https on a different port #39
Comments
Have you had any luck? I have been trying to figure this out too. |
Nope, not with this container/package. I compromised with installing another searx container (wonderfall/searx) which allows you to switch ports as described above and very easily, but lacks the SSL layer. I don't expose that port to internet and make it only available within my LAN. This was the solution I settled with, I hope it helps. |
Since the commit bdf5619 this solution should work:
See https://caddyserver.com/docs/caddyfile/options No need to modify docker-compose.yml , because of searx-docker/docker-compose.yaml Line 8 in bdf5619
|
Thank you @dalf. This is now resolved. |
Hi,
I apologize in advance if this is a silly question, but what I am trying to do is installing searx container to be reachable from outside world by https from a non-conventional port. To accomplish this, I copied the docker-compose.yaml file to docker-compose-extend.yaml file and edited the caddy ports section to read as follows:
Host machine firewall was set to allow access to the ports 25000 and 25001 via tcp. The edge router was also set to forward ports 80 and 443 to 25000 and 25001 respectively on the host machine.
Then I tested these settings by running start.sh which reported that Letsencrypt could not access the ports for certification.
What am I missing?
Thanks for the pointers in advance!
The text was updated successfully, but these errors were encountered: