u/grantholle

We've tinkered with Laravel Cloud in the past for various environments. Currently we're using it for dev and preview environments, which is nice and generally works well.

A couple days ago I noticed that deployments were failing due to a cache issue.

>php_network_getaddresses: getaddrinfo for tls://cache-[uuid].us-east-1.caches.laravel.cloud failed: Name or service not known

After enabling the connection to be public, you get SSL_connect failed: certificate verify failed errors. It appears the certificate didn't get renewed properly or something. Creating a new cache for the org still has the same issue.

It's been over 24 hours since contacting support, no acknowledgement that they're aware of the issue or currently working on it. A chat widget for such a critical issue seems like a joke. The app is completely down and deployments don't work. If this was production, we would be at days of downtime.

Simultaneously, our org gets emails all the time from the Cloud team trying to get us to migrate over to Cloud and offering discounts. This experience has perhaps put a permanent bad taste in my mouth for Cloud.

Do they not having the monitoring capabilities for their own resources when something goes wrong like this? I understand there's no way to monitor individual project deployments since typically those are userland issues. But this is an issue with their infrastructure. For days.

The product is shiny and well-crafted, but there's still much work to be done to gain my trust back with Cloud.

Update since writing this: Support finally acknowledged they're aware after sending another chat message.

Final update:

The issue is resolved by an environment flag, REDIS_SCHEME=tls fixes it. Frustrating that's all it took, but since the Redis variables are injected automatically I blame myself partially for not looking closer.