This page provides troubleshooting advice for errors and issues that you might encounter when using Akka Serverless. If come across an issue that is not listed here, let us know using any of the below options.
Check out Frequently Asked Questions.
Reach out to our support team via the Contact Support form in the Akka Serverless Console.
Email us at email@example.com to provide feedback or get help.
Suggest ideas in our Idea Portal in the Akka Serverless Console.
Check out the latest discussions about Akka Serverless at https://discuss.lightbend.com/c/akka-serverless/40 .
We make frequent changes and updates to the Akka Serverless CLI to give you a great experience. Make sure that you’re using at least the latest supported version (0.0.38), and preferably the latest version.
You can check the version of the Akka Serverless CLI you have by running
When you deploy a service to Akka Serverless, and it cannot pull the service image, the status will display
waiting - imagePullBackoff, as shown in the example below.
There are two primary reasons as to why this error might occur. Review each case below to see if it fits your particular scenario.
It’s probable that the error is happening because there is a bad value for the Docker image URL used when creating the service. For example, say the URL used is
An invalid value anywhere within the Name or URL triggers the
ImagePullBackoff error. In this case, the tag used,
0.0.81818, does not exist.
To resolve this issue, review the URL for:
The second most likely scenario for this status is when a developer specifies an image in a private repository, but fails to provide Docker credentials, or supplies incorrect Docker credentials. If this is the issue the status will appear as shown in the example below. Note that
unauthorized will be appended at the end of the status.
In this case, the provided image name
gcr.io/some-private-repository/akkaserverless-application:1.0.0 is completely valid. However, it requires container registry credentials to be setup.
The same status message will appear within the System Lifecycle events window.
Options to resolve this issue include:
Use a public repository
Supply your credentials, and validate that they are correct.
It is possible that a user created function may fail, or cause a service to fail. Any user function errors that prevent the proxy from starting (such as, mis-configured services), will be reported through to the logs with an error message.
These error messages include:
An error code
A detailed description of the error
The protobuf source location, if appropriate
To resolve this type of issue:
Review the logs
Note any key information
Peruse the relevant (linked) documentation
Debug the user code locally
This should not happen. Lightbend does not expect any broken proxy releases to be deployed. However, if a service doesn’t start, and there are no errors logged which indicate a problem with a user function, then a proxy failure is a remote possibility.
Steps to resolve:
If you think that you are encountering a failing proxy, the only way to resolve the issue is to log into your Akka Serverless account and contact customer support.