Use MultiMC or Prism Launcher to connect - ensure you’re using Beta 1.7.3, not the release version. (Toggle the “betas” filter and select “b1.7.3” when creating your instance)
Once you are whitelisted, the server is accessible at oldschoolmc.live:25566
Whitelist application is here (After submitting, you should be whitelisted within 12-24 hours, if not sooner)
Rules are on the website
I’m asking because the IP this Minecraft server uses used to belong to a Tor exit (operated by me a while back). It retains permanent bans in a few countries after that.
Also, please try pinging oldschoolmc.live and visiting it in your browser (should display a landing page)
I’m able to reach the landing page. I have read the rules over there and I also copy pasted the address from that site just to make sure everything was correct.
I wouldn’t be surprised if my ISP was pulling some strings though.
I live in Florida and I have Spectrum as my internet provider.
Shouldn’t have any issues in Florida… Restarted the server, try joining again. You’re using the vanilla client, right?
Also confirm your Minecraft username pls, just in case you made any typos in the whitelist app
The server is receiving your connection attempts but rejecting them for some reason… Doesn’t even get into login phase, no idea what’s going on here yet…
The ip address yields similar results.
I’m loading up multimc now
I guess it just wasn’t meant to be. I will try again another time. Otherwise, post some updates on the server so I can get a gander at things going on. It would also be nice as a community project.
Silly question but are you sure you are using minecraft version b1.7.3 and not r1.7.3? Also make sure windows did not block minecraft in your firewall.
ooh yeah, this is a good suggestion.
it’d be easy to select release 1.7.3 instead of beta accidentally in MultiMC, and that’d line up with some of the server responses i’ve seen so far.
Collin, note the “betas” filter has to be ticked when making your instance in MultiMC to see the right version (this is a screenshot from Prism, but their UI here is identical)
After further testing, this is almost definitely what happened. I get the exact same error messages and server responses as Collin was getting when attempting to load into the server with r1.7.3