Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to get Server List #444

Open
truadder opened this issue Sep 7, 2023 · 2 comments
Open

Unable to get Server List #444

truadder opened this issue Sep 7, 2023 · 2 comments

Comments

@truadder
Copy link

truadder commented Sep 7, 2023

What happened?

I changed my DNS settings on Switch and joined a featured server, however the server list never popped up (despite doing so at the beginning of the year)

Expected Behaviour?

A server list shows up, and I am able to connect to any other server

Steps to reproduce.

  1. Go to internet settings on console
  2. Change DNS settings (Primary and Secondary, of course)
  3. Save and open Minecraft
  4. Choose any featured server that isn't CubeCraft
  5. Stand around in the featured server like a bum

Screenshots/Videos

No response

Minecraft Bedrock Version

1.20.15

Console

Nintendo Switch

Additional Context

I also want to say that I have changed the primary AND secondary addresses multiple times (104.238.130.180 with 8.8.8.8, then with 1.1.1.1. Change it to 173.82.100.84, repeat). I have asked two of my friends to do the same thing (All different ISPs, one on Nintendo Switch and the other on Xbox One), and they haven't gotten the server list either. They have also tried different DNS addresses. I also tried restarting my Switch, I've backed out of the servers to retry over and over. It may be that ISP is rejecting every address due to having IPv6 enabled or something, however I cannot find where to even disable it (Xfinity user), and my other friends are having the same issue as me with different ISPs. Is it really that 3 different ISPs/Networks are giving us the exact same issues, and all at the exact same time despite being perfectly fine just half a year ago?

@MCrashCraft
Copy link

try 45.79.162.142 as the primary and 1.1.1.1 as the secondary

@truadder
Copy link
Author

Alright, so I found out that it was indeed the ISP's fault. I have Xfinity, and my friend had Xfinity (they mistakenly thought Comcast wasn't the same thing). So now I have a new issue: Is there any way to remedy this without having to tell Xfinity players on my server "Hey, you gotta have a PC, download this file, and run a command"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants