Hi, we have a vps server we have recently setup that we plan on using for hosting configuration files for our apps. However when we use network.request to ping a file on our server we get the error “Failure cracking URL - http://api.intoitgames.com/Ads/1.0/configure.php?appID=super-stickman”. This URL has been accessible from mobile, desktop, and all other devices we have tested. Perhaps this has to do with some of our DNS changes? Can we get some help about what could be causing this error?
In fact, trying trying to request ANYTHING on our domain “intoitgames.com” gives the same error.
Another followup: Using a direct ip works just fine.
Example: http://173.224.218.205/API/Ads/1.0/configure.php?appID=super-stickman does not give any errors and works just fine.
It has actually just gone offline but it was fine before…I’ll update once its back online
Edit: Back online but still having the same old “Failure cracking URL” error
Ok WOW, I needed to put http:// in front of the URL. What a classic programmer mistake…
Hmmm, I am glad you caught that one but I wish these calls had a standard approach… I was just reading about network.setStatusListener() not liking it if you put in a http:// in front of the URL… So we must now learn and remember which network calls like the http:// and which ones don’t… Not good. I hope CL can take the steps to make it consistent.
In fact, trying trying to request ANYTHING on our domain “intoitgames.com” gives the same error.
Another followup: Using a direct ip works just fine.
Example: http://173.224.218.205/API/Ads/1.0/configure.php?appID=super-stickman does not give any errors and works just fine.
It has actually just gone offline but it was fine before…I’ll update once its back online
Edit: Back online but still having the same old “Failure cracking URL” error
Ok WOW, I needed to put http:// in front of the URL. What a classic programmer mistake…
Hmmm, I am glad you caught that one but I wish these calls had a standard approach… I was just reading about network.setStatusListener() not liking it if you put in a http:// in front of the URL… So we must now learn and remember which network calls like the http:// and which ones don’t… Not good. I hope CL can take the steps to make it consistent.