search

BeardedManStudios / ForgeNetworkingRemastered

See various forks, also please join the Forge Community fork of Forge Alloy! -> https://github.com/ForgeAlloyCommunity/ForgeAlloy
https://twitter.com/FarrisFaulds
Apache License 2.0
1.49k stars 306 forks source link

NAT + MasterServer not working #71

Open pointcache opened 7 years ago

pointcache commented 7 years ago

Version Number and Operating System(s):

Latest version, win 10

Expected behavior:

You put them on Linux vps, launch them following these instructions https://github.com/BeardedManStudios/ForgeNetworkingRemastered/wiki/Starting-up-MasterServer-and-NatPunch-on-DigitalOcean-droplet

And it just works.

Actual behavior:

Nothing works, no error, no warning, NOTHING in bms log , just refuses to connect to server. Nat output doesnt show anything at all as well.

Steps to reproduce:

[Optional] Discord Username:

poolfire

I can just give you access to the repository with the project, and you literally can see the bug in action. I am absolutely 100% incapable of understanding why it doesnt work.

adhicl commented 6 years ago

I also got the same result so +1

adhicl commented 6 years ago

Any news on how or when this could probably solved? I myself has been trying to investigate why, so far it seems that the natpunchhole fail to receive register message from client. When connected on local computer: connected What happened on server: notconnected

adhicl commented 6 years ago

Hi, so is there anyone working on this? I am now able to get the register command to be sent from the server but the NAT hole punch is still failing a.k.a the host client can not send the first message to the connecting client and I have no idea why this time

Crazy8ball commented 6 years ago

Here is the documentation for Nat Hole Punching. We didn't write that Wiki on how to use it for Digital Ocean but I would contact the person who did if you are trying to use it through them. http://docs.forgepowered.com/nat-hole-punching/#nat-hole-punching

I can't tell if it is firewall related but I would also check the ports of that machine and make sure they are 100% open.

adhicl commented 6 years ago

Hi @Crazy8ball , yeah my problem right now is the Nat Hole Punch seems like does not working between the clients. I have testing things using the ConsoleProgram in this github source. And I already manage to make it so that the NatHolePunch on server and client can communicate. The problem is the connection between client that does not work. My setup right now is: NatHolePunch is in DO Ubuntu Server (port is opened etc) then I run the console as server and client on my computer (is it because of this?) both can communicate to the Nat, but cannot communicate to each other. I also have tried with 2 PC on same Nat, 2 PC (1 behind Nat and 1 using mobile hotspot) in all the cases the result is same. The server console (client hosting server) got the message that a client is connecting and the debug that it is attempting to do Nat to the other client shows up. But the other client does not get anything. Do you have any example on a working Nat Hole Punching before?