Nukkit port bound, but not visible externally.

Like mentioned, Nukkit seems to be able to bind to the port 19133 just fine. However using a site like canyouseeme to see if the port is open or closed, it reports closed. Switching to PocketMine on the same port makes it switch over to open.


Anyone got similar experiences?

 

I have another issue (it could be a problem of Minecraft Windows 10 Edition): when I run nukkit on my PC (for example on port 29132) I can connect to it using my phone and windows 10 tablet, but I can't connect from the same PC.


I hope @Snake1999 could provide us some additional info

 

That's an issue with Minecraft Windows 10. You have to run on a another port since MCW10 comes with a built in server running on 19132 and even when running on another port, I need to connect using my external IP for it to work.

 

This is just because you haven't port forwarded correctly. My issue is specific to Nukkit.

 

That is an issue for mojang's client. Usually it's their client that make it possible or impossible to do something, especially in network.
I wrote advices on "srv forwarding in mcpe" and "upnp forwarding" for mojang in its website, just hope for the best
For Nukkit, we did query in it, you can test if this server is online using query

 

It does actually work if you connect using your external IP.

 

It works external with simply socket connection, but if work internal needed, upnp forwarding should be added in the client. If I'm true, working on server is useless if no client supports. Our team does much on port forwarding and even use a virtual machine, just want to adapt it and test the server in win10
Just write to mojang and hope for mojang to add

 

@Snake1999
Did you create a ticket at bugs.mojang.com?
If yes, please give us link - will vote for this this ticket

 

@fromgate Here it is
https://bugs.mojang.com/browse/MCPE-12293

 

My vote given for this issue It think now everyone must vote too

 

This is not the issue. This is entirely something else. We're not talking about forwarding here at all. When running PocketMine the port registers as open, when using Nukkit it does not. How can this have anything to do with SRV records forwarding when there are none.

 

For your problem, it's about an undone Nukkit feature called UPnP forwarding(what pocketmine have already done). And yes, we will have that done.

-----------------------------------------------------------
If you want to know the detail for your problem, see this:
Usually for server opening home, to make server visible to internet, the route might be:
[Your computer ---Router(UPnP)-]-> Internet -[-> Client]
[Your computer ---Router(Manual Configurate)-]-> Internet -[-> Client]
[Your computer -]-> Internet -[-> Client]

but not this:
[Your computer ---Router-]-XX Internet -[-X Client(Can not find server)]

Notice that something called UPnP make it possible to bind forward automatically, but without it you could only port forward by config your router manually. To bind forward automatically, both routers and softwares should adapt UPnP.

-----------------------------------------------------------
For SRV Forwarding, it could be:
[Your computer running many servers =]=> Internet =[=> Client(Many servers)]
For example, if you add a SRV record to DNS, that make it possible to transfer s35.example.com:19132 to h1.example.com:20991 (port changed).

 

I know how both UPnP and SRV works. SRV is irrelevant to this issue, but UPnP WOULD have been an issue if it wasn't for the fact that the port is exposed using NAT-PMP (equivalent of UPnP). The PocketMine UPnP client is not enabled as witnessed in the pocketmine.yml: "upnp-forwarding: false".

This is an issue with Nukkit itself as the port is specifically opened by a port mapper application I run. I don't need to run a program on the port at all in order to open it.

 

OKAY, I will have our team mentioned to make this UPnP system done

 

@Snake1999
@ProjectInfinity

Here is solution that helped me (@Tee7even told me at another topic):

I typed in command line: CheckNetIsolation LoopbackExempt -a -n="Microsoft.MinecraftUWP_8wekyb3d8bbwe"

And now I can connect from MCW10E to server created at localhost!