[GH-ISSUE #162] Proxyman blocks Dropbox #159

Open
opened 2026-03-03 19:15:48 +03:00 by kerem · 1 comment
Owner

Originally created by @DeLoeribas on GitHub (Jun 6, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/162

Which Proxyman version are you using? (Ex. Proxyman 0.5 (200))

Version 1.4.1 (1410)

What OS Version are you using? (Ex. mac 10.13)

macOS Mojave 10.14.5

Steps to reproduce this issue

Proxyman gives a status code or 999 for a Connect method to https://bolt.dropbox.com

Screenshots (optional)

2019-06-06_20-23-46

Originally created by @DeLoeribas on GitHub (Jun 6, 2019). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/162 ### Which Proxyman version are you using? (Ex. Proxyman 0.5 (200)) Version 1.4.1 (1410) ### What OS Version are you using? (Ex. mac 10.13) macOS Mojave 10.14.5 ### Steps to reproduce this issue Proxyman gives a status code or 999 for a Connect method to https://bolt.dropbox.com ### Screenshots (optional) ![2019-06-06_20-23-46](https://user-images.githubusercontent.com/43988075/59057139-03b44e00-889a-11e9-8132-233005929f61.png)
Author
Owner

@NghiaTranUIT commented on GitHub (Jun 7, 2019):

Hey @DeLoeribas

Dropbox has the built-in SSL-Pinning mechanism to prevent all 3rd-party MITM (man in the middle) apps like Proxyman, Fiddler by using their own Dropbox certificate when verifying the source of requests and response.

Therefore, Proxyman is unable to intercept the data of https://bolt.dropbox.com and result in the 999 error code.

I would recommend that we shouldn't "Enable HTTPS Response" for Dropbox's domains.

If we enabled, we could disable it by righ-click on the app/domain, and select Disable.
Screen Shot 2019-06-07 at 10 22 27

Let me know if you need more help 😄

<!-- gh-comment-id:499744120 --> @NghiaTranUIT commented on GitHub (Jun 7, 2019): Hey @DeLoeribas Dropbox has the built-in [SSL-Pinning](https://security.stackexchange.com/questions/29988/what-is-certificate-pinning) mechanism to prevent all 3rd-party MITM (man in the middle) apps like Proxyman, Fiddler by using their own Dropbox certificate when verifying the source of requests and response. Therefore, Proxyman is unable to intercept the data of [https://bolt.dropbox.com](https://bolt.dropbox.com) and result in the 999 error code. I would recommend that we **shouldn't** "Enable HTTPS Response" for Dropbox's domains. If we enabled, we could disable it by righ-click on the app/domain, and select **Disable**. <img width="521" alt="Screen Shot 2019-06-07 at 10 22 27" src="https://user-images.githubusercontent.com/5878421/59079491-36982980-890e-11e9-9a47-e1673df12760.png"> Let me know if you need more help 😄
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#159
No description provided.