Results 1 to 6 of 6
  1. #1
    Join Date
    Jun 2014
    Posts
    217
    Points
    3,880
    Level
    26

    CURL error: Could not resolve host: license.interworx.info

    Hi all,

    we have two test installations of Interworx servers running on our local network. But one or the other keep failing doing the licensing check.

    Naturally I have check all things listed here http://www.interworx.com/support/faq...license-error/ : The time is correct (via NTP), port 2443 is open, IP has not changed, licenses are ok and license.interworx.com resolves just fine. But still it keeps failing every now and then.

    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
    Last edited by mdeinhardt; 09-15-2017 at 06:39 AM.

  2. #2
    Join Date
    Apr 2012
    Posts
    2,150
    Points
    23,244
    Level
    66
    Hi Michael

    I hope your well

    Sorry, I do not believe it needs mapping to an IP address

    I think your issue maybe curl

    What version are you using Curl -v I think it Curl -V

    If not latest, I would think about updating it

    Prior to upgrade though, next time it happens, what do you get if you run Curl licence.interworx.info

    Aha, your error shows dns error sorry

    I might be tempted to add license.imterworx.info into host file, then see how it goes

    I hope that helps a little

    Many thanks

    John

  3. The Following User Says Thank You to d2d4j For This Useful Post:


  4. #3
    Join Date
    Apr 2012
    Posts
    2,150
    Points
    23,244
    Level
    66
    Hi Michael

    Many thanks, and sorry, just read your ps sorry

    Title looks ok from here so hope I have not missed anything sorry

    Many thanks

    John

  5. #4
    Join Date
    Jun 2014
    Posts
    217
    Points
    3,880
    Level
    26
    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).

    Cheers,

    Michael

  6. The Following User Says Thank You to mdeinhardt For This Useful Post:


  7. #5
    Join Date
    Apr 2012
    Posts
    2,150
    Points
    23,244
    Level
    66
    Hi Michael

    Many thanks, will do

    Just one point sorry, you have .inf and it should be .info unless your changing it

    I'll have to check on one of our servers

    Many thanks

    John

  8. The Following User Says Thank You to d2d4j For This Useful Post:


  9. #6
    Join Date
    Jun 2014
    Posts
    217
    Points
    3,880
    Level
    26
    Hi John,

    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...

    Thanks and have a great weekend.

    Michael

  10. The Following User Says Thank You to mdeinhardt For This Useful Post:


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •