Replies: 3 comments 7 replies
-
VPN port forwarding means you can access it through http://vpnip:forwardedport you can't access it on your LAN or router. Try with |
Beta Was this translation helpful? Give feedback.
5 replies
-
Hi Quentin,
Thank you *very much* for the information. I wrote up a reply last night
(when I tested 3.20.0) but it looks like I didn't submit it. I didn't have
any luck with that version either.
I took your Docker statement and modified it for my configuration.
```
docker run --rm --cap-add=NET_ADMIN \
-e VPNSP=mullvad \
-e USER=accountnumber\
--name=gluetun \
-e SERVER_HOSTNAME=us-phx-004 \
-e FIREWALL_VPN_INPUT_PORTS=56386 \
-e PUID=1027 \
-e PGID=100 \
-v /volume1/docker/gluetun/config:/gluetun \
qmcgaw/gluetun
```
There were some differences from what I was using before. I was using
*OPENVPN_USER* instead of* USER*. I was also setting *OPENVPN_PASSWORD *to*
m *as I had seen on several posts.
Unfortunately, I still was unable to connect.
[image: image.png]
[image: image.png]
Port forwarding rule
[image: image.png]
I attached my gluetun run log.
Thank you again for your help with this. I do appreciate it. I am going to
keep trying. It's definitely something on my end.
Thanks,
Erick
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi Quentin,
Thank you so much for your detailed reply and assistance. I appreciate it.
So I found a couple of mistakes on my side.
1) I reread the Mullvad port forwarding page and something glaring jumped
out at me
[image: image.png]
I had mistakenly chosen a key to associate with it and I shouldn't have.
Because of OpenVPN, I should have selected "No Key".
[image: image.png]
2) I still was having an issue after this and I found one other problem
(and this one is *really dumb*, my apologies for wasting your time).
I was starting port checker with an SSH shell to my Synology itself.
It then all of a sudden hit me that it was not running within the container
itself and of course it would not be accessible from the outside world.
As soon as I launched a shell within gluetun and ran port checker there,
all was good!!!
Very lame on my part. Sorry about wasting your time on that. Because of
that, I sent you some money via Paypal to go buy yourself a beer or
something.
[image: image.png]
Thanks again. Now on to the fun stuff!!
Appreciate it. Have a good day.
Erick
…On Thu, Jul 29, 2021 at 5:49 AM Quentin McGaw ***@***.***> wrote:
I looked at the logs a bit more in depth and noticed some items related to
the TUN interface.
That's all good. Gluetun manages to create it. If you want you can map the
/dev/net/tun device but it doesn't really change anything. Soon Gluetun
will create wireguard devices too, so no need to worry on that one 😉 I
might remove the warning as it's misleading today.
USER is the old variable I still use for dev for some reason I guess
because it's shorter.
Setting an openvpn password for Mullvad is ignored anyway since there
isn't one.
Are you sure you use the same SERVER_HOSTNAME as your port? Since now
Mullvad forwards a port for a particular server location, you need the
hostname to match that location.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#545 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMWSQU2JF6QXRQDB5S5L5DT2FE4XANCNFSM5BDE4HEA>
.
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I'm hoping that someone can assist me with a port forwarding issue that I am having. I'm sure that it's a configuration issue on my side that I am simply missing.
The Docker container is running on a Synology NAS. My VPN provider is Mullvad.
I have setup gluetun and here are some of the parameters I have been testing with:
CITY - Two different servers, one US, one Sweden
SERVER_HOSTNAME - Two different servers, one US, one Sweden
PORT_FORWARDING (tested with both ON and OFF)
FIREWALL (tested with both ON and OFF)
FIREWALL_VPN_INPUT_PORTS, two different ports. One for each server.
Note that I am only setting one server and one port at a time. I tested with two different servers to see if it was a server issue.
I can post logs if necessary but I don't see any errors in the log. The container is assigned an address from Mullvad (I obfuscated for posting).
I checked the IP address in the container (via a shell) and it is the VPN Address. I have also forwarded the VPN port in my router to the Synology.
I setup the port checker and am not seeing any hits and the browser fails to connect as well.
Any suggestions on what I can check or try next?
Thank you,
Erick
Beta Was this translation helpful? Give feedback.
All reactions