| Error log | Possible cause | Resolution |
|---|
micro-gw: Error occurred while trying to connect with server. Is the server running at https://localhost:9443?
| The API Manager node (Publisher) is down when running the setup command in the Microgateway. | Verify the connectivity between the Microgateway and the API manager node. |
Micro-gw: ERROR [src:0.0.0] - Error in client response : {message:"Connection refused: localhost/127.0.0.1:8080", cause:null} | Connection to the backend is refused. | Check the connection to the backend. |
error [docker plugin]: Unable to build docker image: {"message":"invalid reference format: repository name must be lowercase"} | The name of the docker images should be in lower case. When building the project with docker annotations, the docker image name is retrieved from the API name and version. If the API name contains a capital letter, then the docker image n ame would reflect that, resuling in this error.
|
When building the API microgateway project, provide a simple letter name for the docker image in the deployment.toml file as shown below.
[docker]
[docker.dockerConfig]
enable = true
name = "hello_world"
|
ERROR [wso2/gateway:0.0.0] - Error occurred while reading the key validation response : {message:"Connection refused: localhost/127.0.0.1:9443", cause:null}
ERROR [wso2/gateway:0.0.0] - Error occurred while converting the authorized value from the key validation response to a
string value : {message:"'null' cannot be cast to 'string'", cause:null}
ERROR [wso2/gateway:0.0.0] - Error occurred while getting key validation information for the access token : {message:"call failed", cause:{message:"call failed", cause:{message:"'null' cannot be cast to 'string'", cause:null}, causes:[{message:"'null' cannot be cast to 'string'", cause:null}]}, causes:[{message:"call failed", cause:{message:"'null' cannot be cast to 'string'", cause:null}, causes:[{message:"'null' cannot be cast to 'string'", cause:null}]}]}
| The Microgateway could not connect to the Key Manager for OAuth2 key validation. | Check the connection between the Microgateway and the Key Manager. |
ERROR [wso2/gateway:0.0.0] - Error occurred while reading the key validation response : {message:"General SSLEngine problem/192.168.8.101:9443", cause:null}
ERROR [wso2/gateway:0.0.0] - Error occurred while converting the authorized value from the key validation response to a
string value : {message:"'null' cannot be cast to 'string'", cause:null} | SSL hostname verification has failed in the key validation call. | The localhost hostname is supported by default. You need to add the public certificate of the Key Manager to the Microgateway truststore. Also, make sure that you change the certificateAlias accordingly. |
ERROR [ballerina/http] - Error while validating JWT token : {message:"Invalid signature", cause:null} | JWT signature verification has failed. | Verify the following: - JWT signer’s public cert should be available in the Microgateway’s truststore.
- The correct Certificate Alias should be given in the
<MGW_HOME>/conf/micro-gw.conf file.
|
