cURL Requests Not Working When Pushed to Live Server

Two things come to mind: There could be a restriction on their API based on an IP address, so that when you access the API from a different server it won't let you connect. Your Ravelry dashboard or admin page could help you out on that one.

The second thing is to dump result without json_decode wrapped around the curl_exec. Because now your dumping the result of the json decoded result which, if the result isn't json, won't give you much to go on.

Thank you for the response! I'm currently at work, so not able to try that out right away, but I will see what I come up with when I dump the result without the json_decode(). I might have a moment over my lunch to give it a try.

I'm also trying to nail down what the exact issue is, whether its the communicating with the Ravelry API or an issue with cURL, I'm not too sure. I'm not very comfortable working with Guzzle, but it may be worth working with if the issue is cURL. If anything Guzzle would probably be much easier to debug.

Thanks again for the input, any and all is appreciated!

Are you caching your config for production (always good to do) using artisan config:cache? As per the docs, you shouldn't be using env() outside of config files. You should be calling config() to get the values, not env().

It's just good practice, whether you're caching the config or not, to only use env() inside of config files. That way, if you one day choose to cache the config to get the extra speed performance, everything will just work. Once the config is cached, laravel reads from the cache file and ignores env() calls. I suspect that's what's happening here.

Just create a /config/ravelry_api.php file:

return [
    'ACCESS_KEY' =>  env('RAVELRY_API_ACCESS_KEY'),
    'PERSONAL_KEY' => env('RAVELRY_API_PERSONAL_KEY'),
    'URL' => env('RAVELRY_API_URL')
];

Then instead of:

$login = env('RAVELRY_API_ACCESS_KEY');
$password = env('RAVELRY_API_PERSONAL_KEY');
$url = 'https://api.ravelry.com/patterns/search.json?designer=Handiworks+LTD';

use

$login = config('ravelry_api.ACCESS_KEY');
$password = config('ravelry_api.PERSONAL_KEY');
$url = config('ravelry_api.URL');
// ...

I also added the URL to the config as it seems appropriate, so you'd need to add RAVELRY_API_URL to your env file...

Thank you for the suggestion! I'm still pretty new with Laravel, so there's a fair bit I don't know as far as best practices go, especially involving the finer aspects of the framework. I did move those items over to a new config file and once again that page works fine in a local environment, but still has issues on the production server...

I also dd'd that curl_exec($ch) on both my local and production environment. On my local environment it spits out the json file as expected, but in production all I get is false, which probably isn't good.

For now, I'd hardcode the values instead of using env() just to make sure that isn't the issue.

Also try running artisan config:clear on your production box after you make changes

Also did artisan config:clear and that didn't seem to change matters. I'm just so at a loss as to what the issue is...

I just checked the debug logs on the Ravelry API, and the calls from my local environment are being received, but the ones from my production box are not, so one way or another it's a problem between the connection of the two, which could be any number of things.

I event attempted a curl request using the same parameters from the terminal on the server, and that worked fine and produced json.