Failed to establish a new connection: [WinError 10060] A connection attempt failed because the conne

@JohnPT, some more info might be helpful. Your Python SDK single method call involves 2 API calls (on 2 different Dropbox servers)! It's not clear least which one fails. Some stacktrace would be fine. Does the same happen if you perform client object initialization with access token, instead of refresh token? Check that, if possible, on the machine where execution fails.

It fails on the final line the upload request. > print(dbx.files_upload(f.read(),filetouploadname, mode=dropbox.files.WriteMode("overwrite")))

I get a dbx object that looks fine in vscode.

I will try this. working to get trace and try on another machine. i am testing on windows 10 machine for test and prod.

Thank you for your help.

@JohnPT wrote:
...
It fails on the final line the upload request. > print(dbx.files_upload(f.read(),filetouploadname, mode=dropbox.files.WriteMode("overwrite")))
I get a dbx object that looks fine in vscode.
...

Just to add some clarification. Yes, for sure the code, you posted, is the only place where things can get wrong. It's the only place, in your code, where API calls get performed. The 'dbx' object itself can look fine after construction. Construction doesn't perform too much checks! You can construct Dropbox client object with completely wrong parameters and it will looks "fine". It wont look the same when you're going to execute some of its method though (where the actual mistakes get up). 😉

ok cool. thank you for the details.

Thanks for the access token idea.

I created a new app and used a new access code. that worked fine on both the local test and cloud test machine.

Not enough knowledge to know what that means?

Does that mean my orginal app is problematic?

Nothing has changed here and it does work on my test machine?

any thoughts?

Thank you for your kind help. still a bit of a newbie to DB. 😆

@JohnPT wrote:
...
I created a new app and used a new access code. that worked fine on both the local test and cloud test machine.

Not enough knowledge to know what that means?
...

That means your upload API call works, but your refresh API call seems problematic for some reason. When you're using access token refresh doesn't happen, so it lets limit the possible issues. The debug is going to go on here. Are you certain the same Dropbox SDK installed on all your machines? Next step can be to perform refresh by hand, on the machine where code fails - to see what's going on more close.

ok thanks.

current config - test machine - dropbox 11.18.0 - urllib3 1.26.3 : cloud machine - dropbox 11.25.0 - urllib3 1.26.8 a bit behind :<

(and hate to change midstream.. it's time )

upgrade both? to v11.36.0? i will do the test machine first.

should i do a pip --upgrade? or reinstall?

thanks for your help. 😆

Your versions are not too different, but it's good idea to be the same so when you do some test to be sure the result will be repeatable to max extent. Also it's good to be the last version (possible bug fixes etc.), in spite not mandatory. Do it however you like.

If something is going wrong still, as I said, check the refresh process by hand - it can show much more things - usable during debug.

Good luck.

makes sense. thank you. 😆

Hi. sorry to pester... still having the same issues.

i did a pip -upgrade (Successfully installed dropbox-11.36.0 cloud machine) and created new app with a refresh token.

same result - works fine on test (also did upgrade to 11.36.0) fails the same way in my cloud machine...

going to try to figure out the During handling of the above exception, another exception occurred:

error :

Exception has occurred: ConnectionError
HTTPSConnectionPool(host='api.dropboxapi.com', port=443): Max retries exceeded with url: /oauth2/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x000001BBB8E9DFD0>: Failed to establish a new connection: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'))

During handling of the above exception, another exception occurred:

File "Z:\users\........s\py-testupload.py", line 31, in <module>
print(dbx.files_upload(f.read(),filetouploadname, mode=dropbox.files.WriteMode("overwrite")))

any ideas?

thank you for your thoughts.

@JohnPT wrote:
...
Exception has occurred: ConnectionError
HTTPSConnectionPool(host='api.dropboxapi.com', port=443): Max retries exceeded with url: /oauth2/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x000001BBB8E9DFD0>: Failed to establish a new connection: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'))
...

As I said, the refreshing process fails. The 'api.dropbox.com' is involved in this. Seems you didn't try to refresh by hand. Why? 🧐 Try ping the host, at least, and try query the server with alternative tool, all on the failing machine.

Thanks, sorry i was more focused on the PIP upgrade and creating a new app/refreshtoken. thinking that the was the refresh you mention...

i guess not understanding "as I said, check the refresh process by hand sorry." was thinking that was the upgrade.. and the accesstoken did work and the refreshtoken not might indicate something with the app.

thanks for your patience. how do i check the "refresh process"? i thought that they never expired?

here is the ping

C:\Users\.....>ping api.dropbox.com

Pinging api-env.dropbox-dns.com [162.125.1.19] with 32 bytes of data:
Reply from 162.125.1.19: bytes=32 time=4ms TTL=55
Reply from 162.125.1.19: bytes=32 time=4ms TTL=55
Reply from 162.125.1.19: bytes=32 time=4ms TTL=55
Reply from 162.125.1.19: bytes=32 time=4ms TTL=55

Ping statistics for 162.125.1.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 4ms, Average = 4ms

@JohnPT, Yes refresh token doesn't expire. It's used for periodical retrieve/refresh access token anew. This happens with specific request to Dropbox server (usually performed by SDK internally). That's something that fails. Let's see why. Take a look here about details on how OAuth works (including the refresh - last request). 'curl' is in use there; you can use whatever you want.