Hi, I need help connecting an iPhone simulator with the WireMock server. I’m running a

standalone version 3.4.1

I have set up my Mac machine network to use HTTP and HTTPS to my local address with specified ports: • port = 9999 • https-port = 2424 IP: • Tried both 127.0.0.1 and actual local IP address. I have also set up my own certificate using OpenSSL and keytool and I’m adding these when starting the server: • --https-keystore cert/keystore.jks • --keystore-password xxx • --key-manager-password xxx • --keystore-type JKS Additional flags I set for running a server: • --proxy-all “https://censored.net” • --https-port 2424 • --verbose • --bind-address 0.0.0.0 • --preserve-host-header • --enable-browser-proxying • --trust-all-proxy-targets I have installed the

server.cert

that was generated via. OpenSSL to the Simulator device and gave permissions/enabled it. When I start the Application on my device, I’m just not getting any response. There is no traffic visible in the terminal. Opening

localhost:9999/__admin/

in Safari of the device works fine and I can see traffic printer to terminal. I would really appreciate anyones help 🙏 I’ve spend the whole day trying to figure this out 😐

Are you trying to get the iPhone simulator to use forward proxying as a way of integrating with your mock API?

Yeah, I did that, but that does not seem to help.

You may have trusted WireMock’s HTTPS certificate rather than the CA cert is uses to sign generated certs when proxying.

via. the http://localhost:9999/__admin/certs/wiremock-ca.crt, right?

Might be worth dropping the one you created, at least from the WireMock startup parameters. I don’t think you need it, and although it shouldn’t interfere with proxying, you never know…

ok, let me try that

In terms of WireMock startup, I suggest only these parameters:

--port 9999 --verbose --enable-browser-proxying --trust-all-proxy-targets

Done, I downloaded the certificate again and approved it:

That doesn’t prove much unfortunately. If you have Postman installed you could try setting up forward proxying and testing from this.

ok, but then I would need to enable https, right?

No, counterintuitively

I received this error:

Network failure trying to make a proxied request from WireMock to {some-url}
Connect to <http://127.0.0.1:2424> [/127.0.0.1] failed: Connection refused

Looks like your proxy settings are still pointing at 2424

Ahh yes, I fixed it 🙂

No, if you’ve got forward proxying set up correctly

Omg… 🫠 so my problem the whole time was because I was using HTTPS setting!

You’re not alone with that. Trips everyone up!

Ahh, I can’t believe it 😄 Thank you very much for your time, Tom! 🙇 This is a life saving 🍻

No worries 👍

I added

--record-mappings

to my command hoping that I could record a session with an app. I actually noticed that while using the app, the endpoints are not being forwarded, because they are not recorded 🤔 I’m getting records only when using Safari and hitting the endpoints directly to

localhost:9999/{somepath}

.

--record-mappings

is the old way and doesn’t really work with forward proxying. Instead I suggest you use the newer snapshot recording approach - let some traffic flow through first, then snapshot afterwards like this:

curl -v <http://localhost:9999/__admin/recordings/snapshot> -d '{
    "captureHeaders": {
        "Host" : {
          "caseInsensitive" : true
        }
    }
}'

Hmm… something’s not right. I used the app for some time and when I executed the

curl

, there are only few records created with url as

SectigoRSADomainValidationSecureServerCA.crt

🤔

That’s very weird. Might be worth resetting WireMock, generating some traffic, then hitting

/__admin/requests

to see what’s there

Yeah, now I can confirm that the App network is not being forwarded. I also restarted the server and removed

--record-mappings

.

So there’s nothing in the request log?

no, not until I run the endpoint

localhost:9999/{path}

via. Safari

This isn’t required. You only need a proxy config like this for reverse proxying (where you’ve changed the endpoint config in your app). When forward proxying the destination is embedded in the request.

no, not this time. It works normally

If there are no requests in WireMock’s log and the app works OK that suggests that it’s not proxying through WireMock at all

Exactly, though Safari on the device works

That’s because you’re going directly with Safari

Is there anything else i need to setup?

Not from what you’ve told me

I did set it up in the meantime

Set up Postman Proxy like this:

Have you deleted all your proxy stubs?

only this one:

{
  "request": {
    "method": "GET",
    "urlPattern": "/api/v2/.*"
  },
  "response": {
    "proxyBaseUrl": "<https://myendpoint.net>"
  }
}

If you have any others, delete them too

Now i get:

No response could be served as there are no stub mappings in this WireMock instance.

Did you set up Postman to proxy like in my screenshot?

yes

Try doing

GET

<https://api.github.com/users>

in Postman

OK, that’s progress

yeah, now it works in Postman

OK, so you’ve got WireMock set up correctly. Now you just have to get your iOS emulator to proxy in the same way as Postman

I think I finally solved it

Ah, that’ll be it

Super awesome! It finally works 🙇 thank you soo much!!!

No probs

Hi again, Tom 👋 I’m trying to connect the proxy on Browserstack’s device to my local machine via. the local tunnel. I see it with 2 options: • Force Browserstack’s network to run over my local network via. the tunnel, while my network is set to run via. proxy on my local machine. If I set this up, I’m unable to start the execution because because it can not connect to Browserstack. • Force Browserstack to run via Proxy, where I determine my local IP + PORT. _In this case I’m getting this error: “[CONN_FAIL:4004] Looks like you have SSL inspection enabled. You can either bypass *.browserstack.com or disable SSL inspection entirely for BrowserStack local to connect.”_ Which option would be preferable in your opinion? Is there a way to exclude the SSL inspection for browserstack endpoints?

It’s a long while since I’ve worked with Browserstack and I don’t think I ever tried it with MITM proxying so I’m probably not the best person to ask. I’m guessing the bypass suggestion didn’t help?

Thanks for your feedback. I managed to make the connection to the proxy from the device on Browserstack, but now I’m struggling because the proxy changes the header when forwarding to our server, especially user-agent. What is the most efficient way to avoid this? 🤔 … my goal is to keep the user-agent in the header and pass the same value to our server.