Android application Lose internet connection once connect to Fiddler - https

I have a strange situation using Fiddler to capture the HTTP/HTTPs traffic from an android application, in general, fiddler works fine, I got everything from any other app as chrome, and more, but this specific app not connect to the internet or lose the connection once I connect to fiddler Proxy server, I don't know why this happened also I don't know if someone has an explanation or got the same issue before, because fiddler in general working, but only this app, once I back to the normal connection and stop connecting to the Fiddler proxy server the connection back to this app.
so if someone has a solution or there is a similar problem as I did not find such kind of problem when I searched it will help.
I use the normal way to capture the data from fiddler by open Fiddler proxy server and connect my Android phone to my PC IP and the port of fiddler app, I was thinking about it and I'm not sure maybe this happened because the app did not trust the root certificate of the https of fiddler or the app protect from sniffing by disconnect the connection once the Android phone use a proxy, I am new using fiddler so I'm not sure how it's going.
I read about also certificate pinning, but I think this is not the case as if it happened it normally connect and show Tunnel or something like this as I understand in the fiddler screen, but not lose the connection.
Thanks in advance.

Related

Using a third party Windows Application, Fiddler Classic's proxy changes, "click to reenable" capturing. Are any requests getting by unnoticed?

I recently began using Fiddler to capture requests from a windows application that I believe is sending malevolent requests. This said application actually has a browser extension for both Chrome and Microsoft Edge. However, only on the Windows Application does Fiddler gives me a yellow pop up: "The System proxy was changed, click to reenable Fiddler capture." This happens specifically when the App begins running and the user logs in.
An example is seen on here: Fiddler not capturing traffic. Proxy settings keep getting changed
I also notice in my windows machine network proxy settings that the App automatically checks "use a setup script" and provides a link to their proxy script.
On my machine, I clearly still am seeing many requests after clicking the yellow pop up. I also am still seeing many requests called by this App. However, I am worried that there could be an instance where the App is clearly able to send requests that it can hide from Fiddler, and only let Fiddler see the requests it wants it to.
The reason I believe this is that Fiddler is a proxy, and the App is yet another proxy. Fiddler doesn't know that it's intercepting a network's traffic through the App's proxy. So Fiddler wouldn't know if it's not hearing everything, and neither would I.
Is this a realistic fear?
If so, where can I find some more information on what is happening, and how to bypass it?
If not, that's all I need to know.

Can't connect to certain databases/apps with https proxy

I have recently been sharing the connection of my mobile device to my laptop, when i'm out and about, through the use of an app called netshare. It provides a https proxy I believe through which it acts as a network repeater?(not sure about this part). I can access webpages and such quite easily. However, I have realised that I cannot connect to some apps. For example, I cannot use spotify. Installing some other apps like games etc also prove to fail. I have done a bit of research and found that apparently I could only surf the web with a https proxy. However, I found this to be unambiguous. Does this mean that I can only make https requests? Or is this because of https using TCP over UDP? What are the limitations and what can I do to possibly solve it?
Thanks

Fiddler on Windows 10: All Captured HTTPS Traffic Dies

I've had a problem with Fiddler ever since my machine was upgraded from Windows 7 to Windows 10. If I configure Fiddler to decrypt HTTPS traffic, any traffic it captures is, for lack of a better word, killed.
For example, if I visit the (HTTPS) page that documents configuring HTTPS decryption, without Fiddler, I see it as normal:
However, once I begin capturing traffic, and reload the page, I get this:
All of the responses feature this same exception message:
I only use Fiddler occasionally, when I need to see what's going into and out of my apps. I could've sworn I was able to do this with HTTPS before migrating to Windows 10. I'm not sure what changed, but Fiddler has become fairly useless to me now that all the traffic it captures fails. Any help would be appreciated.

how to work with laravel-chat app in pusher.js if I have no internet connection

Lately, my internet connection is going sour and sometimes I get no internet, can I work with like resuming this chat-feature, will I be able to write one without an internet connection
https://blog.pusher.com/how-to-build-a-laravel-chat-app-with-pusher/
You can use https://www.npmjs.com/package/laravel-echo-server which is a self-hosted pusher compatible server.

socket.io not connecting to mobile browser

I wanna create a connection between my mobile Safari and nodejs + socket.io on my Macbook.
When i call localhost:8080 from my laptop, everything works fine. The console says that the client is connected and my little website is displayed.
When i call it over my mobile browser with 10.0.1.5:8080, the website is displayed as well, but my socket.io don't identify the mobile browser (iPhone) as client and nothing happens on the console board.
Does anybody where the problem is?
I found this post on SO, probably can help you out. why does my nodejs socket.io app not work on ios6
Localhost is local to the machine. You're IP should use a ip address
or domain name:
something like: io.connect('192.168.1.110'); or
io.connect('test.myapp.com');
WebSockets do not work over cellular network as they are not forwarded by the http proxy.
A possible workaround it to set the WebSocket server port to 443 (https) which forwards everything (as https is encrypted the proxy has to forward it in order to support https).
To see a real world example which solves this problem this way checkout nearby.
Remember this requires using two http servers:
Serving you mobile application (on port 80)
Serving the web sockets on (port 443)
Else you always have to use the specific ports in your urls which is mostly not preferred in production.

Resources