-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
file ID [ ... ] is not shared, while the file is existing #10
Comments
I have the same issue, cannot download a file thats 1 Gb |
Unfortunately, I cannot replicate your situations. In my environment, I could confirm that a 4 GB file, which was publicly shared, could be downloaded. For example, when the file is downloaded by the partial download, what result will you get? Ref |
Same problem here with a 7GB+ file. The file is shared by someone else so I tried to copy it on my drive but it didn't help. I tried the following commands:
|
Thank you for your comment. When the error message of For example, when you confirm such file using the method of Files: get in Drive API, what result will you get? In this case, please use |
Ah, using the GET method, I find this new error:
That would explain the issue. Would be nice if that error message was passed on (what is odd is that I can still download the file using the web interface just fine. |
I have the same message. I tried to download it with the web interface in a private window (so I'm not logged in) and I can download the file. |
Same here. |
Thank for the explain, can anyone explain how to make goodls use IPv6 instead IPv4 to bypass download limitation ! |
Basically, goodls has stopped working for me over the past few months. I always get the same error file ID [ ... ] is not shared, while the file is existing (actual file ID redacted). These are typically large files in the couple GB range. I thought maybe it was a size limit, 24-hour lock out period, but it has been days and days since I've tried a download, and probably a month or two since it actually worked.
The text was updated successfully, but these errors were encountered: