starred/Proxyman

Fork 0

mirror of https://github.com/ProxymanApp/Proxyman.git synced 2026-04-25 16:15:55 +03:00

[GH-ISSUE #1884] Issues with running Map Remote. Map Remote not mapping. #1876

New issue

Open

opened 2026-03-03 19:55:07 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 19:55:07 +03:00

Owner

Originally created by @maciejpigulski on GitHub (Dec 15, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1884

Description

I have tried everything and I still cannot get map remote to work.

Simplest possible rule:

Give me back the "Welcome to Local Proxyman Server" page.

I give up. Help?

Originally created by @maciejpigulski on GitHub (Dec 15, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1884 ## Description I have tried everything and I still cannot get map remote to work. Simplest possible rule: ![image](https://github.com/ProxymanApp/Proxyman/assets/7657893/19a9bf86-4123-4b98-8cad-9db499663c0d) Give me back the "Welcome to Local Proxyman Server" page. ![image](https://github.com/ProxymanApp/Proxyman/assets/7657893/77b56ce1-99b0-442b-b5b3-35caeb5260f7) I give up. Help?

kerem added the

question

label

2026-03-03 19:55:07 +03:00

kerem commented

2026-03-03 19:55:07 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Dec 15, 2023):

If you use localhost:3000 or something it's not port 9090. It will work.

Localhost and port 9090 are reserved for the local Proxyman server -> It's a reason why you get a Local Proxy Server Response.

If you're not familiar with the Map Remote, you might use the Scripting. Here is the snippet code: https://docs.proxyman.io/scripting/snippet-code#http-to-https

function onRequest(context, url, request) {
    request.scheme = "https";
    request.port = 443; // Don't forget to override the port
    return request;
}

@NghiaTranUIT commented on GitHub (Dec 15, 2023): If you use `localhost:3000` or something it's not port 9090. It will work. Localhost and port 9090 are reserved for the local Proxyman server -> It's a reason why you get a Local Proxy Server Response. If you're not familiar with the Map Remote, you might use the Scripting. Here is the snippet code: https://docs.proxyman.io/scripting/snippet-code#http-to-https ```js function onRequest(context, url, request) { request.scheme = "https"; request.port = 443; // Don't forget to override the port return request; } ```

kerem commented

2026-03-03 19:55:07 +03:00

Author

Owner

@maciejpigulski commented on GitHub (Dec 19, 2023):

I have tried 3000 and 9091 so it is not 9090 but still fail to get the rule to work. This looks like something else is wrong.

When trying exact IP instead of localhost has the same result:

Haven't tried scripting yet.

@maciejpigulski commented on GitHub (Dec 19, 2023): I have tried `3000` and `9091` so it is not `9090` but still fail to get the rule to work. This looks like something else is wrong. <img width="1743" alt="image" src="https://github.com/ProxymanApp/Proxyman/assets/7657893/12ec8bc0-8cbf-44a5-8877-fefb0996922e"> When trying exact IP instead of localhost has the same result: <img width="1729" alt="image" src="https://github.com/ProxymanApp/Proxyman/assets/7657893/06171c3d-0856-4a29-baf9-5d2c574cbfdf"> Haven't tried scripting yet.

kerem commented

2026-03-03 19:55:08 +03:00

Author

Owner

@maciejpigulski commented on GitHub (Dec 19, 2023):

Ok I begin to understand what you have meant.

So for the setup I need to get to work I should never point to the port of ProxyMan, it will just show me the page and won't allow to do any redirects from there. Changing ProxyMan port just changes where it is listening for external calls to install the certificate if needed.

Second thing, assuming ProxyMan running on 9090, my local server on 3000 and from my local server I will be calling some external host say: external.host.url.com I should:

turn on macOS proxy Overridden and capture any calls that go through the OS,
when there is a call to external.host.url.com then I override it in ProxyMan with whatever remote address I want i.e. google.com.

Now I also begin to understand why I was able to get Map Remote in the past (it is not the first time I use it) and failed this time.

I am using Cisco Secure Client VPN (5.0.03072). When VPN is enabled to access external.host.url.com that is otherwise inaccessible then I get no traffic in ProxyMan with macOS proxy Overridden.

My initial idea was that I will redirect all the traffic from my localhost:3000 server to ProxyMan's running port. This though proved to not work as I would expect it to work because of the reasons mentioned in this conversation.

Is there a way to achieve what I need using ProxyMan?

@maciejpigulski commented on GitHub (Dec 19, 2023): Ok I begin to understand what you have meant. So for the setup I need to get to work I should never point to the port of ProxyMan, it will just show me the page and won't allow to do any redirects from there. Changing ProxyMan port just changes where it is listening for external calls to install the certificate if needed. Second thing, assuming ProxyMan running on `9090`, my local server on `3000` and from my local server I will be calling some external host say: `external.host.url.com` I should: - turn on `macOS proxy Overridden` and capture any calls that go through the OS, - when there is a call to `external.host.url.com` then I override it in ProxyMan with whatever remote address I want i.e. `google.com`. Now I also begin to understand why I was able to get `Map Remote` in the past (it is not the first time I use it) and failed this time. I am using Cisco Secure Client VPN (5.0.03072). When VPN is enabled to access `external.host.url.com` that is otherwise inaccessible then I get no traffic in ProxyMan with `macOS proxy Overridden`. My initial idea was that I will redirect all the traffic from my localhost:3000 server to ProxyMan's running port. This though proved to not work as I would expect it to work because of the reasons mentioned in this conversation. Is there a way to achieve what I need using ProxyMan?