January 23, 20251 yr I have an Unraid 7.0 installation and want to create the 4Get search engine with GluetunVPN, as Space Invader also shows. I get the GluetunVPN CA app to work and can route Firefox through it confirming that GluetunVPN works. When I install 4Get CA app, it also works. However, when I route the network through the GlutunVPN, I can see in 4Get's console that Mullvad's IP address is being used, but I cannot access 4Get's website. I added the port 280 to the GluetunVPN docker. I don't know how to get it working. I also linked Gluetun to my Tailscale network and set it as an exit node, if I don't route 4Get through the GluetunVPN and also link it to Tailscale, again i can't open the webgui. I am a bit at my wit's end....
January 23, 20251 yr 24 minutes ago, groetg said: I am a bit at my wit's end Can you please link the video that you've watched from @SpaceInvaderOne please? Some screenshots from your configurations in the templates would also help.
January 23, 20251 yr Author 40 minutes ago, ich777 said: Can you please link the video that you've watched from @SpaceInvaderOne please? Some screenshots from your configurations in the templates would also help. https://youtu.be/AnhwoARGNzo?si=p9OlSCq3MuGsa5ps
January 23, 20251 yr Just now, groetg said: https://youtu.be/AnhwoARGNzo?si=p9OlSCq3MuGsa5ps Do you also have Screenshots from your template? This would make troubleshooting a lot easier.
January 23, 20251 yr Solution Just now, groetg said: Like this? First of all please disable Serve everywhere, did you watch the video all to the end? Serve doesn't work for this container in the default configuration. After you disabled Serve everywhere try to connect through a device that is able to access your Tailnet and connect with http://<4getTailnetIP> (please note that no port is needed because it uses port 80 internally and also that you have to use http:// not https://) Do you need Serve for GlutenVPN too? I would recommend that you don't enable Serve where you not need it.
January 24, 20251 yr Author I watched it. I deleted /mnt/user/appdata/gluetun/.tailscale_state and than rebuild the docker. After that it worked. After Gluetun was working, it was easy to deploy 4Get and all is working now. I just have one wish: to use NextDNS in Gluetun, but I have read that is not possible until some DNS issue is fixed?
January 25, 20251 yr 21 hours ago, groetg said: After Gluetun was working, it was easy to deploy 4Get and all is working now. If you update the 4Get container it should now be possible to use Serve if you only have http enabled in 4Get.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.