[kaleem818]

gdrive login cookies keep expiring after 1 or 2 hours
15.07.23 19.50.23 <--> 14.07.23 00.12.25 jdlog://0946311370661/
log id

[pspzockerscene]

Which addon did you use to add your Google Drive cookies?
Which browser did you use?

Did you maybe kill your own cookies by mistake e.g. by logging out in the browser-session the cookies came from?

I can't reproduce this issue here.
Browser: Chrome
Addon used for cookie export: EditThisCookie

[MA RYAND]

Originally Posted by kaleem818

gdrive login cookies keep expiring after 1 or 2 hours
15.07.23 19.50.23 <--> 14.07.23 00.12.25 jdlog://0946311370661/
log id

my gdrive login cookies keep expiring after 5 or 10 min

[kaleem818]

i am using firefox browser and add is edit this cookie
no i did not log out from the login session

[pspzockerscene]

Try Chrome and EditThisCookie and see if the same issue will happen there too.

[MA RYAND]

Originally Posted by pspzockerscene

Try Chrome and EditThisCookie and see if the same issue will happen there too.

i use Chrome and EditThisCookie

but gdrive login cookies keep expiring after 5 or 10 min again.

[pspzockerscene]

This one is really hard to debug especially because I can't reproduce here.
It could be all kinds of new restrictions/checks by google.
To all users who posted here:
- Where are you from (Country)?
- Which ISP do you have?
- Are you using a VPN and/or do you often switch your IP?
- Can you reproduce this problem with different Google accounts consistently or only with one/your main Google Drive account?
- Can you reproduce this problem on other systems too [same Google account]?

[patbowling89]

Hello All,

I am currently using jdownloader on docker with jlesage/jdownloader-2 latest Docker Image and sudenly since a week ago or more my cookies expired as they always do after a couple months, so I went to edit this cookie and got new ones and updated it on My.Jdownloader site however they now keep expiring after 15-30 min, I have tried getting new cookies from Flag Cookies and same thing.

I even deleted my current docker container, removed image, deleted config folder and everything to start installation from scratch but same thing keeps happening.:outch:

Any help would be greatly appreciated.

[pspzockerscene]

Merged same-topic threads.

@patbowling89
I do see these reports of multiple users but I was not yet able to reproduce any of these issues.
In my test-environment I got GDrive cookies which are 6+ months old and never expired.

If at all, this is a plugin issue. Re-installing JD will not solve plugin issues.

[Sonatine]

My issue is specifically with YouTube, but as my symptoms are identical to what others have posted here, and both are Google services, I thought this may be the best thread to report my issue also (my apologies if, regardless, I should have added this to the dedicated YouTube thread).

My login cookies are expiring for YouTube in exactly the same manner as the others have described for Drive - anywhere from 15 mins - 1 hour after exporting and refreshing them. I've reimported my cookies multiple times (at least 7-8 times yesterday within a few hours) in a session, and during that time never closed my connection, my browser or JDownloader, yet after a short time the cookies show as expired.

The other information requested:

Location: United Kingdom
ISP: Three
VPN: No
Can I reproduce this problem: I don't currently have another system with which to test, but I've added a different Drive account to see if the same occurs with that.
Browser: Firefox
Plugin: Flag Cookies

[Sonatine]

