feat: revamped error section #4477
Conversation
revamped error section with actionable points and additional solutions from devrel
|
Your Platform.sh environment has successfully deployed. 🚀 See the changed pages: Platform.sh docs |
Kemi-Elizabeth
added
the
newsletter
|
|
||
| #### 1. Your app is listening at the wrong place | ||
| - **Solution**: Check your app's [upstream properties](/create-apps/app-reference/single-runtime-image.md#upstream). | ||
| - If your app is listening at a specific port, verify that it’s using the [`PORT` environment variable](/development/variables/use-variables.md#use-provided-variables) and ensure that it is listening at the correct port. |
There was a problem hiding this comment.
Shall we add a bullet here for apps listening to a socket?
| #### 2. Configuration issues in `.upsun/config.yaml` | ||
| - **Solution**: Review your `.upsun/config.yaml` configuration. | ||
| - Look for any errors that might prevent a process from starting or cause issues with requests being forwarded properly. | ||
| - Check the `web.commands.start` entry or your `passthru` configuration for any misconfigurations. |
There was a problem hiding this comment.
I would propose to point our customers to the logs of their apps in order to understand what's going wrong here as well.
Indeed, one of the possible issues here is that they haven't configured their web.commands.start correctly, but identifying potential typos or what's really going south is only possible when they look into their logs.
| #### 5. PHP process crashing due to segmentation fault | ||
| If your PHP process crashes due to a segmentation fault, you may encounter a message like the warning error detailed below. This indicates that either a PHP extension is causing the segmentation fault or there’s an issue in your PHP app code. | ||
|
|
||
| ```text {location="/var/log/app.log"} | ||
| WARNING: [pool web] child 112 exited on signal 11 (SIGSEGV) after 7.405936 seconds from start | ||
| ``` | ||
| - **Solution**: Review recent changes made to your app to identify potential causes. | ||
| - Consider using a debugging tool such as [Xdebug](/languages/php/xdebug.md) to help with quicker troubleshooting and identify the root cause of the crash. |
There was a problem hiding this comment.
Is this something we've identified commonly in our customers? If yes, then that's definitely the place for this to be.
My PHP experience is limited, but I wouldn't consider this a common case.
Revamped error section with actionable points and additional solutions from devrel
Why
Closes #4476
What's changed
I've revamped this page so that we have actionable points and more solutions for customers who may be redirected here from an error 502 page.
Where are changes
https://docs.upsun.com/development/troubleshoot.html#http-responses-502-bad-gateway-or-503-service-unavailable
Updates are for:
sites/platformtemplates)sites/upsuntemplates)