It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Kalanyr: paladin181

I've looked into the login problem but I can't duplicate it. I just logged in using the existing script on Python 2.7 and Python 3 and it worked on both for me without any problems. If you want to help me out by getting further data: I'd suggest seeing if logging out and logging in on GOG.com clears the scripts need for a recaptcha and then verifying your username and password entry were correct by using a text file and copying and pasting both to log into GOG.com from a browser and via the script , in order to copy and past into a Dos window Right click on the title bar -> Edit -> Paste.
avatar
paladin181: I will do. I'm at work now, but when I get home I'll try that. Thanks again for your help. I may try logging with Python 2 (that was where my original cookies came from). I just found it odd that the script wouldn't update the cookies.dat properly; I've done so before with no problems.
That's probably because of the ReCaptcha crap that GOG activated again.

Until a few days ago you only needed ReCaptcha when you redeemed a gift code or (from what I have heard) when you mistype you login several times. Now it's mandatory even on the first login. GOG did that once before but stopped doing that on user protest.
avatar
Geralt_of_Rivia: That's probably because of the ReCaptcha crap that GOG activated again.

Until a few days ago you only needed ReCaptcha when you redeemed a gift code or (from what I have heard) when you mistype you login several times. Now it's mandatory even on the first login. GOG did that once before but stopped doing that on user protest.
The thing is, I didn't get the reCAPTCHA prompt the first few times, I got "login successful" but my cookies.dat wasn't updated. The problem is my cookies expired and they won't update. Hopefully, relogging at home will make this work and allow me to login, because importing the cookies.txt looks a little daunting.
avatar
Geralt_of_Rivia: That's probably because of the ReCaptcha crap that GOG activated again.

Until a few days ago you only needed ReCaptcha when you redeemed a gift code or (from what I have heard) when you mistype you login several times. Now it's mandatory even on the first login. GOG did that once before but stopped doing that on user protest.
avatar
paladin181: The thing is, I didn't get the reCAPTCHA prompt the first few times, I got "login successful" but my cookies.dat wasn't updated. The problem is my cookies expired and they won't update. Hopefully, relogging at home will make this work and allow me to login, because importing the cookies.txt looks a little daunting.
Try deleting your cookies.dat then ? I've never actually been in the be situation of having naturally expired cookies in my cookies.dat and it's not really artificially inducible to test. I did my test of the login by renaming the dat file and logging in , then testing an update command.
avatar
Geralt_of_Rivia: That's probably because of the ReCaptcha crap that GOG activated again.

Until a few days ago you only needed ReCaptcha when you redeemed a gift code or (from what I have heard) when you mistype you login several times. Now it's mandatory even on the first login. GOG did that once before but stopped doing that on user protest.
What does that mean, "first login"? Do you mean trying to log in without valid cookies?

Normally i login with Chrome (where I keep cookies), but just to try if anything has changed, I logged out from Chrome and logged in with Firefox where I always delete all cookies, offline data, cache etc. Worked fine, i didn't get CAPTCHA either.

Someone in another thread pointed out CAPTCHA would come (and require lots of pictures to go through) if one blocks Google tracking scripts and doesn't use Google services. I am unsure how to do that exactly (stop the tracking and google services), but maybe I am then allowing Google to track since I don't face such problems with CAPTCHA. Merely not having cookies doesn't seem to trigger CAPTCHA, at least for me.

I do get CAPTCHA when redeeming codes (and there I only have to solve two pictures, not doing CAPTCHAs for five minutes like some say they do); I don't recall the last time I've gotten CAPTCHA on GOG besides that.
Post edited December 18, 2017 by timppu
avatar
Kalanyr: Try deleting your cookies.dat then ? I've never actually been in the be situation of having naturally expired cookies in my cookies.dat and it's not really artificially inducible to test. I did my test of the login by renaming the dat file and logging in , then testing an update command.
I renamed the file, as I said earlier. I still haven't gotten home to try your solution yet, or try in Python 2. :) I'm at work for another 3 hours or so, so there isn't any news. I was just explaining the situation to Geralt. When I tried last night though, it didn't generate a new cookies.dat even after a successful login (as demonstrated in this post). Again, I haven't tested or tried anything since that post last night.
avatar
Kalanyr: Try this method for using Cookies exported from Firefox for (actually anything you can log into got on and get a standard format cookies.txt out of should work) now:

https://www.gog.com/forum/general/gogrepopy_python_script_for_regularly_backing_up_your_purchased_gog_collection_for_full_offline_e/post1189

You may need a Cooke export plugin on Firefox to export your cookies depending on how new your FF version is.

I haven't touched the login part of the script at all, so I'll have a look at it sometime today.
Ok. This actually worked and created a cookies.txt.tmp and cookies.dat in my GOGRepo folder... Still can't create a new cookies.dat through normal login. Tried in Python 2.7 and 3.6 It logs in fine, but doesn't generate a file. And the folder isn't protected in anyway.

