Fixing the Code 502 Message Error during function invocation error
Issue description
You used to run your application in a CRI-compatible environment within a container on a VM or a physical server. After you migrated the application to Serverless Containers, you get the 502 Message Error during function invocation error when invoking it.
Solution
You may get error 502 when the code running in the container makes an HTTP request that terminates with an error.
Check your container operating log. It may include the full error text mentioning the request in question. If you are unable to find any useful data in your container log, enable detailed logging for your containerized application.
Alert
When calling a container over HTTPS, certain HTTP headers in the request and response are changed (see this article for details).
You need to consider these changes when migrating your application to the Serverless Containers environment.
If the issue persists
If the above actions did not help, create a support ticket. Provide the following information in your ticket:
- Container ID.
- Date and time of your container call that terminated with an error.
- Description of the container call: whether the container is called from the third-party application code over the Serverless Containers API or directly, from the management console or YC CLI.
- Full text of the error from the Serverless Containers container log.