Can't mount

Question

Can't mount

rgb5100 opened this issue 2 years ago · 11 comments

Hello, I would like to use my 516.16GB from Degoo on Linux and I came across this repository. I tried to mount it but the mount fails.
Command:
python3 fuse_degoo.py --mountpoint /home/user/degoo --degoo-email ************************* --debug --debug-fuse --degoo-pass ****************************************************************************************************

Logs:
2022-06-29 15:45:56.785 MainThread: [main] ##### Initializating Degoo drive #####
2022-06-29 15:45:56.785 MainThread: [main] Local mount point: /home/user/degoo
2022-06-29 15:45:56.786 MainThread: [main] Cache size: 15728640 kb
2022-06-29 15:45:56.786 MainThread: [main] Degoo email: *************************
2022-06-29 15:45:56.786 MainThread: [main] Degoo pass: ****************************************************************************************************
2022-06-29 15:45:56.786 MainThread: [main] Root Degoo path: /
2022-06-29 15:45:56.786 MainThread: [main] Refresh interval: 600 seconds
2022-06-29 15:45:56.786 MainThread: [main] Flood control: Disabled
2022-06-29 15:45:56.786 MainThread: [main] Change hostname: Disabled
2022-06-29 15:45:56.786 MainThread: [main] Search split files: Disabled
2022-06-29 15:45:56.786 MainThread: [main] Mode: lazy
2022-06-29 15:45:56.786 MainThread: [main] Reading Degoo content from directory /
Token and/or refresh token does not found. Login with Degoo
2022-06-29 15:45:56.789 MainThread: [urllib3.connectionpool] Starting new HTTPS connection (1): rest-api.degoo.com:443
2022-06-29 15:45:56.854 MainThread: [urllib3.connectionpool] https://rest-api.degoo.com:443 "POST /login HTTP/1.1" 429 0
Token expired. Refreshing
2022-06-29 15:45:56.857 MainThread: [urllib3.connectionpool] Starting new HTTPS connection (1): rest-api.degoo.com:443
2022-06-29 15:45:56.898 MainThread: [urllib3.connectionpool] https://rest-api.degoo.com:443 "POST /access-token HTTP/1.1" 429 None
2022-06-29 15:45:56.905 MainThread: [urllib3.connectionpool] Starting new HTTPS connection (1): production-appsync.degoo.com:443
2022-06-29 15:45:57.105 MainThread: [urllib3.connectionpool] https://production-appsync.degoo.com:443 "POST /graphql HTTP/1.1" 401 129
Traceback (most recent call last):
File "/home/user/Downloads/degoo_drive/fuse_degoo.py", line 959, in
main()
File "/home/user/Downloads/degoo_drive/fuse_degoo.py", line 919, in main
operations.load_degoo_content()
File "/home/user/Downloads/degoo_drive/fuse_degoo.py", line 789, in load_degoo_content
degoo_tree_content = degoo.tree_cache(mode=self._mode)
File "/home/user/Downloads/degoo_drive/degoo/init.py", line 2032, in tree_cache
tree(dir_id, show_times, _done, mode=mode)
File "/home/user/Downloads/degoo_drive/degoo/init.py", line 1988, in tree
kids = get_children(dir_id)
File "/home/user/Downloads/degoo_drive/degoo/init.py", line 1452, in get_children
CACHE_CONTENTS[dir_id] = api.getFileChildren5(dir_id)
File "/home/user/Downloads/degoo_drive/degoo/init.py", line 831, in getFileChildren5
raise DegooError(f"getFileChildren5 failed with: {response}")
degoo.DegooError: getFileChildren5 failed with: <Response [401]>

Answer 1 · 2022-07-02T14:15:04.000Z

You must use --degoo-token and --degoo-refresh-token as it is explained in bypass login

Answer 2 · 2022-07-03T07:46:51.000Z

It was of no use. Also with --degoo-token and --degoo-refresh-token. I'm on a LMDE5 with lvm encrypted.
The following came out on the command line:
2022-07-03 09:42:24.345 MainThread: [main] ##### Initializating Degoo drive #####
2022-07-03 09:42:24.345 MainThread: [main] Local mount point: /home/user/degoo
2022-07-03 09:42:24.345 MainThread: [main] Cache size: 15728640 kb
2022-07-03 09:42:24.345 MainThread: [main] Degoo token: **********
2022-07-03 09:42:24.345 MainThread: [main] Degoo refresh token: **********
2022-07-03 09:42:24.345 MainThread: [main] Root Degoo path: /
2022-07-03 09:42:24.345 MainThread: [main] Refresh interval: 600 seconds
2022-07-03 09:42:24.345 MainThread: [main] Flood control: Disabled
2022-07-03 09:42:24.345 MainThread: [main] Change hostname: Disabled
2022-07-03 09:42:24.345 MainThread: [main] Search split files: Disabled
2022-07-03 09:42:24.345 MainThread: [main] Mode: lazy
2022-07-03 09:42:24.346 MainThread: [main] Reading Degoo content from directory /
2022-07-03 09:42:24.349 MainThread: [urllib3.connectionpool] Starting new HTTPS connection (1): production-appsync.degoo.com:443
2022-07-03 09:42:25.063 MainThread: [urllib3.connectionpool] https://production-appsync.degoo.com:443 "POST /graphql HTTP/1.1" 401 129
Traceback (most recent call last):
File "/home/user/Dokumente/degoo_drive/fuse_degoo.py", line 959, in
main()
File "/home/user/Dokumente/degoo_drive/fuse_degoo.py", line 919, in main
operations.load_degoo_content()
File "/home/user/Dokumente/degoo_drive/fuse_degoo.py", line 789, in load_degoo_content
degoo_tree_content = degoo.tree_cache(mode=self._mode)
File "/home/user/Dokumente/degoo_drive/degoo/init.py", line 2032, in tree_cache
tree(dir_id, show_times, _done, mode=mode)
File "/home/user/Dokumente/degoo_drive/degoo/init.py", line 1988, in tree
kids = get_children(dir_id)
File "/home/user/Dokumente/degoo_drive/degoo/init.py", line 1452, in get_children
CACHE_CONTENTS[dir_id] = api.getFileChildren5(dir_id)
File "/home/user/Dokumente/degoo_drive/degoo/init.py", line 831, in getFileChildren5
raise DegooError(f"getFileChildren5 failed with: {response}")
degoo.DegooError: getFileChildren5 failed with: <Response [401]>

