-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant get PADListener to capture #80
Comments
PAD fetches data from GungHo's servers when you hit START on the title screen. |
Yes I surely did, sorry for mis-explanation in the first post. |
So I did try some other stuff to capture my data but still cant do it. |
Using the Auto Iptables mode, the Listener should not have any impact on any other app. Using the Proxy Mode, all HTTP and HTTPS request go through the proxy. Only request sent to GungHo's servers are processed, but all request still go through the proxy. HTTP requests should not be impacted. When your browser sends a request to https://foo.bar, the proxy answers with a generated HTTPS certificate that does not match foo.bar. Any properly coded app should refuse this certificate as it's detected as a Man-in-the-middle attack. To investigate your capture issue : can you check in PADListener's settings > Listener > Target servers if your region is selected ? |
Thanks for the explanation. I could not try Auto Iptables mode since my device is not rooted by the way. Target servers are all set in the settings. I tried to set only NA version, with no success. I also tried to set a custom server name (that includes "padsv" insted of "pad" as you mentionned in some other post). No success either. As said earlier, I installed PAD 7.3.0 via the .apk package since it is not available here in France. Title screen says my PAD is NA version, may the irregular installation create my issue ? |
Nope. I'm in France too and had to use a VPN to install the NA version. I've tested the JP and KO versions installed from APK files and everything works. You can check if you manage to capture data with SandroProxy.
If the capture works, you should see a few calls to https://api-na-adr.padsv.gungho.jp//api.php. If that works, the capture with the core proxy from SandroProxy works. PADListener is based on this core, so it should also capture correctly (when done, remember to stop SandroProxy and disable your Wifi proxy ;p) |
SandroProxy starts correctly, listening to 127.0.0.1:8008. SandroProxy says "no data" in the HTTP tab. Looks like nothing is captured at all. |
Just to be sure, the proxy settings are :
You might need to hit the refresh button in the HTTP tab to show the captured request. Without root and special configuration, SandroProxy should capture everything. |
My proxy settings look correct. But SandroProxy does not capture anything : no PAD launch, no browser traffic, even though I hit the refresh button. Also, that difference you mention between http and https request, I dont see it. Any site I try to connect to, the browser says : Unable to connect to proxy server. |
The scary caps error means some proxy settings are wrong. What kind of Wifi are you using ? I mean, is it your home Wifi, or a school / work Wifi ? Stop SandroProxy and PADListener. Set your Wifi proxy to None. Is internet still working (in Chrome for example) ? Set it to Proxy Auto-Config if you can (I have the option in 5.0 but not 4.4). How about now ? |
Well, 127.0.0.1 looks good ! PADListener captured my data, nice ! Afterwards, I have to unset it to allow sync with PADHerder. So, in my case, this is not as automatic as one wish, but it works. Thanks for the precious help and time you gave me. |
So 127.0.0.1 works and localhost doesn't ? Weird ! Glad you could finally sync ;p |
That's right, 127.0.0.1 is ok, localhost is not. |
Hello, I cant get PADListener to capture data at PAD launch, details :
I used both manual and auto wifi mode, I see the internet connection turn off and on and check that my proxy is correctly set : localhost, port 8008. Then I launch PAD (manual capture) or autolanch (auto capture) and wait at the title screen, but the capture does not start.
Other facts :
Any help will be grandly appreciated.
The text was updated successfully, but these errors were encountered: