Anyone else struggling with tricky Laravel troubleshooting issues lately?
0
hey guys, just launched a new feature in my Laravel app and we've been hitting some really weird, hard-to-debug issues. specificly, we're seeing problems with a third-party API callback that sometimes just doesn't process correctly, leading to data inconsistencies. it's not consistent, which makes it a nightmare to pin down.
sometimes, something like this pops up in the logs, but it's not always the same error or even in the same spot:
sometimes, something like this pops up in the logs, but it's not always the same error or even in the same spot:
[2024-03-15 14:22:01] local.ERROR: GuzzleHttp\Exception\ConnectException: cURL error 7: Failed to connect to api.thirdparty.com port 443: Connection refused (see https://curl.haxx.es/libcurl/c/libcurl-errors.html) at /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:200 {"exception":"[object] (GuzzleHttp\\Exception\\ConnectException(code: 0): cURL error 7: Failed to connect to api.thirdparty.com port 443: Connection refused (see https://curl.haxx.es/libcurl/c/libcurl-errors.html) at /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:200)"}it's really frustrating when the stack trace isn't super clear. what general strategies or tools do you all use for effective laravel debugging, especially for these more obscure errors that don't have a clear path? any specific packages or techniques for getting more insight into these intermittent issues? thanks in advance!0 Answers
No answers yet.
Be the first to provide a helpful answer!
Your Answer
You must Log In to post an answer and earn reputation.