Instagram knows my real ip?

dllll

Registered Member
Joined
Jun 20, 2014
Messages
89
Reaction score
43
Im using a dedicated proxy and i just visited Instagram and they blocked me from their site and i got this message that displays my real IP address, wtf?
Im pretty sure this never happened to me before ,so is it Instagram or the proxy i should blame?

CLIENT_IPADDR: 101.21.86.152
SERVER_HOSTNAME: sppnsh.nashville.tn.us
URL: http://instagram.com/
REQUEST_METHOD: GET
PROTOCOL: http
PORT: 80
ERROR_CODE: ERR_ACCESS_DENIED
ERROR_DESCRIPTION: Access Denied. Access control configuration prevents your request from being allowed at this time. Please contact your service provider if you feel this is incorrect.
 
Your proxy definitely leaked and since you are from China(I'd recommend removing your real IP from the initial post) you see that error. I wouldn't be so sure if the proxy is the one to blame. It could be you not knowing how to use it the right way.
 
I am not from China im from the US, obviously i put a random ip address in my original post im not an idiot.
 
I am not from China im from the US, obviously i put a random ip address in my original post im not an idiot.

Ha ha nice lol.. . and now days Instagram very bad most of accounts get banned with in sec. .
 
If you use wifi or a mobile they will get your real ip.
Did you disable WebRTC in your browser???
 
Use a different private proxy provider and try to get a random port instead of 80.
 
If you use wifi or a mobile they will get your real ip.
Did you disable WebRTC in your browser???

Right there, WebRTC is the problem with your real IP leak in VPNs to some extend this may be the problem with the proxies as well.

I dont see how the usage of WiFi can cause this kind of problem, since this is just a technology for connection only to the internal network>gateway> and behind that your public IP comes to play, so I highly doubt WiFi can be the problem here.

About mobile the topic is broad, mb some mobile OSs can't really handle the proper support of proxy usage, but after all I think WebRTC could cause this problem if you use desktop or mobile browser, if you use bot.. it depend on how the bot is build I think.
 
did you fix it somehow? mine works fine on instagram.com but I have the same problem on mail.com
 
Back
Top