Jump to content
  • Sign Up

Archived

This topic is now archived and is closed to further replies.

DeetPlayer

Localhost server

Recommended Posts

I finally could port foward and got the classicube url, I joined the classicube url and found this:

image.png.a177eaeda94986214d0255fe07b9fae3.png

Why would I connect to 127.0.0.1????? (classicube's localhost)

Don't reply with an answer because I know how to fix it

Classicube gave me this URL but it won't take you to 127.0.0.1, it will take you to my server (The URL won't work anymore, not even my server)

http://www.classicube.net/server/play/703d1984486cba0cf6c0a1603e9a4b75/

Share this post


Link to post

with the webclient it check if the server is your ip and if so then it automatically sets itself to localhost but its weird how you were able to join it 

Share this post


Link to post
5 hours ago, DeetPlayer said:

I finally could port foward and got the classicube url, I joined the classicube url and found this:

image.png.a177eaeda94986214d0255fe07b9fae3.png

Why would I connect to 127.0.0.1????? (classicube's localhost)

Don't reply with an answer because I know how to fix it

Classicube gave me this URL but it won't take you to 127.0.0.1, it will take you to my server

http://www.classicube.net/server/play/4bbce454f3bcde8462511408be295975/

that happens to alot of people i even had that happen to me so theres no way to fix it 😞

Share this post


Link to post
9 hours ago, lashednova said:

that happens to alot of people i even had that happen to me so theres no way to fix it 😞

There is a way to fix it. In server.properties if you put your private ip classicube takes you to 127.0.0.1 if you  instead of private ip you  leave 0.0.0.0 it takes you to your server.

Share this post


Link to post
On 3/12/2021 at 7:57 PM, DeetPlayer said:

I can join my server in the webclient because  I knew how to fix itimage.png.8a08509523a9eb7be918e67c66478b8b.png

I couldn’t join it. It says that the server is down.

Share this post


Link to post

I've run into issues with 127.0.0.1 myself. I'm not sure exactly what is going on behind the scenes, but whenever I run into this issue (which isn't often), replacing 127.0.0.1:25565 with "localhost:25565", localhost has always resolved to the local address I've needed to enter the server.

 

I'd say give it a shot, couldn't hurt to try.

 

Edit: Just read that you didn't need a solution after all. Hopefully this helps someone in the future then.

Share this post


Link to post

×
×
  • Create New...