docker-openvpn VS searx-docker

J'ai trouvé pour openvpn ces deux: [https://hub.docker.com/r/kylemanna/openvpn [https://hub.docker.com/r/linuxserver/openvpn-as DMAM

Else - https://github.com/kylemanna/docker-openvpn

I'm fighting a weird issue plaguing both a friend and myself. I'm using the kylemanna/openvpn docker container on the server side and whatever OpenVPN client there is on clients.

I'm using the latest kylemanna/openvpn container for the server, running on Debian 11 x86_64.

Talking with some contacts I have, right now the big ask is for secure VPNs. If you can host a server (location should be outside the US and other western countries so CSPs may by your best option) that would perhaps be the best. OpenVPN is a solid choice and there are docker images you can use to readily deploy: https://github.com/kylemanna/docker-openvpn a solution.

3 . Clone the project from this repo (https://github.com/kylemanna/docker-openvpn) with this command

When I look into vpn servers, I find easy installers, which directly work on linux (e.g. angristan/wireguard-install) or also vpns, which operate from docker (like kylemanna/docker-openvpn). Then there are options, where multiple things are included, like firezone or this. I am not so sure how well they integrate with my reverse proxy and some seem to be much more complicated than others.

I know that tunneler supports OpenVPN, so I imagine I could use kylemanna/openvpn but I can't figure out how to set it up...

I'm trying to setup an openvpn docker container in a one to many setup. I know there exist already solutions but I'm kind of scared that it hasn't been updated in a year (OpenVPN Docker Container).

I'm having the exact same issue on my Arch machine. I think this Github issue might be relevant.

I found a solution so if anyone comes across this thread with the same question here's how I resolved it. I installed Searx using the instructions found here. https://github.com/searx/searx-docker on a laptop and while the instructions got the service up and running the https cert wasn't trusted so I kept getting an error when accessing the service at https://localhost. To resolve the issue I installed Caddy. Trusted the cert, and ran the CA now I can access https://localhost and get Searx without an error. Hopefully someone with more knowledge of web services will comment on this tread and provide a more detailed expiation but here's there commands I ran on my Arch Linux install so modify to your needs. # pacman -S caddy # caddy trust

There is some extra stuff you've got to give it permission to access out of the box. You can see an example csp here https://github.com/searx/searx-docker/blob/4ad61d64991d76a7d300b7b867771ffed9f224ca/Caddyfile#L83 that will work nicely with searx itself however possibly not plugins. Your browsers devtools can be very helpful in figuring out what exactly you need to add/change if something specific is not working. Post the details of that if you are still having issues while using something like what I have linked.

I first attempted to follow the install instructions but got stuck there, and now I have tried to install with docker using searx-docker but have run into an error. Everything was going fine but when I finally try to run with the command:

I just installed a searx instance into my VPS followed the instructions on searx/searx-docker, and i have some question:

If you are not comfortable with Linux you could install Searx using Docker, it's very simple and officially supported: https://github.com/searx/searx-docker