Ryzom

HMm... good job turs. Not sure how I missed that when I was readin that file last night

HOT DAMN.....Tursas you are now my favorite person on the planet.

I must say that i was very distraught last night, and was having homicidial throughts,at not being able to get in. Tursas you prolly just saved my wifes cats life...cause it was lookin like i'd have to take my fustrations out on it.

I suspected something like this.. however how could it not have updated somehow....???? How did everyone elses update?

Jindo when you are mad at cats just pee on them, its good venting and no harm done, plus you are claiming your territory.

amitst wrote:I suspected something like this.. however how could it not have updated somehow....???? How did everyone elses update?

My guess is, it's because the client first needs to connect to the login address (which has changed) to download the patches, and there is no configured separate address for patch downloads that would have been maintained throughout the server move. Those who didn't experience problems are probably all people who had been playing the game before the server move and got their clients autopatched in time.

The manual patching utility ryzom_recover.exe does try to connect to some alternate host but atleast today, for me it was also unreachable.

Anyways thanks to spriteh and Thara on the IRC channel for helping me find out what was wrong.

StartupHost = "rslogin.juk.shards.nevrax.com:40916";

even with that info checked i still get error 1 message the upto date info was all rdy there for me. i also can't even login to the website either maybe login server is down then?

It is very odd. I renamed the server in the config file as specified, updated and played on two separate machines about three hours ago. Now, it is giving me the same error.

Perhaps it is a maintenance issue. I'll check back before I go to work and see if it is still a problem. If so, I'll be checking this thread and posting my tests, etc.

my cfg file reads correctly and in still getting the cant conect message

teper wrote:my cfg file reads correctly and in still getting the cant connect message

As was I.

My cfg file read correctly and pinging 83.141.21.155 was successful... yet still an "Error 1" message.

Waited 5ish minutes and tried again… and I could log in. Sorta strange.

Same case here, Ryzom technical team, pls, look into this. I have not had any issues before, was playing, all of a sudden, I can't login with Error-1 and all the hosts are reachable and tracert runs completely and without problems.

make sure you edit client.cfg and not client_default.cfg as last one gets overwritten with patching process and may restore wrong StartupHost again.
--
StartupHost = "su1.rzl01.gameforge.fr:40916";
--
rslogin.juk.shards.nevrax.com is alias for su1.rzl01.gameforge.fr

ohh yeah, after each patch check client_default.cfg StartupHost value. if they patch in new address there, then remove StartupHost from client.cfg

there was ip change i think or dns hickup. rslogin.*.nevrax.com didnt answer before, but now it does. cant remember ip i got for it when it didnt work ;-(

other domain game connects at startup is crashcounter.nevrax.com (first thing in log.log) , which also points to old ? address and thats the other reason it takes time to load. ban it in firewall for now... i did