Can't connect via public ip
Options
Modemi4
✭
Hello. I can't connect to my server via public ip, but it works well for localhost or with devices in the same local network (on port 9090, is this ok? Not sure why).
My server pc is connected directly to ethernet cable with no routers, has firewall disabled and public ip selected in the tray, BUT i still get Client: Error: 1004 Master peer error timeout on connecting
I can ping my public ip with no problems from own or other devices
No logs on server appear on my attemts to connect
But there are suspicious logs on start, like:
Please check full logs: https://drive.google.com/drive/folders/1zCfysYkJLRNuERyy95UDrYHO2mNGjE3d?usp=sharing
I will appreciate an answer in the shortest time, because till Monday everything has to be working
My server pc is connected directly to ethernet cable with no routers, has firewall disabled and public ip selected in the tray, BUT i still get Client: Error: 1004 Master peer error timeout on connecting
I can ping my public ip with no problems from own or other devices
No logs on server appear on my attemts to connect
But there are suspicious logs on start, like:
CTCPWebSocketServer::OnError() - TAsyncSocket::Shutdown() - An existing connection was forcibly closed by the remote host.
Please check full logs: https://drive.google.com/drive/folders/1zCfysYkJLRNuERyy95UDrYHO2mNGjE3d?usp=sharing
I will appreciate an answer in the shortest time, because till Monday everything has to be working
0
Answers
-
Another interesting line in logs:
Photon.LoadBalancing.Common.NodesReader - Internal address for node 0 unknown; using loop back
0 -
I can "ping" my public ip from other machine but telnet xx.xx.xx.xx 9090 gives an error, if ip is public0
-
@chvetsov
Thanks. That is how port 9090 is described in cmd:Can not obtain ownership information TCP 0.0.0.0:9090 0.0.0.0:0 LISTENING
I'm still pretty sure that this is a listener run by Photon, because it appears only once I start the server
But if I try to listen this port by telnet or from browser it doesn't respond
Just in case, the other listeners related to Photon:[PhotonSocketServer.exe] TCP 0.0.0.0:943 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 0.0.0.0:4530 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 0.0.0.0:4531 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 0.0.0.0:5040 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 0.0.0.0:9091 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 127.0.0.1:4843 0.0.0.0:0 LISTENING [PhotonSocketServer.exe] TCP 127.0.0.1:63342 0.0.0.0:0 LISTENING [PhotonControl.exe] TCP 192.168.1.3:63210 104.45.24.151:80 ESTABLISHED [PhotonControl.exe] TCP 192.168.1.3:63214 192.168.5.10:80 SYN_SENT [PhotonSocketServer.exe] TCP 192.168.1.3:63224 131.253.33.200:443 ESTABLISHED [PhotonSocketServer.exe] UDP 0.0.0.0:53472 *:* [PhotonSocketServer.exe] UDP 0.0.0.0:63078 *:* FDResPub [PhotonSocketServer.exe] UDP 127.0.0.1:5056 *:* [PhotonSocketServer.exe] UDP 127.0.0.1:49339 *:* [PhotonSocketServer.exe] UDP 192.168.1.3:5056 *:* [PhotonSocketServer.exe] UDP 192.168.1.3:49338 *:* SSDPSRV
0 -
restart photon and try telnet from same machine, then from intranet and then from internet. On what stage you fail to connect using public IP?
best,
ilya0 -
@Modemi4 I'm sorry, but I can not help here. that is something with your network setup
Try it somewhere else. I mean use some hosting. When I tried to setup azure server once, I found out that is not enough to switch off firewall. Azure machines have some polices that you have to edit before they will allow external connections at all.
May be it is the case here too?
best,
ilya0