Maintenance for the week of November 10:
• PC/Mac: NA and EU megaservers for patch maintenance – November 10, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PC/Mac: NA and EU megaservers for patch maintenance – November 10, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
login problems timeout and 301
Windshadow_ESO
✭✭✭
in the evenings eastern time on the NA server esp. on Saturday evenings i get first a time out error and then if i immediately log in again i get this 301 error
is there any workaround other than waiting a few hours?
is this the way server busy is now handled?
is there any workaround other than waiting a few hours?
is this the way server busy is now handled?
1
-
Windshadow_ESO✭✭✭oh yes game consultant results in the spinning beachball of death o n this computer so I can not send it to support as the faq tells you to
0 -
KhajitFurTrader✭✭✭✭✭
✭✭Have you seen the info about error 301 given in the stickied post here? This is clearly a network issue, but as always with this kind of thing, it may be hard to find out exactly where and why it's occurring. You could try to follow the suggested steps if you haven't already.
Btw, the host.developer.log file that's being mentioned in the post can be found within the Launcher.app folder in Contents/MacOS (use "Show Package Contents" from the right-click menu on Launcher.app).0 -
Windshadow_ESO✭✭✭it must be something the time warner folks are doing sometimes on Saturday evenings... after about 2 hours the problem went away... i did send the requested stuff to support though the connection assistant hangs under 10.10 so they got the huge crash log it created as well0