mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 08:35:53 +03:00
[GH-ISSUE #851] Chrome error: NET::ERR_CERT_COMMON_NAME_INVALID #846
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#846
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chaoyangnz on GitHub (Apr 8, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/851
Originally assigned to: @NghiaTranUIT on GitHub.
Proxyman version? (Ex. Proxyman 1.4.3)
latest
macOS Version? (Ex. mac 10.14)
10.15
Steps to reproduce
I forward requests in Chrome to Proxyman. then I got the error
Expected behavior
Screenshots (optional)
@NghiaTranUIT commented on GitHub (Apr 8, 2021):
Hi @chaoyangnz, thanks for opening the ticket. I have few questions:
It looks like your domains has special character, so Proxyman couldn't generate a certificate with correct CommonName
@chaoyangnz commented on GitHub (Apr 8, 2021):
@NghiaTranUIT I suppose there is no domain, just IP address. why there is no domain, because I am using Proxifier to route the requests to Proxyman, not sure why Proxifier is not leaving the name resolve to downstream proxy, maybe my wrong configuration. But whatever, you can try to point a raw IP address access using Proxyman. that should be able to reproduce.
@NghiaTranUIT commented on GitHub (Apr 8, 2021):
If I access https://, for example,
https://142.250.66.46(142.250.66.46 is google.com server), I still get the Error from Google Chrome without using Proxyman app.It causes because the Certificate's Common Name from Google.com doesn't contain the IP, so Google Chrome would reject it.
Therefore, I will happen with Proxyman app too
@NghiaTranUIT commented on GitHub (Apr 8, 2021):
The logic behind of generating the Certificate from Proxyman is that:
So, if the original Common Name in the certificate doesn't contain the IP, the Proxyman Certificate will not have the IP too. Therefore, Google Chrome will reject it (as I discuss in the previous comment)
Just wondering:
Do it works with other Proxy tools, like Fiddler or Charles 🤔
@NghiaTranUIT commented on GitHub (Apr 8, 2021):
@chaoyangnz Maybe you have to fix the Proxifier to make it uses the domain instead of the raw IP address.
Access to
https://<ip>will result in the Certificate Error even though Proxyman is not opening. Ref: https://stackoverflow.com/questions/33419568/accessing-https-sites-with-ip-address@chaoyangnz commented on GitHub (Apr 8, 2021):
@NghiaTranUIT yep, that is caused by my wrong config in Proxifier, it should resolve dns through downstream proxy.
another thing i noticed, even though I disabled
override macOS proxy, I found requests in myjavaprogram still go through Proxyman. I don't know what is the magic, I even didn't config proxy for my java server and double checked MacOS global proxy is not on.@NghiaTranUIT commented on GitHub (Apr 8, 2021):
Look like the connection from your Java App is still alive, and still connect through Proxyman Proxy Server. Restart your app might fix the problem 👍
@chaoyangnz commented on GitHub (Apr 8, 2021):
@NghiaTranUIT I did restart my java server and Proxyman as well.
all the request method is
CONNECT, that is true.but how can i make connection stop alive and captured by Proxyman? last resort is restarting my laptop :)
@NghiaTranUIT commented on GitHub (Apr 8, 2021):
If you try to restart the Proxyman (By quitting the app or clicking on the Start/Stop button), but your connection is still alive. I'm not sure how to fix it 🤔
Maybe it's a bug from Java?
Because as soon as click on the Start/Stop, it will start/stop the local proxy server.
@chaoyangnz commented on GitHub (Apr 9, 2021):
thanks @NghiaTranUIT close this issue. the original issue is caused by buggy Proxifier.