[BDS-9950] Can't connect to bedrock server Created: 19/Nov/20 Updated: 28/Apr/21 Resolved: 28/Apr/21 |
|
| Status: | Resolved |
| Project: | Bedrock Dedicated Server |
| Affects Version/s: | 1.16.40 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michał Dąbrowski | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | awaiting-response | ||
| Confirmation Status: | Unconfirmed |
| Description |
|
I used to be able to connect to the bedrock server just fine, but it suddenly stopped working. https://bedrockinfo.com/ can connect fine and displays the correct server info, but my iOS clients just say "can't connect to the world". Restarting the server nor the clients does not help. I upgraded to 1.16.100 and the issue persist.
It's running on Ubuntu, there is no firewall set-up. I can't even connect by typing local IP within the same network.
How can I troubleshoot further? How to get more debug info from the iOS client? How to get the server to be more verbose? It does not show anything in the log file when https://bedrockinfo.com/ is sending requests. |
| Comments |
| Comment by [MCQA] Kinga Izdebska [ 28/Apr/21 ] |
|
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 [ 26/Nov/20 ] |
|
Your server needs to be updated any time there has been a client update. If you haven't yet updated your server to 1.16.100 and your clients have, that would explain your issue. |
| Comment by Michał Dąbrowski [ 19/Nov/20 ] |
|
I just noticed my iOS clients were updated 2 days ago to 1.16.100. Maybe this caused the problem? As I tried with a friend who owns a PC and he could connect without issues |
| Comment by Michał Dąbrowski [ 19/Nov/20 ] |
|
iOS devices can access the HTTP server on the same machine, so this is unlikely to be a network issue. |