Cant log into DDO

Bug #662028 reported by Luan Almeida
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PyLotRO
In Progress
Undecided
Unassigned

Bug Description

LoTRO works just fine but when I try to log into DDO, pylotro wont pass the message "Checking account details..."
If I type a wrong password it actualy validate and say it is wrong, but if it is correct just wont do anything.

Revision history for this message
Alan Jackson (ajackson-bcs) wrote :

What sort of DDO account is it? Is it an account that has never been logged into before? If it is then it could be that it is waiting for some kind of response that PyLotRO doesn't provide (ie DDOs native launcher might be showing something which you have to click), I've heard of one other person have a similar problem with a F2P LotRO account.

It could be that the servers are busy and you are in a queue, I've never been able to test the queuing procedure, PyLotRO should display a message but as I've said I've never been able to test it properly.

Have a look in ~/.LotROLinux/GLSAuthServer.config after you end up in that situation (post the contents here but blank out the account field).

Revision history for this message
Luan Almeida (luanlmd) wrote : Re: [Bug 662028] Re: Cant log into DDO

It worked!
I never had logged before in DDO with this acc. Just in LoTRO.
When I tried to log on a windows machine it showed a window saying I
needed to add the DDO subscription to my account.
I added the subscription and its running perfectly now.

Thank you very much.

PS: PyLoTRO should show that warn ><

On Sun, Oct 17, 2010 at 4:40 AM, Alan Jackson <email address hidden> wrote:
> What sort of DDO account is it? Is it an account that has never been
> logged into before? If it is then it could be that it is waiting for
> some kind of response that PyLotRO doesn't provide (ie DDOs native
> launcher might be showing something which you have to click), I've heard
> of one other person have a similar problem with a F2P LotRO account.
>
> It could be that the servers are busy and you are in a queue, I've never
> been able to test the queuing procedure, PyLotRO should display a
> message but as I've said I've never been able to test it properly.
>
> Have a look in ~/.LotROLinux/GLSAuthServer.config after you end up in
> that situation (post the contents here but blank out the account field).
>
> --
> Cant log into DDO
> https://bugs.launchpad.net/bugs/662028
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Linux/Mac OS X Launcher for LotRO/DDO: New
>
> Bug description:
> LoTRO works just fine but when I try to log into DDO, pylotro wont pass the message "Checking account details..."
> If I type a wrong password it actualy validate and say it is wrong, but if it is correct just wont do anything.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/pylotro/+bug/662028/+subscribe
>

--
Atenciosamente,
Luan Almeida
http://luanlmd.com

Revision history for this message
Alan Jackson (ajackson-bcs) wrote :

It's a new thing that was added when F2P went live first in DDO then LotRO, it doesn't always happen and as yet I have had no clean capture of what is sent instead of the normal login process.

It is all very well saying PyLotRO should show the warning but chances are I wouldn't be able to get it to add the subscription to the account.

I'll leave this open in case anyone can provide me with any clue about what exactly is sent back from the server when this happens, without that I can't do anything.

Revision history for this message
Alan Jackson (ajackson-bcs) wrote :

This will be fixed in 0.1.14.

Unfortunately PyLotRO can't fix the problem directly but the solution is to login to your user account on the Turbine site and associate the game account (in this case DDO) to that user account and that should solve the problem.

PyLotRO will now show an error [E14] and tell you to visit the account management site.

Changed in pylotro:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.