Issues getting Port Forwarding set up

I’m having some issues with setting up port forwarding on my home desktop. I want to use it to run FoundryVTT, which uses port 30000. I recently switched to Linux, using Pop!_OS. When I previously ran Windows, I got this working without any big issues. I have the same router (ASUS RT-AX58U) as I did when it worked on Windows.
I have set up port forwarding on the router, and set my PC as a static/manual IP. I also enabled UFW and the terminal and set up an allow rule for 30000 there.

I still can’t get it to work and haven’t been able to find any advice anywhere that could point me in the right direction.

Any help would be greatly appreciated!

1 Like

So I actually run a FoundrVTT server on a ubunutu VM. You need to verify and make sure you forwarded port 30000 on TCP. You can run sudo ufw status. If you need to set it as TCP you can remove the rule that you’ve created and set the new one like sudo ufw allow 30000/tcp. If its still not working make sure to verify your PC has the correct IP address and it lines up with what is on the routers port forwarding rule.

If you ever decide you would want to host Foundry 24/7 on server this is a pretty decent guide: Recommended Linux Installation Guide | Foundry VTT Community Wiki

I’ve spun it up on a VPS before and it worked pretty well. Just make sure not to host any private data on the VPS or to try an contain any issues with a VM as it’s not the most secure.

1 Like

How exactly? Did you open 30000 explicitly on the router, or did you use some ‘automated’ thing like UPnP?

Here are images both from the router and the ufw settings.

Screenshot from 2025-01-08 23-19-48

Friend tried the same on his Ubuntu system, makes me think this is more likely to be a router issue…

1 Like

Hmm, that all looks ok.

Maybe a stupid question, but you can access this on your local machine on 127.0.0.1:30000? And also on 192.168.x.x:30000, from the local machine or another one on your network?

Is there any setting on this app which IP it listens to? Is that set to 0.0.0.0?

I tried in my browser to connect with both 127.0.0.1:30000 and 192.168.x.x:30000 and they worked.

Not sure what you mean with the second part :sweat_smile:

An application can ‘listen’ to connections to a certain port, in this case 30000, so it can receive incoming packets. But it does not have to ‘listen’ on any IP; 127.0.0.1 is the ‘localhost’, i.e. the IP address your PC can use to connect to ‘itself’, whereas 192.168.x.x is the IP on the LAN. Some apps by default only listen on the localhost, but not on any IP assigned to the PC.

0.0.0.0 is a catchall for ‘any ip’

But if you can connect via 192.168.x.x:30000 that setting should be fine.

Does 192.168.x.x:30000 also connect from another PC or phone on your local network?

Yes, phone can connect while on WiFi.

Hmm, then it must be the router… The setting looks OK though. Has the IP perhaps changed after switching to linux? Try a reboot?

I did try to reboot the router already, without any change. I wonder at this point if I need to do a factory reset on the router…

what kind of network is the router connected to?

Um, what do you mean? (Networking is not my strong suit…)

what is the wan port plugged into in this case? who is your network provider? what gateway address does the router have? how are you checking if the port is properly forwarded?

The router is connected to a provided Fiber switch.
I use a local network provider (“mediateknik dot net”).
I’ve used “canyouseeme” to check the port.

Ok so I’m going to ask a dumb question but based on your responses, im guessing english is not your first language. Are you sure its a ‘switch’ and not like a modem? What do you believe your gateway is? You dont have to post it here if you dont want to but it sounds a lot like you might have double NAT going on. Knowing what your gateway IP is, even just the first 2 octets, would help.

You can DM your IP or post it and edit the post later to remove if that is preferrable.

I’m living in Sweden. Yeah, modem is most likely what it is (never remember the difference on modem/router/switch, lol).
Gateway: 10.192.48.xxx

so anything 10.xxx.xxx.xxx is going to be a class A private addressing scheme, similar to what you use internally.

172.16-32.xxx.xxx is class b
192.168.xxx.xxx is class c

These are used to translate a single public IP address to many internal addresses without having to give every device its own public IP.

It would not be possible for me to reach your computer using this addressing scheme.

You should be able to google ‘what is my IP’ and see your public IP information. This is what you would test against, but in this case, you probably wont find an open port there either. It could be the case that you should have a public IP but something is misconfigured on your ‘modem’. I’m still not fully sure.

Here in the US I have AT&T fiber, and I have to use their combo AP/modem thing to pass the public IP to my opnsense router in order to not have double NAT and forward ports.

1 Like

Are you in an apartment building or is this a house?

If you can take a picture or give a model number of the fiber device that might help explain as well.

I really need to head to bed now, but will respond again tomorrow! Thanks for the help so far!

1 Like