You are not logged in.
It was completely working before there was a voltage drop that forced my router to restart (the server received new IPv4 adress). Now that I've changed the IP for all virtual servers there, everything works just fine except TeamSpeak server. It works completely fine in LAN and WLAN but is not accessible from web. All ports are right(9987,10011 and 30033), I've double-checked that with log from teamspeak and systemctl status. I didn't change resolv.conf and hosts.conf since it was working. I do have my server connected to the internet. So what is the cause and how to solve this trouble?
Offline
Are you using nat-forwarding on the router ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Are you using nat-forwarding on the router ?
It looks like I do
*it says virtual server up there
Last edited by zinstack (2017-05-13 16:38:28)
Offline
Given your description, the problem is likely in the router.
Does ftp acccess work from outside your own network ?
you may want to run network tools from clients outside the network to verify the status of the ports.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Does ftp acccess work from outside your own network ?
Yes, it does
you may want to run network tools from clients outside the network to verify the status of the ports.
nmap is saying that the 9987 is closed with dsm-scm-target service using tcp. The other two ports (10011 and 30033) are open
Offline
are all 3 ports open from within your network ?
try removing / recreating the rule for port 9987.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline