I've been trying to connect to the server that I've just put up. I can get sphere to load and everything, but when I attempt to login, I get an error.

"We were unable to authenticate your login. Usually this means that a newer client patch is now available or the username or password you provided are incorrect.....etc etc etc"

But, here's the thing.

a) client was fully patched, but it still uses the AOS loading screen despite the fact that it came from a ML setup.

username/password are correct

c) the client isn't being picked up on the server

EDIT:

I changed login.cfg to login.scp (and then to login.mul) and I've tried using the IP I get at whatismyip.com and the one that the server says it's listening to and when I put in my password, the client crashes.

A. That's normal, it always shows the AOS screen until you've successfully logged in once. The second time you'll log in it will show the latest login screen you've set.

B. Also check if you have placed them in the correct file: sphereacct

C. Did you specify the correct login in your sphere.ini? (127.0.0.1 for local logging in) Also you need to keep the .cfg extention.

Still getting the same problem.

These are from the sphere.ini the 192 IP is the one that comes up in the server counsel instead of what is shown on whatsmyip.com





And here's the login.cfg

If you want to login locally you have to change your login.cfg to:


The way you had it would work for computers outside your network, you just need the local address

That doesn't work either.

you have to uncomment this

//[SERVERS]
//Ultima
//127.0.0.1
//2593

//Acheron
//192.168.1.101
//2593

1) Do not use different names

2) If you're trying to run more than 1 server, you must use different ports. But if that's not your case, just comment the last 3 lines...

3) Go to ...scripts/sphere_serv_triggers.scp and search for this:

did what both valios and phoenix said and the client still crashed both times and didn't register on the server.

1) Have you forwarded your ports correctly?
2) Have you really used your local IP "127.0.0.1" in your login.cfg, remember it must be (.cfg) not .mul or .scp
3) What does your console says about it? (not the client)
4) Is this what you really have in your sphere.ini and sphere_serv_triggers.scp?


Btw, I doubt 192.x.x.x is your external IP... the console will never show your external IP if you're behind a router.

1) not sure, but all are listed as 2593

2) yes

3) counsel doesn't pick it up at all

4) yes

5) changed sphere_trigger to actual external ip, still crashed

6) What client version? what server build?
7) Make sure that your sphereaccu format is (.scp) and NOT (.txt) => go to the properties of the file to confirm this. / *Do not put an [EOF] there.

It's "sphere_serv_triggers.scp" NOT "sphere_triggers.scp"
Try also putting there your local IP, we have to figure out why your console didn't even noticed of your attempt to get in.

I've changed the sphere_serv_triggers and login files around every which way and still getting nothing.

6) latest 56b build client is 7.0.2.2 patched from the ML client

Try then with a previous client version like 7.0.1.1, and set this in your ini file:

Make sure that you have your sphereCrypt.ini up-to-date.
If that doesn't work either, try using the ip given by the console in every place you have the local ip. And if that also doesn't work you're fucked up dude because I ran out of ideas.

What about your sphereaccu, is it .scp or .txt?

how would I check if the spherecrypt.ini is up to date or not?

the sphereaccu is .scp I double checked that already

So please try with a previous client version like 7.0.1.1 to see what happen, maybe encryptions have changed between 7.0.2.1 and 7.0.2.2. I haven't tried yet with the latest patch so I can't confirm that one. But you will

I've uninstalled UO entirely then reinstalled and patched to 5.0.6 and I'm still crashing the client every time.

found the problem. even though I saved the login as login.cfg it wasn't reading it as a cfg file. I downloaded another login, edited as is, and works fine now.

I'm glad you solved your problem.

Well, I tried upgrading all the way, but again I can't login only this time it's cause the sphere_crypt isn't up to date. I copied the line that you put in, but I'm guessing the client is newer than that lol. any idea without having to uninstall/reinstall/not patching to 7.0.3?

Hey guys! I have same problem...
When Server started on local machine i can login but if i started sphere on remote server i cant log to game...
Sphere console viewing my conect and disconect...client get to me error: We were unable to authenticate your login. Usually this means that a newer client patch is now available or the username or password you provided are incorrect.....

Its problem for Latest Automated build only

I'm also experiencing this with the latest build. I've tried all the configs mentioned here my SphereCrypt is up to date. Locally I can log in fine. My router is set to forward the ports and things were working fine before. I'll try on another system to be sure.