ts3 server not visible to internet

pousoupoux

New Member
Jul 14, 2022
6
0
1
Hello, i would like to start off with a disclaimer saying i am a total noob when it comes to networking. I am just starting my journey into this field so apologies for any stupid settings/mistakes you may see.

i have proxmox in bare metal in an old pc of mine and from there i successfully created 2 VMs. 1) debian 11 and 2) win 10.
in the debian one i have downloaded the ts3 server .sh and i left it running.

i then port forwarded to my proxmox host ip (192.168.2.100) on my router page the necessary ports and visited canyouseeme . org to see if the server is visible. well it wasn't.

So i changed the etc/network/interfaces file to this:
Bash:
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
    address 192.168.2.100 (static ip of proxmox host)
    netmask 255.255.255.0
    gateway 192.168.2.1 (my router)
    bridge-ports vmbr0
    bridge-stp off
    bridge-fd 0

with ip a yielding:
Screenshot at Jul 14 23-49-59.png

please help me

EDIT 1: ok this is really weird. without touching any settings i could see tcp port "30033" open for a moment but not the other 2 (tcp 10011, udp 9987). now everything is closed again

EDIT 2: i will provide you guys with a screenshot of both my host's firewall and VM's
Host:
my_firewall.png

Debian VM:
deb_fireawll.png
 
Last edited:
i then port forwarded to my proxmox host ip (192.168.2.100) on my router page
if you want to use the server on your vm, you have to port forward to the VMs ip, not that of the PVE server

also, the firewall rules seem weird, you shouldn't use the 'source port' field in that case (thats not how that works)
 
  • Like
Reactions: pousoupoux
if you want to use the server on your vm, you have to port forward to the VMs ip, not that of the PVE server

also, the firewall rules seem weird, you shouldn't use the 'source port' field in that case (thats not how that works)
oh, so every vm is its own entity in my network? i thought they all were communicating through the pve server. and that's why i did that.

regarding firewall rules now, what interfaces should i put where (if i have to) and why the source port should be empty?
 
oh, so every vm is its own entity in my network?
yes

regarding firewall rules now, what interfaces should i put where (if i have to) and why the source port should be empty?
i think you can completely omit the rules for the host (the host firewall does not interfere with vms in any way)

the source port should be empty since in most connections, the source port will be randomized when some client connects to your service, only the target port is relevant
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!