I can now confirm that for me the issue is also with Google Drive logins - I added two different Google Drive accounts (one on the same Google account as the YouTube login, one entirely separate), and the login expired on one almost instantaneously, the other an hour or so later. I refreshed the logins on all accounts and all expired again at some point later (this time I didn't make a note of the time, I just noticed the icon appearing in JDownloader.)

[Perene]

I can't provide you a log because this is a random event which I cannot reproduce whenever I want, but it's been perhaps 3-4 times in the last days that my cookies are expiring with JDW. Before that, it took lots of days.

The only difference in what I am using here is that Cloudfare DNS (1.1.1.1), which I may or may not enable the regular DNS or "WARP". But even if I switch between those daily, it should NEVER expire my cookies, since I am already logged using the EDGE browser in that same (GOOGLE) account.

Also, I added two sets of cookies, for Youtube and then Google (Drive). From the same account. Both are expiring.

That signals to me your idea explained here:

https://support.jdownloader.org/Know...instructions/3

Is being broken by Google itself.

NOTE: I have other servers added here, for a lot more time, and none of them have expired cookies. It's solely Google's fault, please investigate what kind of shenanigans they are doing to interfere with this.

[Perene]

P.S. Debug log is now active, and before I did this, GD and Youtube were added back again, with the same free account, in the plugin area.

I am going to let DEBUG LOG enabled, so I can catch it next time it happens. In the meantime, if possible check this out, or wait for a future log.

EDIT:

Here it is

It expired that quick:

13.08.23 22.54.41 <--> 14.08.23 00.30.47 jdlog://1707311370661/

Now I can say the debug log caught that

[pspzockerscene]

Merged threads about the same topic.

I haven't found the cause of this yet and I wasn't able to reproduce this problem yet.

[Perene]

The problem is repeating itself and I don't think this is related to my use of Cloudfare's DNS (I can switch between WARP, regular Cloudfare, or turn both off and use my ISP's). Somehow Google is blocking JDW's cookies after less than 1 hour, and that applies to Google Drive and Youtube (I added both cookies).

One thing I noticed in Google's account control panel is that now they list all sites that used Google's login, in here:

**External links are only visible to Support Staff****External links are only visible to Support Staff**

They must have modified how this is handled by JDW and you need to do some changes for these cookies to not expire so soon...

I am also trying a free Google account.

[pspzockerscene]

Okay again:
I'am absolutely aware that this issue exists but I'm still unable to reproduce this.
I got two Google Accounts in my dev JD with cookies that are 6+ months old.
Also I did two more tests today and in both cases the cookies are still valid more than 5 hours later.

Also that subpage you posted is not new and it simply shows the services, connected to your google account via API. This is something totally different than what JD is doing (just re-using your browser-session)!

Please try the following:

1. Go to this website, copy your User-Agent string and put it in JD under Settings -> Plugins -> drive.google.com -> User-Agent
2. Delete all drive.google.com accounts in your JD if any are left.
3. Use Chrome + EditThisCookie to export your cookies and re-add your google drive account to JD.
4. Now check if your cookies are valid for a longer time.

[UnknownEntryEvent]

Just adding that I've been getting the same issue with drive/google cookie expiring within 30 min or so, for the past week or two.

I have to re-log in and get a new cookie each time. I guess it is somehow triggers expired when the automatic log-out in the web client would have occurred? Since whenever I go back to get a new cookie after it expires, it forces me to log in again.

[pspzockerscene]

Well if it works as desired, it would behave like the browser so yes theoretically when the session expires in JD it is expired via browser too - I thought this would not be the case here.

Did you maybe forget to set this checkbox "trust this device" (or similar) when you've logged in via browser.

[Chicken++]

Originally Posted by Sonatine

[...] and during that time never closed my connection, my browser or JDownloader, yet after a short time the cookies show as expired.

I have had a similar issue (though admittedly not for very long), and so far, it seems I managed to fix it.

Try this:

Step 1: Get Cookies from browser, paste them into Jdownloader

Step 2: CLOSE YOUR INTERNET BROWSER and DON'T OPEN IT AGAIN. (or maybe just the all tabs related to Google in general)

That's it.



My guess is that - depending on what browser you use, or perhaps browser settings or version - your browser silently keeps requesting new cookies in the background, even without a page refresh, which invalidates the old cookies server-side that Jdownloader has. Just a hunch. I might be wrong on the technical details.

Which would explain why the behavior differs so wildly for different users.

Personally, I am logged into the Google-account used by Jdownloader only on a secondary browser (Edge) that I don't use for much else.

I only began noticing oddities when I had to switch to a third browser (Opera) for Google Drive but not for Youtube (long story that isn't relevant here), and noticed how only my Google Drive cookies kept expiring despite me only downloading from Youtube that day. (Yes both are logged into the same Google account. No, neither got logged out in-browser.)

My natural instinct was to keep Opera open to more easily re-export cookies. The cookies stopped expiring once I just closed Opera. So there.






Here's how to test if this solves your problem:

Test A: Get cookies from browser, paste into Jdownloader, but don't actually download anything.
Keep both Jdownloader and browser tab with Google Drive open for however long it usually takes for your cookies to expire (hours? minutes?)
Did your cookies expire despite not even downloading anything?

Test B: Get cookies from browser, paste into Jdownloader. Then go to bed and sleep for several hours.
Turn on PC, open Jdownloader (but not your browser). Check if cookies are still valid. ;-)


I'd be curious to hear if I actually stumbled into a helpful solution by total chance accident XD

[pspzockerscene]

@Chicken++

LOL I was actually just able to confirm this 100%.
This would also mean that there is nothing we can do about this other than updating our login-dialoge for google logins.
Before doing anything I will wait for more feedback of other users regarding this topic.