FG won't use my VPN internal ip address to connect

[Gwydion]

Morning, all. As some of you may have seen, I have been able to get AlgoVPN to work for me with Fantasy Grounds. So, I spent a few hours last night trying to go through the entire process on another laptop so I could document how to set it up for others. Unfortunately I ran into a snag that I didn't run into before.

Put simply, on the new AlgoVPN installation on my backup laptop, I can connect to AlgoVPN fine. Works like a charm. However, when I go to run a connection test in FG, it always shows my internal ip address assigned by my wireless router (Let's say 10.0.0.47), instead of the VPN network address which is 10.19.48.1. Now, when I go out to whoer.net or other location to check my ip addresses, it properly shows the external ip of the vpn for my machine and it also shows the 10.19.48.1 as another WebRTC ip address.

When I run an ipconfig /all, I see both the 10.19.48.1 for my ip address under the AlgoVPN connection and the 10.0.0.47 for my ip address for my wireless network. (And this is consistent with how it shows up on my "working" configuration). To be clear, I have set up two completely different VPN's. Meaning, on my primary laptop, the VPN installation is a separate IP with separate storage on AWS.

I'm at a loss. I don't want to go back and reinstall everything but I'm not sure what else to do. I sent the client login info to another dm and he loaded it up and had the same issue. Connected just fine, but couldn't get FG to recognize the ip address of the vpn. I've tested my original installation with another DM and it works great. Recognizes the vpn internal ip just fine.

Anyway, if anyone has any ideas to try I'm all ears. If not, I'll try to reinstall and see if I just missed something in the setup that I forgot to do. Thanks in advance!

[Trenloe]

First - it doesn't really matter what FG sees as your internal IP address if you're not using UPnP (i.e. FG is setting the port forwarding for you). FG listens for connections on all local IP addresses on the computer.

If it bothers you, look at setting the network card order in Windows advanced network card settings. https://ecross.mvps.org/howto/change...windows-10.htm But, as I say, you don't need to actually do this.

[Gwydion]

First - it doesn't really matter what FG sees as your internal IP address if you're not using UPnP (i.e. FG is setting the port forwarding for you). FG listens for connections on all local IP addresses on the computer.

If it bothers you, look at setting the network card order in Windows advanced network card settings. https://ecross.mvps.org/howto/change...windows-10.htm But, as I say, you don't need to actually do this.

Yeah, I did my thread due diligence and found you mentioning how to do that. Well... I guess I'll go back to assuming I'm done something wrong in the port forwarding. Given the vpn solution works just fine, I think that is the most likely scenario. I don't think I'll reinstall everything yet unless i just can't find my error. Thanks Trenloe!

[Gwydion]

Sigh... Nuked it... Starting over... See if I just made a simple mistake in the setup. Darn it!

[Gwydion]

So, I nuked my AlgoVPN AWS EC2 server and built everything again from scratch. Still no joy. Then I decided to go back to the basics. I looked at my windows defender firewall and realized since this is my backup laptop and I had never run an FG game from it, there weren't any rules for it. I added FG.exe and the updaters to the rules and set them to private. Then I made sure my algovpn connection was set to private. Then I launched FG again. The ip address still showed my normal internal ip, but I held my breath and ran the test. Voila! Connection successful. So, there was nothing wrong with my setup, just didn't have the firewall configured properly.

Now to test with another DM and make sure it works for them. Then I can document the whole process and post where others can try it. Nice!