Answer 3 · 2022-07-03T08:13:08.000Z

There must be something wrong with the tokens because you are getting a 401 (Unauthorized) response. Try modifying the keys.json file which should be in the ~/.config/degoo path. And remember not use --degoo-token and --degoo-refresh-token

Answer 4 · 2022-07-04T10:01:57.000Z

What should the ~/.config/degoo/keys.json look like? My token starts with ey. You can give me an example where $TOKEN is the token and $REFRESH-TOKEN is the refresh-token. I don't know json. I also cleared everything in ~/.config/degoo/.

Answer 5 · 2022-07-05T14:34:30.000Z

You can see how they are obtained from the link above. There is a screenshot where you can see part of both tokens: bypass login

Answer 6 · 2022-07-09T20:10:04.000Z

I get the same error. I logged in and pasted the json response from login into the ~/.config/degoo/keys.json.

Answer 7 · 2022-07-13T15:28:39.000Z

I don't think I'm going to be able to help you much more. To access you need both tokens and the way to use them is one of two options:

Using the arguments --degoo-token and --degoo-refresh-token.
By directly editing the --keys.json file.

Answer 8 · 2022-07-13T15:35:04.000Z

Could you make any video tutorial ?

Answer 9 · 2022-07-13T16:04:49.000Z

Honestly, I don't think a video is necessary. There are all the commands to install dependencies, several examples and how to access with tokens with the help of the browser developer tools

Answer 10 · 2022-07-30T18:53:06.000Z

Just an update on this, I'm getting 400 here with both user/pass, as well as token/refreshToken.

2022-07-30 18:51:23.365 MainThread: [__main__] ##### Initializating Degoo drive #####
2022-07-30 18:51:23.365 MainThread: [__main__] Local mount point:   /home/degoo
2022-07-30 18:51:23.365 MainThread: [__main__] Cache size:          15728640 kb
2022-07-30 18:51:23.365 MainThread: [__main__] Degoo token:         **********
2022-07-30 18:51:23.366 MainThread: [__main__] Degoo refresh token: **********
2022-07-30 18:51:23.366 MainThread: [__main__] Root Degoo path:     /
2022-07-30 18:51:23.366 MainThread: [__main__] Refresh interval:    600 seconds
2022-07-30 18:51:23.366 MainThread: [__main__] Flood control:       Disabled
2022-07-30 18:51:23.366 MainThread: [__main__] Change hostname:     Disabled
2022-07-30 18:51:23.366 MainThread: [__main__] Search split files:  Disabled
2022-07-30 18:51:23.366 MainThread: [__main__] Mode:                lazy
2022-07-30 18:51:23.366 MainThread: [__main__] User access:         True
2022-07-30 18:51:23.366 MainThread: [__main__] Reading Degoo content from directory /
2022-07-30 18:51:23.369 MainThread: [urllib3.connectionpool] Starting new HTTPS connection (1): production-appsync.degoo.com:443
2022-07-30 18:51:24.020 MainThread: [urllib3.connectionpool] https://production-appsync.degoo.com:443 "POST /graphql HTTP/1.1" 400 126
Traceback (most recent call last):
  File "/root/degoo_drive/fuse_degoo.py", line 959, in <module>
    main()
  File "/root/degoo_drive/fuse_degoo.py", line 919, in main
    operations.load_degoo_content()
  File "/root/degoo_drive/fuse_degoo.py", line 789, in load_degoo_content
    degoo_tree_content = degoo.tree_cache(mode=self._mode)
  File "/root/degoo_drive/degoo/__init__.py", line 2032, in tree_cache
    tree(dir_id, show_times, _done, mode=mode)
  File "/root/degoo_drive/degoo/__init__.py", line 1988, in tree
    kids = get_children(dir_id)
  File "/root/degoo_drive/degoo/__init__.py", line 1452, in get_children
    __CACHE_CONTENTS__[dir_id] = api.getFileChildren5(dir_id)
  File "/root/degoo_drive/degoo/__init__.py", line 831, in getFileChildren5
    raise DegooError(f"getFileChildren5 failed with: {response}")
degoo.DegooError: getFileChildren5 failed with: <Response [400]>```

Answer 11 · 2022-08-04T18:46:27.000Z

@QrchackOfficial Check that the keys.json and default_properties.txt files are in the correct path. I have uploaded an update that checks that both files exist and that the keys have a value of