There’s one thing I am not 100% sure about: Does port 2443 have to be mapped to the internal IP in our local firewall? It wouldn’t make much sense to me, but I still like to check all possible reasons for this problem. More of a nuisance really, ~iworx/cron/license.pex --sync usually fixes this issue.
But this time it fails with the following error on one machine:
root@tarkin ~]# ~iworx/cron/license.pex --sync
XMLRPC error encountered
Code: 8
Error: CURL error: Could not resolve host: license.interworx.info; Unknown error
I can ping license.interworx.info or license.interworx.com and they both resolve fine to 207.32.181.150. So what could be the issue here? The other machine with exactly the same codebase wors fine…
Thanks
P.S. John, I edited the title, can you make that reflect in the thread title? Cheers, Mate
Curl version is 7.28.0 on both machines. Both fail at
[root@thrawn ~]# curl licence.interworx.inf
curl: (6) Could not resolve host: licence.interworx.inf; Name or service not known
But one fails at ~iworx/cron/license.pex --sync, the other doesn’t
Strange…
Regarding title, I meant the thread title “Must port 2443 be mapped in local Firewall?”, it shoud be “CURL error: Could not resolve host: license.interworx.info”, as this thread is about that more than the port mapping (where i share your thoughts).
ha ha, you’re right about .inf
And there’s even one more typpo in there: “licenCe”
But my whole issue was a wild mix of typos, DNS loops and stupidity. I recently changed our whole network topology and made one tiny mistake on the DNS server, so it would resolve but take some time for that. So I guess nslookup worked but Curl ran into a timeout.
So you helped with a keen eye and Nathan indirectly pointed me to DNS by adding the Gooogle DNS to resolv.conf on another server, which made me think…