[BDS-5131] Cannot connect to server on non-default ports. Created: 07/May/20 Updated: 19/Aug/20 Resolved: 19/Aug/20 |
|
| Status: | Resolved |
| Project: | Bedrock Dedicated Server |
| Affects Version/s: | 1.14.60 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Taser597 | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows 10 |
||
| Confirmation Status: | Unconfirmed |
| Description |
|
Affected Version Note: The server itself is outputting 1.14.60.5 to the log, but this doesn't show as a valid version in the "Affects Version/s" field. I have one server running on the default ports that works fine. I stopped the main server and found that the second server runs fine as long as it has the default ports, but if I change the default ports, connections will fail regardless of the first server running or not. It fails with a simple "Unable to connect to world." Since the server seems to be working, I'm not sure if this is a BDS or a Minecraft (client) bug. Test method: Added server with local ip address (127.0.0.1) and a non-default port (20XXX). Interesting Note: When starting the second server when the first wasn't running, instead of picking ports in the 50XXX or 60XXX range for the second set of ports, it would pick the default 19132/19133, and attempting to connect on those would give the error "Wow this server is popular! Check back later to see if a space opens up." despite the proper ports (non-default ports chosen in settings) displaying running with 0/10 players when queried by the Minecraft client. |
| Comments |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 19/Aug/20 ] |
|
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem. Quick Links: |
| Comment by IonicEcko [ 15/May/20 ] |
|
I've not heard back in a while so I'm going to place this report in "Awaiting Response" status. It will reopen automagically when you next comment. |
| Comment by IonicEcko [ 08/May/20 ] |
|
Hi Tommy, I'm not able to replicate this behaviour. I started a server on both 19132 (and 19133 ipv6) and 19134 (and 19135 ipv6) and was able to connect to both. I even tried switching the second instance to a higher port number to match your description (20132 and 20133 ipv6) and its till connected. Do you have firewall rules in place for both instances? Ionic |