Earlier today I changed my Origin password, and when I tried to reconnect the integration on Galaxy 2.0, it became stuck at "connecting".

I've tried :
- Restarting Galaxy
- Restarting Windows
- Deleting Origin plugin files (when I do that it redownloads the pluging but immediatly proceeds to "connecting" without giving me any prompt.

Any idea ?

I've solved it.

I manually ended the python process while it was running, so that the Origin integration crashed and the disconnect button appeared. Then I could reconnect and get the login prompt.

Can confirm both the issue and the fix. In the integrations dialog I would only see a loading spinner and no other option to stop or disconnect the process. After stopping the Python process, I hit retry and the same happened. Stopped the process again and disconnected and reconnected the Origin integration. It worked ok afterwards.

I've encountered this issue after enabling the two-step authentication on Origin.

EDIT: worked for me as well. Took a while for the Python process to show up in my Task manager though. Thanks!

12/10 tnx

And another confirmation that killing the python process (check the command line to see which one is origin), then disconnecting and reconnecting the plugin solves the problem, at least for now.

Thanks for the suggestion Tolrem.

What is the name of the task I have to kill?

python.exe - there will be several processes, one for each plugin, so make sure to go into details view and expand the column "commandline" so you'll kill the correct process

Then switch back to GoG Galaxy Client, it will say plugin crashed.
Next, click DISCONNECT

After that you can retry / CONNECT the platform


This workaround worked for me but the issue keeps reappearing.
Logged it in issue tracker as well.

Same here.

Why is there no "cancel"-button to stop Synchronizing and enter new login data?

Greetings, Ronny

Same for me.
The solution to kill the python process works but if you can add a button for disconnect/reconnect could be a better and more friendly user solution :)

this is still happening

This happened to me as well and the workaround was perfect and well explained. Thanks @Tolrem, @Daktary, @Zerofk, @Johnny5wd

In my case I had to kill the process, press retry, kill the process again, and press retry again. Then the window that popped up could connect and I could enter the login info.

Take care :)

Well, this worked like magic to my problem where the login prompt didn't accept my credentials, thank you.