[GH-ISSUE #870] Can't reach http://proxy.man/ssl on iPhone #865

Open
opened 2026-03-03 19:22:32 +03:00 by kerem · 5 comments
Owner

Originally created by @parski on GitHub (Apr 26, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/870

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? (Ex. Proxyman 1.4.3)

2.24.0 (22400)

macOS Version? (Ex. mac 10.14)

11.0.1 (20B29)

Steps to reproduce

Premise:

I've closed all VPN programs (Wireguard and ProtonMail Bridge just to be sure) after a restart of the computer. I've only used Proxyman on Mac before, mostly for iOS Simulator and I have an installed and trusted root certificate on the Mac to enable SSL proxying.

IP in Proxyman instruction page matches what I see in my network settings.

en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 4c:20:b8:aa:97:5f
	inet6 fe80::1c18:c4c5:9de:9e1d%en1 prefixlen 64 secured scopeid 0xc
	inet 10.110.110.21 netmask 0xffffff00 broadcast 10.110.110.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active

On computer:

  1. Restart computer.
  2. Quit Wireguard and ProtonMail Bridge.
  3. Open Proxyman.

On iPhone:

  1. Open Settings → Wi-Fi → ⓘ on the cell of the network phone and Mac are connected to → Configure Proxy
  2. Select Manual.
  3. Enter server as computer IP and Port 9090.
  4. Open Safari and go to http://proxy.man/ssl

Expected behavior

I'm extecting certificate things to happen.

Screenshots (optional)

Screenshot 2021-04-26 at 11 03 59

Open Proxyman ports:

parski@savoy ~ % sudo lsof -PiTCP -sTCP:LISTEN | grep Proxyman
Proxyman  618 parski   14u  IPv4 0xf8d368867453dd51      0t0  TCP *:9090 (LISTEN)
Proxyman  618 parski   15u  IPv4 0xf8d3688677cec941      0t0  TCP localhost:10090 (LISTEN)
Proxyman  618 parski   28u  IPv6 0xf8d368867452a489      0t0  TCP *:10909 (LISTEN)

IMG_0817
IMG_0818
Screenshot 2021-04-26 at 11 16 06

Originally created by @parski on GitHub (Apr 26, 2021). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/870 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? (Ex. Proxyman 1.4.3) 2.24.0 (22400) ### macOS Version? (Ex. mac 10.14) 11.0.1 (20B29) ### Steps to reproduce **Premise**: I've closed all VPN programs (Wireguard and ProtonMail Bridge just to be sure) after a restart of the computer. I've only used Proxyman on Mac before, mostly for iOS Simulator and I have an installed and trusted root certificate on the Mac to enable SSL proxying. IP in Proxyman instruction page matches what I see in my network settings. ```sh en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 4c:20:b8:aa:97:5f inet6 fe80::1c18:c4c5:9de:9e1d%en1 prefixlen 64 secured scopeid 0xc inet 10.110.110.21 netmask 0xffffff00 broadcast 10.110.110.255 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: active ``` On computer: 1. Restart computer. 2. Quit Wireguard and ProtonMail Bridge. 3. Open Proxyman. On iPhone: 1. Open Settings → Wi-Fi → ⓘ on the cell of the network phone and Mac are connected to → Configure Proxy 2. Select Manual. 3. Enter server as computer IP and Port 9090. 4. Open Safari and go to **http://proxy.man/ssl** ### Expected behavior I'm extecting certificate things to happen. ### Screenshots (optional) <img width="572" alt="Screenshot 2021-04-26 at 11 03 59" src="https://user-images.githubusercontent.com/2445818/116057457-1cd96a00-a67f-11eb-9305-276accb4c8d0.png"> Open Proxyman ports: ```sh parski@savoy ~ % sudo lsof -PiTCP -sTCP:LISTEN | grep Proxyman Proxyman 618 parski 14u IPv4 0xf8d368867453dd51 0t0 TCP *:9090 (LISTEN) Proxyman 618 parski 15u IPv4 0xf8d3688677cec941 0t0 TCP localhost:10090 (LISTEN) Proxyman 618 parski 28u IPv6 0xf8d368867452a489 0t0 TCP *:10909 (LISTEN) ``` ![IMG_0817](https://user-images.githubusercontent.com/2445818/116058483-2f07d800-a680-11eb-99dd-21b3be1c5da1.PNG) ![IMG_0818](https://user-images.githubusercontent.com/2445818/116058550-3fb84e00-a680-11eb-93b7-853ef95467cb.PNG) <img width="1625" alt="Screenshot 2021-04-26 at 11 16 06" src="https://user-images.githubusercontent.com/2445818/116059133-d127c000-a680-11eb-8fac-cdcaacb5291d.png">
Author
Owner

@NghiaTranUIT commented on GitHub (Apr 26, 2021):

@parski Look like the problem is from the External Proxy. Can you temporarily disable it and try again (Open http://proxy.man/ssl on your iOS Devices) 🤔

<!-- gh-comment-id:826665191 --> @NghiaTranUIT commented on GitHub (Apr 26, 2021): @parski Look like the problem is from the External Proxy. Can you temporarily disable it and try again (Open http://proxy.man/ssl on your iOS Devices) 🤔
Author
Owner

@NghiaTranUIT commented on GitHub (Apr 26, 2021):

Just wondering: After setting the HTTP Proxy on your iOS Device and you could not open http://proxy.man/ssl.

Are you able to access other domains? such as opening https://google.com from your Safari 🤔 I would like to verify that the problem is from the proxy or from the http://proxy.man/ssl

<!-- gh-comment-id:826668101 --> @NghiaTranUIT commented on GitHub (Apr 26, 2021): Just wondering: After setting the HTTP Proxy on your iOS Device and you could not open http://proxy.man/ssl. Are you able to access other domains? such as opening https://google.com from your Safari 🤔 I would like to verify that the problem is from the proxy or from the http://proxy.man/ssl
Author
Owner

@NghiaTranUIT commented on GitHub (Apr 26, 2021):

One more thing to investigate the bug @parski

When you have External Proxy Config, but you could not access http://proxy.man/ssl from your iOS device, please try to open it from your Safari/GoogleChrome on your Macbook.

  • If it works, you are able to download the certificate on your mac. It means the domain is working, and something in your cooperated network blocks it.
  • If not, it means there is a bug from http://proxy.man/ssl => Need to fix
<!-- gh-comment-id:826677990 --> @NghiaTranUIT commented on GitHub (Apr 26, 2021): One more thing to investigate the bug @parski When you have External Proxy Config, but you could not access http://proxy.man/ssl from your iOS device, please try to open it from your Safari/GoogleChrome on your Macbook. - If it works, you are able to download the certificate on your mac. It means the domain is working, and something in your cooperated network blocks it. - If not, it means there is a bug from `http://proxy.man/ssl` => Need to fix
Author
Owner

@parski commented on GitHub (Apr 26, 2021):

Disabling External Proxy solves this issue. Not sure if this is a bug but I'm happy with the workaround.

<!-- gh-comment-id:826689670 --> @parski commented on GitHub (Apr 26, 2021): Disabling External Proxy solves this issue. Not sure if this is a bug but I'm happy with the workaround.
Author
Owner

@NghiaTranUIT commented on GitHub (Apr 26, 2021):

Thanks for the input @parski 👍

I tested on my machine:

  1. Open Charles Proxy at port 8888
  2. Open Proxyman, then setting the External Proxy to 127.0.0.1 at port 8888 (Charles Proxy is like a Proxy Server).
  3. Make sure the Internet is still working and I'm able to access the Internet => Setup correctly
  4. Set HTTP Proxy on iOS devices with the configuration from Proxyman app.
  5. Try to open http://proxy.man/ssl from my iOS device

and it's still working.

I suppose that your External Proxy causes the bug, like you've fixed it by disabling it. I will keep investigating it 👍

<!-- gh-comment-id:826715163 --> @NghiaTranUIT commented on GitHub (Apr 26, 2021): Thanks for the input @parski 👍 I tested on my machine: 1. Open Charles Proxy at port 8888 2. Open Proxyman, then setting the External Proxy to 127.0.0.1 at port 8888 (Charles Proxy is like a Proxy Server). 3. Make sure the Internet is still working and I'm able to access the Internet => Setup correctly 4. Set HTTP Proxy on iOS devices with the configuration from Proxyman app. 5. Try to open http://proxy.man/ssl from my iOS device and it's still working. I suppose that your External Proxy causes the bug, like you've fixed it by disabling it. I will keep investigating it 👍
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#865
No description provided.