Bedrock cannot connect to a server: fixes to try

"Unable to connect to world", "Could not connect to server" or a screen that loops on Locating server: these have a short list of causes. Go down the list in order.

1. The address and the port

Bedrock needs both. The Java address alone is not enough. On the server's dashboard look for the Bedrock card and type the address and the port exactly. A number that is one digit off looks like a dead server.

2. Is the server awake?

A free or sleeping server wakes when someone joins, and the first attempt can fail while it starts. Wait 20 seconds and try again.

3. Is your game up to date?

Bedrock servers only accept a matching version. Since 26.60 the way Bedrock connects changed as well; see Bedrock 26.60 and NetherNet. If one friend can join and another cannot, compare their game versions first.

4. Delete and re-add the server entry

The game remembers how it last reached a server. Remove the saved entry and add it again. Use the IP address instead of the name if the name sits on "Locating server".

5. Consoles

Xbox, PlayStation and Switch have no Add Server button. Use a tool that adds a featured entry, or join through a friend on the same network, or use the "Friends" route if your server supports it. This is a console limit, not a server fault.

6. Your network

A school, work or public network may block the ports. Try a phone hotspot.
A VPN can block or reroute the connection.
On your own router, check that both TCP and UDP are open if you host at home.

7. The server side

If you run the server yourself, check that Geyser (or the Bedrock server) is running and listening on the port you gave out, that the firewall allows it, and that online-mode and whitelist settings are what you expect. In the console, geyser version shows whether Geyser is new enough.

Still stuck

Open the server's connection check on Saryno: it tests the server list reply from outside and says what is wrong. See also Java and Bedrock crossplay hosting.