The problem:
MPPASS is generated by the site when you give it a username and a server string, so if you connect via an IP it doesn't work because it can't generate MPPASS and it assumes you're faking.
The solution:
To bypass this we provide MPPASS manually. To get MPPASS we need to visit the external URL, it doesn't matter if the server is down it still generates the MPPASS. So, we then take this MPPASS value and copy it, we then force the server to take it when running locally, we do this by editing the HTML with firebug.
The video of how is below; sorry if the video is a bit ****, it's rushed because I was super proud that I figured it out. Any questions, ask away! :biggrin.gif: I'll make a better one :smile.gif:
Whoa, how the hell did you know where to look/edit? :S
just a bit of looking and working out how things worked. The problem occurrs whenever you used the IP based URL with verify-names true, so I worked out that the cause must be a difference between those 2 urls. I then opened up the source for each page and compared; the only difference was the lack of MPPASS, so that told me that this must be the cause. I then tried using the MPPASS from the proper page in the local page and it worked. Pretty simple, really :smile.gif:
Hmmm... I have wondered what that mppass was before. I guess it was for this. Finally this will fix all those problems and get rid of people impersonating Notch. (or someone else :tongue.gif:)
Whoa, how the hell did you know where to look/edit? :S
just a bit of looking and working out how things worked. The problem occurrs whenever you used the IP based URL with verify-names true, so I worked out that the cause must be a difference between those 2 urls. I then opened up the source for each page and compared; the only difference was the lack of MPPASS, so that told me that this must be the cause. I then tried using the MPPASS from the proper page in the local page and it worked. Pretty simple, really :smile.gif:
Damn, you're a great asset to the Minecraft community.
If I don't want to go through the hassle of switching browsers because I've been to lazy to get Firefox, is there a way to get this to work with IE, or would that be a waste of my time?
If I don't want to go through the hassle of switching browsers because I've been to lazy to get Firefox, is there a way to get this to work with IE, or would that be a waste of my time?
Not sure, I know IE8 has some "dev tools" but I honestly doubt they work. Firefox is well worth the 5 minute switch time.
would love to know whether anybody has figured out a way around this permanently, where one could also use a standalone client.
but my method so far is, use Hotspot Shield
this probably wouldn't work if you're running the server on the same computer as the one you're trying to play from. but if you have a setup like myself, and have a separate PC in your home which is used as a server for games, such as steam games, and minecraft, then this should work for you as well.
the issue seems to have something to do with being on the same network as the server? I have no idea. but this works for me. so try it out yourself!
SO glad this is finally fixed. Just for those who missed it, here's a recap from Notch:
"+ Added a HUGE warning for running without verify-names turned off"
"######################### WARNING #########################
verify-names is set to false! This means that anyone who
connects to this server can choose any username he or she
wants! This includes impersonating an OP!
AND SINCE THIS IS A PUBLIC SERVER, IT WILL HAPPEN TO YOU!
If you wish to fix this, edit server.properties, and change
verify-names to true.
###########################################################"
"From now on, if minecraft.net detects someone trying to connect to a server from the same ip as the server, it will direct the player to 127.0.0.1 instead of to the server ip."
"Also, if you ran into problems with the local ip fix I blogged about before, I’ve added a work-around for it: add “&override=true” to the url to force it to use the external IP."
SO...long story short (too late) to log on to your own server:
Use the address in the "ExternalURL.txt" file and add "&override=true" to the end of it (without the quotes)
Rollback Post to RevisionRollBack
Monkey Mines is a small 18+ Whitelisted Realms server that also allows families. We're currently looking for new players if they're not jerks.
Does this problem still happen at all? (Heard from someone it doesn't)
If not, this sticky is useless.
Rollback Post to RevisionRollBack
"Can you point to the object that represents a resilient parasite of an idea caught in the tangled nature of the subconscious human mind? Thaaaat's right!"
http://firefox.com
http://getfirebug.com
The problem:
MPPASS is generated by the site when you give it a username and a server string, so if you connect via an IP it doesn't work because it can't generate MPPASS and it assumes you're faking.
The solution:
To bypass this we provide MPPASS manually. To get MPPASS we need to visit the external URL, it doesn't matter if the server is down it still generates the MPPASS. So, we then take this MPPASS value and copy it, we then force the server to take it when running locally, we do this by editing the HTML with firebug.
The video of how is below; sorry if the video is a bit ****, it's rushed because I was super proud that I figured it out. Any questions, ask away! :biggrin.gif: I'll make a better one :smile.gif:
MUST WATCH IN HD
Now I can finally get my server up when I'm using my relatives routers. :biggrin.gif:
just a bit of looking and working out how things worked. The problem occurrs whenever you used the IP based URL with verify-names true, so I worked out that the cause must be a difference between those 2 urls. I then opened up the source for each page and compared; the only difference was the lack of MPPASS, so that told me that this must be the cause. I then tried using the MPPASS from the proper page in the local page and it worked. Pretty simple, really :smile.gif:
Damn, you're a great asset to the Minecraft community.
Well done, citricsquid.
no.
Nice job citric, i was thinking the problem was on those lines.
Quality of output = Skill * Effort
If I don't want to go through the hassle of switching browsers because I've been to lazy to get Firefox, is there a way to get this to work with IE, or would that be a waste of my time?
Short term time vs long term time.
Quality of output = Skill * Effort
Not sure, I know IE8 has some "dev tools" but I honestly doubt they work. Firefox is well worth the 5 minute switch time.
to
Thank you so much!
but my method so far is, use Hotspot Shield
this probably wouldn't work if you're running the server on the same computer as the one you're trying to play from. but if you have a setup like myself, and have a separate PC in your home which is used as a server for games, such as steam games, and minecraft, then this should work for you as well.
the issue seems to have something to do with being on the same network as the server? I have no idea. but this works for me. so try it out yourself!
"+ Added a HUGE warning for running without verify-names turned off"
"######################### WARNING #########################
verify-names is set to false! This means that anyone who
connects to this server can choose any username he or she
wants! This includes impersonating an OP!
AND SINCE THIS IS A PUBLIC SERVER, IT WILL HAPPEN TO YOU!
If you wish to fix this, edit server.properties, and change
verify-names to true.
###########################################################"
"From now on, if minecraft.net detects someone trying to connect to a server from the same ip as the server, it will direct the player to 127.0.0.1 instead of to the server ip."
"Also, if you ran into problems with the local ip fix I blogged about before, I’ve added a work-around for it: add “&override=true” to the url to force it to use the external IP."
SO...long story short (too late) to log on to your own server:
Use the address in the "ExternalURL.txt" file and add "&override=true" to the end of it (without the quotes)
If not, this sticky is useless.
The topic is from 16 months ago, it's no longer relevant.