Login to start a new topic
Answered

iOS configuration issue

I have just acquired the Fiddler Everywhere app and I am in the process of configuring it for my Mac.

 

I have been following the documentation guide on your website here - https://docs.telerik.com/fiddler-everywhere/traffic/configure-ios

 

I am having issues with the iOS set up steps, specifically after configuring the server and proxy settings on my iPhone.  Attempting to download the certificate from http://ipv4.fiddler:8866 does not work as my iPhone loses connection to the internet after the settings change.

 

My investigations online shows that other people are having this exact problem.  Could you please share a solution?


Best Answer

Reposting the suggestion provided in our private ticket:



The inability to open http://ipv4.fiddler:8866 indicates that your iPhone does not have access to the Fiddler proxy. Because it can't reach the proxy as a consequence it will lose Internet connectivity (because at that point your iOS WiFi is set to use the Fiddler Everywhere host IP as a proxy server). Before continuing our investigation can we retry and verify the following steps:

1. On the host machine, start the Fiddler Everywhere, go to Settings > Connections and ensure that the Allow remote computers to connect option is checked.

2. Go to Settings > HTTPS > Advanced and fully reset your Fiddler Root CA by pressing the Reset root certificate button. After the successful reset operation, ensure that the Capture HTTPS traffic option is checked.

3. WIth Fiddler Everywhere started, ensure that the Live Traffic capturing is turned on.

4. Connect your iOS device to the same network as the Fiddler host. Using the iOS device and the Fiddler Everywhere host from different networks is impossible.


5. Configure the WiFi network on the iOS device to use the Fiddler Everywhere proxy host IP (the local IP of the host in the network, usually something like 192.168.xxx.xxx) and Port (by default 8866).


6. At this point, you should be able to capture non-secure traffic like http://example.com - try to load that page in your mobile browser and see if it is being successfully captured in Fiddler Everywhere. Suppose you cannot open any site at that point on your mobile browser that indicates that the iOS device cannot access the Fiddler host at all. This is most likely caused by software (GPO policies, third-paprty security tools, corporate tools, VPNs, etc.) or hardware restrictions (check for restrictions applied in routers, extenders, etc.) in your network setup. Contact your network administrator or try to switch both host and mobile device to a different network.


7. In case you can capture non-secure traffic (previous step), but you are unable to open HTTPS traffic (secure), then that indicates that the issue is that your mobile device needs to reinstall and fully trust the Fiddler root trust certificate. Go through the steps in this tutorial and note that the 9th step is crucial for the certificate installation. If, for some reason, you are not able to access the Fiddler loopback address (step 6 in the tutorial), then you could export the certificate manually (Export root certificate option) and send it to your mobile device via third-party services (like email).



Answer

Reposting the suggestion provided in our private ticket:



The inability to open http://ipv4.fiddler:8866 indicates that your iPhone does not have access to the Fiddler proxy. Because it can't reach the proxy as a consequence it will lose Internet connectivity (because at that point your iOS WiFi is set to use the Fiddler Everywhere host IP as a proxy server). Before continuing our investigation can we retry and verify the following steps:

1. On the host machine, start the Fiddler Everywhere, go to Settings > Connections and ensure that the Allow remote computers to connect option is checked.

2. Go to Settings > HTTPS > Advanced and fully reset your Fiddler Root CA by pressing the Reset root certificate button. After the successful reset operation, ensure that the Capture HTTPS traffic option is checked.

3. WIth Fiddler Everywhere started, ensure that the Live Traffic capturing is turned on.

4. Connect your iOS device to the same network as the Fiddler host. Using the iOS device and the Fiddler Everywhere host from different networks is impossible.


5. Configure the WiFi network on the iOS device to use the Fiddler Everywhere proxy host IP (the local IP of the host in the network, usually something like 192.168.xxx.xxx) and Port (by default 8866).


6. At this point, you should be able to capture non-secure traffic like http://example.com - try to load that page in your mobile browser and see if it is being successfully captured in Fiddler Everywhere. Suppose you cannot open any site at that point on your mobile browser that indicates that the iOS device cannot access the Fiddler host at all. This is most likely caused by software (GPO policies, third-paprty security tools, corporate tools, VPNs, etc.) or hardware restrictions (check for restrictions applied in routers, extenders, etc.) in your network setup. Contact your network administrator or try to switch both host and mobile device to a different network.


7. In case you can capture non-secure traffic (previous step), but you are unable to open HTTPS traffic (secure), then that indicates that the issue is that your mobile device needs to reinstall and fully trust the Fiddler root trust certificate. Go through the steps in this tutorial and note that the 9th step is crucial for the certificate installation. If, for some reason, you are not able to access the Fiddler loopback address (step 6 in the tutorial), then you could export the certificate manually (Export root certificate option) and send it to your mobile device via third-party services (like email).



1 person likes this

Hi Nick,


Thank you for the detailed feedback.  This was very useful.  I believe reseting the certificate helped with my process.  I was able to connect successfully and download the certificate to my phone.  I will be retrying the process again on my work's machine.


Thanks for your help.

Login to start a new topic