Still, this solved my problem for now. Thanks, Kalanyr
Post edited December 19, 2017 by paladin181
I cannot download with the latest master build, Dec 6th - python 3.6.
The download starts with normal speed and drops massively after 20 seconds until the server pulls the plug. I don't get any error messages. Update ist fast, no difficulties, only the download is affected.
I tried rebuilding the cookies.dat file to no avail.
I am currently downloading with the previous build, Dec 4th, which runs smoothly.
Just wanted to report this issue.
avatar
Kalanyr: I'm running Python 2.7 primarily and I'm not getting this error. Is your Python 2 install up to date ? Or have edited GOGRepo py to run substantially more than 4 threads ? There's no reason that Timer threads should be failing to spawn, and it shouldn't be accumulating threads, the only way out without the responseTimer in a thread being cancelled is an exception and that should hang the thread.

If anyone else with Python 2.7 is getting that problem let me know.
I have not edited GOGRepo in any way, but it seems I was running Python 2.7.13, which is not current.

avatar
RupertMurdock: I cannot download with the latest master build, Dec 6th - python 3.6.
The download starts with normal speed and drops massively after 20 seconds until the server pulls the plug. I don't get any error messages. Update ist fast, no difficulties, only the download is affected.
I tried rebuilding the cookies.dat file to no avail.
I am currently downloading with the previous build, Dec 4th, which runs smoothly.
Just wanted to report this issue.
It seems I'm having the same issue. Using Python 3.6.3 with the gogrepo.py Dec 6 build, update went fine, but download speed drops to half my usual max speed after a few seconds and then drops to at most 0.1 MB/s per file after a few minutes.

Testing with Python 2.7.14 also results in the same poor speeds, with a few additional error messages between the downloads:

22:58:10 | request failed: ('Connection aborted.', error(10054, 'An existing connection was forcibly closed by the remote host')) (3 retries left) -- will retry in 5s...
(...)
2Traceback (most recent call last):
File "C:\Python27\lib\logging\__init__.py", line 872, in emit
stream.write(ufs % msg)
IOError: [Errno 0] Error
Logged from file gogrepo.py, line 1790
(...)
Post edited December 19, 2017 by Nix31
Please use the commit numbers when reporting regression errors. I'm in Australia, so the last three updates I see are 4/5/6 of December and I don't know which you're talking about.

I'm currently trying to make Steam work in the middle of the Christmas Sale but I'll upload the current version of GOGrepo I'm using later on today.

(I can't see how December 6 would be slowing downloads. I can see how December 5 could potentially do so, under corner case conditions that the Winter Sale might be causing, but there's a significant loss of functionality beteween the December 4 and 5 builds).

ETA - Those emit errors happen when you're scrolling up during the logger outputting to standard out, they are harmless.
Post edited December 19, 2017 by Kalanyr
avatar
Kalanyr: Please use the commit numbers when reporting regression errors. I'm in Australia, so the last three updates I see are 4/5/6 of December and I don't know which you're talking about.
I tried to find out the commit number this morning and it seems that commit nr a59597742dadf225d948a4c39bb3cc96b49e7a24
ist running fine. That's the one I am currently using.
Haven't tried commit 350b8b962819cb11ff70f1ba5a9098c04431077c.

I am using the latest master build for 9 days and the problems started right away, so I do not think the Winter Sale is causing the drop of download speed. Yesterday I finally found a bit time to investigate this issue and try out an older version I still had in my gogrepo folder.
Post edited December 19, 2017 by RupertMurdock
Okay, just updated with my current working build. I downloaded 200 GB with this at normal speeds last week so if people are still having weird download performance this is going to be a "fun" issue to debug.
A bit too late I guess, but I tested commit 350b8b962819cb11ff70f1ba5a9098c04431077c:
Running flawlessly...

Will download and try out the new version in several hours.
avatar
Geralt_of_Rivia: That's probably because of the ReCaptcha crap that GOG activated again.

Until a few days ago you only needed ReCaptcha when you redeemed a gift code or (from what I have heard) when you mistype you login several times. Now it's mandatory even on the first login. GOG did that once before but stopped doing that on user protest.
avatar
timppu: What does that mean, "first login"? Do you mean trying to log in without valid cookies?
Exactly. Logging in from Firefox without valid cookies always give me ReCaptcha since a few days. That didn't happen before.
Test with the last 4 versions of the script:
I created a new folder, transfered my manifest and my cookies.dat and copied the gogrepo scripts.
I ran the first script, downloaded for about 3 minutes, killed the process, deleted all folders and ran the next script.

Here are the results:
a595977 - no loss of speed
350b8b9 - no loss of speed
27da409 - slows down
36b845c - slows down

As long as the script is still compatible with named older versions I can live with the workaround using one file for updating and verifying my collection and the other for downloading.

Thanks for all your good work, for the efforts you spend in this project, which was not even yours, and most of all for offering your work to the rest of us. Much appreciated.
avatar
timppu: What does that mean, "first login"? Do you mean trying to log in without valid cookies?
avatar
Geralt_of_Rivia: Exactly. Logging in from Firefox without valid cookies always give me ReCaptcha since a few days. That didn't happen before.
Odd. I tried the same when I wrote that, and for me it didn't.

Do you have some kind of extra adblockers and stuff which might prevent e.g. google scripts from working? I am otherwise using Firefox without add-ons or plug-ins and default settings, except I've set it to delete all offline data and cache (including cookies) whenever I close Firefox.