2
0
Here's my problem: I have a Java web application that uses Stormpath API for user management. The communication with this API is through HTTP.
Out of nowhere my API call hanged and returned after 3 connection attempts with 503 status code. All of this are happening from my laptop with Ubuntu 16 on it.
So I've tried to PING the address by name or direct IP - both calls hanged. I've switch from WIFI connection to a wired one, one the same network, and still nothing.
Basically, I can't event access this address https://api.stormpath.com/ from my laptop. I can access https://stormpath.com/ though. I've tried from my phone and everything works just fine.
I want to mention that I'm using a token in the HTTPS requests, so is a colleague of mine, token generated from the same account - but this is the way it's suppose to work.
I can't remember doing something special to mess with some settings from my system config. As I said, it happened out of nowhere.
I've also talk with their support and changed the password(from mobile) but nothing changed.
I'm a novice in Ubuntu and networking so I'm asking you guys what could I try to fix this. If other details are required, please just leave a comment and I'll add them.
Thanks in advance!
PS: I hope it's the right place to ask this
1Did you try to disable your antivirus and firewall(s) ? – harrymc – 2017-03-26T12:28:43.310
1Maybe you get the wrong IP? Try DNS resolution (dig) and ping from a different machine on a different network (your smartphone from your carrier's connection) and compare the results. – simlev – 2017-03-26T14:36:03.707
1@harrymc I've disabled the firewall and the problem persisted. I don't have an antivirus program – Bogdan Mihai – 2017-03-26T15:25:41.020
1@simlev Dig-ing the DNS gave me "status: refused". From another machine it works perfectly - I will test with dig also. The problem was indeed the wrong IP what was mapped in hosts file. Removing the line with ip-dns helped me fix the problem. Honestly I don't know why I still can't ping the new IP but it works from browser. – Bogdan Mihai – 2017-03-26T15:30:02.840
1This is most probably not a DNS issue - indeed it's more likely an issue on the server side. Can you detail your network - eg are you using static IP addresses, is your netmask the same throughout, are client and server on same network segment. Have you done any packet dumps to see packets leaving/entering the client and/or server? Does the client have connectivity to other systems? Are you running any VPNs? – davidgo – 2017-03-26T19:37:47.610