Error Code Reference

Error Codes and Troubleshooting

Meshery and its components use a common framework (defined within MeshKit) to generate and document an event with a unique error code identifier as the combination of [component type]-[component name]-[event moniker]-[numeric code]. Each error code identifies the source component for the error and a standard set of information to describe the error and provide helpful details for troubleshooting the situation surrounding the specific error.

Error codes are combination of component type, component name, event moniker and numberic code

Error codes are a hyphenated collection of details that include:

Component Type (string): The type of the component that emits this error event; e.g. adapter
Component Name (string): The name of the component that emits this error event; e.g. ameshery-istio
Error Moniker (string): A semi-human readable short key used in descriptive reference to the specific event at-hand; e.g. ErrClosingDatabaseInstanceCode
Numberic Code (number): Unique number identifying a specific error as scoped by a specific component; e.g. a1000

The numeric portion of error codes are component-scoped. The numeric portion of error codes are allowed to overlap between Meshery components. The combination of the [component type]-[component name]-[event moniker]-[numeric code] is what makes a given error code globally unique.

Error Code Categories by Component

Component Type	Component Name
adapter	CILIUM
adapter	meshery-consul
adapter	meshery-istio
adapter	meshery-kuma
adapter	meshery-linkerd
component	meshery-server
component	meshery-server
library	meshery-adapter-library
library	meshkit
adapter	meshery-nginx-sm
adapter	nsm
adapter	meshery-osm
adapter	meshery-traefik-mesh

Top

Meshery Adapter for CILIUM

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrInstallCiliumCode-1000`	Error with Cilium operation	search forum

Long Description

Error occurred while installing Cilium mesh through Cilium

Probable Cause

Suggested Remediation

Probable Cause

The gzip might be corrupt

Suggested Remediation

Retry the operation

Error getting MeshSpecKey config from in-memory configuration

Probable Cause

Suggested Remediation

Reconnect the adaptor to the meshkit server

Probable Cause

Corrupted cilium binary Command might be invalid

Suggested Remediation

Error occurred while download Cilium binary from its github release

Probable Cause

Checkout https://docs.github.com/en/rest/reference/repos#releases for more details

Suggested Remediation

Probable Cause

Corrupted Cilium release binary Invalid installation location

Suggested Remediation

Error occurred while trying to install a sample application using manifests

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reconnect your adapter to Meshery Server to refresh the kubeclient

Error occurred while applying custom manifest to the cluster

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Upload the kubconfig in the Meshery Server and reconnect the adapter

Error occurred while applying manifest to create a namespace

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Upload the kubeconfig in the Meshery Server and reconnect the adapter

Probable Cause

Corrupted binary Invalid operation

Suggested Remediation

Check if the adaptor is executing a deprecated command

Probable Cause

Suggested Remediation

Cilium adapter received an invalid operation from the meshey server

Probable Cause

The operation is not supported by the adapter Invalid operation name

Suggested Remediation

Check if the operation name is valid and supported by the adapter

Probable Cause

Suggested Remediation

Kubernetes client is nil

Probable Cause

kubernetes client not initialized

Suggested Remediation

Reconnect the adaptor to Meshery server

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while prasing application component in the OAM request made

Probable Cause

Invalid OAM component passed in OAM request

Suggested Remediation

Check if your request has vaild OAM components

Error occurred while prasing component config in the OAM request made

Probable Cause

Invalid OAM config passed in OAM request

Suggested Remediation

Check if your request has vaild OAM config

Probable Cause

Latest version could not be found at the specified url

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Download might be corrupted.

Suggested Remediation

Please retry operation.

Probable Cause

Trying to access a namespace which is not available

Suggested Remediation

Verify presence of namespace. Confirm Meshery ServiceAccount permissions

Probable Cause

The gzip might be corrupt

Suggested Remediation

Please retry operation.

Probable Cause

File might be corrupt

Suggested Remediation

Please retry operation.

Probable Cause

Error occurred while download cilium tar from its release url

Suggested Remediation

Checkout https://github.com/cilium/cilium-cli/releases/download/\<release>/cilium-<platform>-<arch>.tar.gz for more details

Probable Cause

Latest version could not be found at the specified url

Suggested Remediation

Verify network connectivity. Ensure github.com is reachable. Try retrying the operation.

versions for cilium could not be fetched

Probable Cause

could not reach github.com/cilium/cilium/releases no versions could be fetched from cilium release page

Suggested Remediation

make sure adapter is reachable

Top

Meshery Adapter for meshery-consul

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrApplyOperationCode-1000`	Error applying operation	search forum

Long Description

Probable Cause

Suggested Remediation

Error occurred while parsing application component in the OAM request made by Meshery Server

Probable Cause

Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct

Suggested Remediation

Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, check if Meshery Server and adapters are referring to same component struct provided in MeshKit.

Error occurred while parsing configuration in the request made by Meshery Server

Probable Cause

Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct

Suggested Remediation

Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit

Probable Cause

Suggested Remediation

Probable Cause

Chart could be invalid

Suggested Remediation

Use helm verify and helm lint to verify chart path and validity

Error getting MeshSpecKey config from in-memory configuration

Probable Cause

Suggested Remediation

Probable Cause

API version or Kind passed is empty

Suggested Remediation

Make sure API version and Kind are not empty

Probable Cause

Could not marshall generated component to YAML

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Top

Meshery Adapter for meshery-istio

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrEmptyConfigCode-1000`	Config is empty	search forum

Long Description

Probable Cause

Suggested Remediation

Unable to get the latest release info from the GithubAPI

Probable Cause

Checkout https://docs.github.com/en/rest/reference/repos#releases for more info

Suggested Remediation

Probable Cause

Invalid release format

Suggested Remediation

Error occurred while installing istio mesh through istioctl

Probable Cause

Suggested Remediation

Probable Cause

File might be corrupt

Suggested Remediation

Probable Cause

/The gzip might be corrupt

Suggested Remediation

Error getting MeshSpecKey config from in-memory configuration

Probable Cause

Suggested Remediation

Probable Cause

Corrupted istioctl binary Command might be invalid

Suggested Remediation

Error occurred while trying to install a sample application using manifests

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reconnect your adapter to meshery server to refresh the kubeclient

Probable Cause

Suggested Remediation

Error occurred while trying to install a sample application using manifests

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reconnect your adapter to meshery server to refresh the kubeclient

Error occurred while applying custom manifest to the cluster

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Invalid profile passed

Suggested Remediation

Provide one of the profiles: "demo","minimal","default" profiles

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while parsing application component in the OAM request made by Meshery server

Probable Cause

Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct

Suggested Remediation

Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also check if Meshery Server and adapters are referring to same component struct provided in MeshKit.

Error occurred while parsing configuration in the request made by Meshery Server

Probable Cause

Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct

Suggested Remediation

Kubernetes client is nil

Probable Cause

kubernetes client not initialized

Suggested Remediation

Reconnect the adaptor to Meshery server

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Istio adapter received an invalid operation from the meshey server

Probable Cause

The operation is not supported by the adapter Invalid operation name

Suggested Remediation

Check if the operation name is valid and supported by the adapter

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Istio only supports Windows, Linux and Darwin

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

versions for istio could not be fetched

Probable Cause

could not reach github.com/istio/istio/releases no versions could be fetched from istio release page

Suggested Remediation

make sure adapter is reachable to github

Top

Meshery Adapter for meshery-kuma

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrGetLatestReleasesCode-1000`	unable to fetch release info	search forum

Long Description

Unable to get the latest release info from the GithubAPI

Probable Cause

Checkout https://docs.github.com/en/rest/reference/repos#releases for more info

Suggested Remediation

Probable Cause

Invalid release format

Suggested Remediation

Kuma adapter received an invalid operation from the meshey server

Probable Cause

The operation is not supported by the adapter Invalid operation name

Suggested Remediation

Check if the operation name is valid and supported by the adapter

Error occurred while installing kuma mesh through kumactl

Probable Cause

Suggested Remediation

Error getting MeshSpecKey config from in-memory configuration

Probable Cause

Suggested Remediation

Reconnect the adapter to the Meshery Server

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while trying to install a sample application using manifests

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reconnect your adapter to Meshery Server to refresh the kubeclient

Error occurred while downloadingkumactl and moving it to .meshery/bin]

Probable Cause

https://download.konghq.com/mesh-alpine/kuma-\<release>-<platform>-<arch>.tar.gz might be deprecated

Suggested Remediation

Error occurred while download kuma binary from its release url

Probable Cause

Checkout https://download.konghq.com/mesh-alpine/kuma-\<release>-<platform>-<arch>.tar.gz for more details

Suggested Remediation

Error occurred while installing kuma mesh through kumactl

Probable Cause

Suggested Remediation

Probable Cause

The gzip might be corrupt

Suggested Remediation

Retry the operation

Error occurred in the process of untaring a compressed file

Probable Cause

The compressed file might be corrupted

Suggested Remediation

Clear the cache and retry the operation

Probable Cause

Meshery adapter might not have write access

Suggested Remediation

Error occurred while applying custom manifest to the cluster

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reupload the kubconfig in the Meshery Server and reconnect the adapter

Kubernetes client is nil

Probable Cause

Kubernetes client not initialized

Suggested Remediation

Reconnect the adapter to Meshery Server

Error occurred while applying Helm Chart

Probable Cause

Suggested Remediation

Invalid helm chart configuration

Probable Cause

Latest version could not be found at the specified url

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while parsing application component in the OAM request made by Meshery server

Probable Cause

Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct

Suggested Remediation

Error occurred while parsing configuration in the request made by Meshery Server

Probable Cause

Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Trying to access a namespace which is not available

Suggested Remediation

Verify presence of namespace. Confirm Meshery ServiceAccount permissions

Top

Meshery Adapter for meshery-linkerd

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrEmptyConfigCode-1000`	Config is empty	search forum

Long Description

Probable Cause

Suggested Remediation

Unable to get the latest release info from the GithubAPI

Probable Cause

Checkout https://docs.github.com/en/rest/reference/repos#releases for more info

Suggested Remediation

Probable Cause

Invalid release format

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Checkout https://docs.github.com/en/rest/reference/repos#releases for more details

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while trying to install a sample application using manifests

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reconnect your adapter to meshery server to refresh the kubeclient

Error occurred while applying custom manifest to the cluster

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Make sure to apply a valid Kubernetes manifest

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while parsing application component in the OAM request made by Meshery server

Probable Cause

Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct

Suggested Remediation

Error occurred while parsing configuration in the request made by Meshery Server

Probable Cause

Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct

Suggested Remediation

Probable Cause

Suggested Remediation

Kubernetes client is nil

Probable Cause

Kubernetes client not initialized

Suggested Remediation

Reconnect the Meshery Adapter to Meshery Server

Probable Cause

The helm chart URL in additional properties of addon operation might be incorrect Could not apply service patch file for the given addon

Suggested Remediation

Version passed is invalid

Probable Cause

Version might not be prefixed with "stable-" or "edge-\

Suggested Remediation

Version should be prefixed with "stable-" or "edge-\ Version might be empty

Probable Cause

Could not get the namespace in cluster Could not update namespace in cluster

Suggested Remediation

Make sure the cluster is reachable

versions for linkerd could not be fetched

Probable Cause

could not reach github.com/linkerd/linkerd2 no versions could be fetched from linkerd release page

Suggested Remediation

make sure adapter is reachable to github

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

The repository could not be cloned or reached The repository url is invalid Could not reach the remote git repository

Suggested Remediation

Make sure the owner, repo and path is correct for fetching crd names

Top

Meshery Server

Severity	Error Name - Code	Short Description	Discussion
Fatal	`ErrCreatingUUIDInstanceCode-1001`	Unable to create UUID instance	search forum

Long Description

Unable to create UUID instance:

Probable Cause

Suggested Remediation

Error registering local OAM traits:

Probable Cause

Suggested Remediation

Error registering local OAM workloads:

Probable Cause

Suggested Remediation

Unable to retrieve the user's home directory:

Probable Cause

Suggested Remediation

Unable to create the directory for storing user data at:

Probable Cause

Suggested Remediation

Unable to create a new MapPreferencePersister instance:

Probable Cause

Suggested Remediation

Unable to auto migrate to database:

Probable Cause

Suggested Remediation

is invalid url skipping provider

Probable Cause

Suggested Remediation

ListenAndServe Error:

Probable Cause

Suggested Remediation

Error cleaning up local provider:

Probable Cause

Suggested Remediation

Error closing database instance:

Probable Cause

Suggested Remediation

Probable Cause

could not migrate tables into the database

Suggested Remediation

make sure the database instance passed is not nil

Probable Cause

could not migrate tables into the database

Suggested Remediation

make sure the database instance passed is not nil

Kubernetes config is not initialized with Meshery

Probable Cause

Kubernetes config is not accessible to Meshery or not valid

Suggested Remediation

Upload your Kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Kubernetes config is not initialized with Meshery

Probable Cause

Kubernetes config is not accessible to Meshery or not valid

Suggested Remediation

Upload your Kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

User token might be invalid db might be corrupted

Suggested Remediation

Relogin to Meshery

Cannot find valid grafana endpoint in user pref

Probable Cause

Grafana endpoint might not be reachable from Meshery

Suggested Remediation

Setup your Grafana Endpoint via the settings dashboard

Cannot find valid Prometheus endpoint in user pref

Probable Cause

Prometheus endpoint might not be reachable from Meshery

Suggested Remediation

Setup your Prometheus Endpoint via the settings dashboard

Probable Cause

Grafana query did not get executed from Meshery Grafana query is invalid

Suggested Remediation

Check if your Grafana query is correct Connect to Grafana from the settings page in the UI

Probable Cause

Prometheus query did not get executed from Meshery Prometheus query is invalid

Suggested Remediation

Check if your Prometheus query is correct Connect to Prometheus and Grafana from the settings page in the UI

Probable Cause

Prometheus endpoint might not be reachable from Meshery Prometheus endpoint is incorrect

Suggested Remediation

Check if your Prometheus endpoint is correct Connect to Prometheus from the settings page in the UI

unable to get static board

Probable Cause

No boards could be available in grafana

Suggested Remediation

Probable Cause

Request body is empty or faulty

Suggested Remediation

Check if the request is sent with proper values

Probable Cause

Failed due to invalid value of :

Suggested Remediation

please provide a valid value for :

Probable Cause

Websocket is blocked in the network Meshery UI is not able to reach the Meshery server

Suggested Remediation

Ensure Meshery UI is able to reach the Meshery server

Probable Cause

Websocket is blocked in the network Meshery UI is not able to reach the Meshery server

Suggested Remediation

Ensure Meshery UI is able to reach the Meshery server

Probable Cause

Meshery Cloud is not functional or reachable

Suggested Remediation

Make sure Meshery cloud is up and reachable

Probable Cause

Plugin is not available in the location plugin does not match with Meshery version

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

Plugin is not available in the location

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

plugin does not match with Meshery version

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

The data provided could be invalid

Suggested Remediation

Make sure to enter valid parameters in the form

Probable Cause

Query parameter is not a part of the request

Suggested Remediation

Make sure to pass the query paramater in the request

Probable Cause

Result Identifier provided is not valid Result did not persist in the database

Suggested Remediation

Make sure to provide the correct identifier for the result

Probable Cause

The performance spec format is invalid

Suggested Remediation

Make sure to provide the correct spec

Probable Cause

SMI results did not get persisted Result identifier is invalid

Suggested Remediation

Make sure to provide the correct identifier for the result

Probable Cause

The kubeconfig file does not exist in the location

Suggested Remediation

Make sure to upload the correct kubeconfig file

Probable Cause

The kubeconfig file is empty or not valid

Suggested Remediation

Make sure to upload the correct kubeconfig file

Probable Cause

The kubeconfig file is empty or not valid

Suggested Remediation

Make sure to upload the correct kubeconfig file

Probable Cause

The file does not exist in the location

Suggested Remediation

Make sure to upload the correct file

Probable Cause

Kubernetes might not be reachable from Meshery

Suggested Remediation

Make sure Meshery has connectivity to Kubernetes

meshLocationURL is empty to add an adapter

Probable Cause

meshLocationURL cannot be empty to add an adapter

Suggested Remediation

please provide the meshLocationURL

Probable Cause

Adapter operation invalid

Suggested Remediation

Make sure adapter is reachable and running

unable to find a valid adapter for the given adapter URL

Probable Cause

Given adapter URL is not valid

Suggested Remediation

Please provide a valid Adapter URL

Probable Cause

Adapter operation invalid

Suggested Remediation

Make sure adapter is reachable and running

Unable to create a mesh client Unable to ping the mesh adapter

Probable Cause

Adapter could not be pinged

Suggested Remediation

Unable to connect to the Mesh adapter using the given config, please try again

Probable Cause

Adapter operation invalid

Suggested Remediation

Make sure adapter is reachable and running

Probable Cause

unable to retrieve the requested data

Suggested Remediation

Make sure adapter is reachable and running

Probable Cause

uploaded application source content might be converted incorrect source type selected

Suggested Remediation

Select the correct source type Make sure the uploaded application source content is valid

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed is a valid json

Probable Cause

User token could be expired

Suggested Remediation

Re-initiate login

Probable Cause

Provider Database could be down or not reachable

Suggested Remediation

Make sure provider is up and reachable

Probable Cause

Provider Database could be down or not reachable

Suggested Remediation

Make sure provider is up and reachable

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

please provide a valid value for gen (load generator)

Probable Cause

Plugin is not available in the location plugin does not match with Meshery version

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

Yaml provided is not valid

Suggested Remediation

Make sure the yaml is valid and has the right parameters

Probable Cause

The format of the duration passed could be incorrect

Suggested Remediation

please refer to: https://docs.meshery.io/guides/mesheryctl#performance-management

Probable Cause

Load test endpoint could be not reachable

Suggested Remediation

Make sure load test endpoint is reachable

Probable Cause

Kubernetes might not be reachable from Meshery

Suggested Remediation

Make sure Meshery has connectivity to Kubernetes

Probable Cause

Meshery crashes

Suggested Remediation

Restart Meshery

Probable Cause

Load test name empty or not valid

Suggested Remediation

Provide a name for the test

Probable Cause

URL for load test could be invalid

Suggested Remediation

please refer to: https://docs.meshery.io/tasks/performance-management

Probable Cause

Suggested Remediation

Probable Cause

User session could be expired

Suggested Remediation

Re-initiate login

Probable Cause

Check Kubernetes

Suggested Remediation

Check your kubeconfig if valid Ensure Meshery is able to reach the Kubernetes cluster

Probable Cause

Workload Definition is invalid or unable to process

Suggested Remediation

Check Workload Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Connection Error: There was an error connecting to the selected target platform (i.e. Kubernetes cluster(s)). This connection might not be assigned to the selected environment.

Suggested Remediation

Verify that the Kubernetes connection status is 'Connected' or try uploading a new kubeconfig. Assign the current Kubernetes connection to the selected environment.

Probable Cause

Insufficient permission Insufficient storage

Suggested Remediation

check if sufficient permissions are available to create dir check if sufficient storage is available to create dir

Probable Cause

Suggested Remediation

Probable Cause

Context Name might be invalid or not present in the uploaded kubeconfig

Suggested Remediation

Check the context name, if the context name is correct and is present in the kubeconfig then try uploading the kubeconfig again

Probable Cause

Invalid data passed Unable to connect with provider

Suggested Remediation

Pass valid values for preferences Make sure provider supports saving user preferences Make sure you're connected with provider Make sure extension provides these preferences

Probable Cause

Cannot get the filter with the given Filter ID

Suggested Remediation

Check if the given Filter ID is correct

Probable Cause

Cannot save the Filter due to wrong path or URL Filter is corrupted.

Suggested Remediation

Check if the given path or URL of the filter is correct Try uplaoding a different filter

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Cannot save the Filter due to wrong path or URL

Suggested Remediation

Check if the given path or URL of the Filter is correct

Probable Cause

Failed to retrieve the list of all the Filters

Suggested Remediation

Probable Cause

Failed to delete Filter with the given ID

Suggested Remediation

Check if the Filter ID is correct

Probable Cause

Cannot save the design due to an invalid path or URL

Suggested Remediation

Confirm the correct path / URL to the design

Probable Cause

Cannot save the Application due to wrong path or URL

Suggested Remediation

Check if the given path or URL of the Application is correct

Probable Cause

Cannot get the design with the given design ID

Suggested Remediation

Check if the given design ID is correct

Probable Cause

Failed to delete design with the given ID

Suggested Remediation

Check if the design ID is correct

Probable Cause

Failed to retrieve the list of all the designs

Suggested Remediation

Probable Cause

Cannot save the design due to wrong path or URL

Suggested Remediation

Check if the provided path or URL of the design is correct. If you are providing a URL, it should be a direct URL to a downloadable file. For example, if the file is stored on GitHub, the URL should be 'https://raw.githubusercontent.com/path-to-file'.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Meshery handler failed to find a valid Kubernetes config for the deployment

Suggested Remediation

Try uploading a new kubeconfig and also ensure that Meshery can reach Kubernetes API server

Probable Cause

There might be a network disruption or the Meshery server does not have valid credentials.

Suggested Remediation

Try uploading a new kubeconfig. Check the network connection and Kubernetes cluster status. Verify that the Meshery server has valid and updated credentials to access the Kubernetes cluster.

Probable Cause

Meshery handler failed to find a valid Kubernetes context for the deployment

Suggested Remediation

Try uploading a new kubeconfig and also ensure that Meshery can reach Kubernetes API server

Probable Cause

unable to validate the value against given schema either value or schema might not be a valid cue expression

Suggested Remediation

Make sure that the schema and value provided are valid cue values Make sure both schema and value are sent Make sure appropriate value types are sent

Probable Cause

Remote provider might be not reachable Remote provider doesn't support this capability

Suggested Remediation

Ensure you have required permissions or retry after sometime.

Probable Cause

Suggested Remediation

Probable Cause

Failed to clone design with the given ID

Suggested Remediation

Check if the design ID is correct and the design is published

Probable Cause

Failed to clone Filter with the given ID

Suggested Remediation

Check if the Filter ID is correct and the Filter is published

Probable Cause

Suggested Remediation

Make sure the payload is valid

Probable Cause

Failed to publish catalog design

Suggested Remediation

Check if the design ID is correct and you are admin

Probable Cause

Failed to publish catalog filter

Suggested Remediation

Check if the filter ID is correct and you are admin

Probable Cause

Meshmodel entity could not be converted into valid json data in the registry was inconsistent

Suggested Remediation

make sure correct and consistent data is present inside the registry drop the Meshmodel tables and restart Meshery server

Probable Cause

User details could not be fetched from provider Your provider may not be reachable No user exists for the provided token

Suggested Remediation

Make sure provider is reachable Make sure you are logged in Make sure you are using a valid token

Probable Cause

The rego evaluation engine failed to resolve policies Design-File/Application-File is in incorrect format The policy query is invalid The evaluation engine response is unexpected for the code written

Suggested Remediation

Make sure the design-file/application-file is a valid yaml Make sure you're proving correct rego query Make sure the server is evaluating the query correctly, add some logs

Probable Cause

Suggested Remediation

Probable Cause

Insufficient permission Insufficient storage

Suggested Remediation

check if sufficient permissions are available to create file check if sufficient storage is available to create file

Probable Cause

Remote provider might be not reachable

Suggested Remediation

try running performance profile test without using certificates, update the profile without certificates

Probable Cause

might be due to insufficient permissions file was deleted manually

Suggested Remediation

please delete the file if present, path:

Probable Cause

Ensure that DB is not corrupted Ensure Remote Provider is working properly Ensure Meshery Server is working properly and connected to remote provider

Suggested Remediation

Try restarting Meshery server

Probable Cause

Invalid profile ID

Suggested Remediation

Check if the profile ID is correct

Probable Cause

Load test endpoint could be not reachable

Suggested Remediation

Make sure load test endpoint is reachable

Probable Cause

Remote provider might be not reachable. Token might have expired.

Suggested Remediation

Refresh your browser

Probable Cause

Application might already have been deleted You might not have enough permissions to perform the operation.

Suggested Remediation

Check the owner of the application.

Probable Cause

Request contains unknown query variables. Database is not reachable or corrupt.

Suggested Remediation

Check the request URL and try again.

Probable Cause

Provided event status not supported Event has been deleted or does not exist Database is corrupt.

Suggested Remediation

Verify event filter settings Reset database.

Probable Cause

Event might have been deleted and doesn't exist Database is corrupt.

Suggested Remediation

Verify event filter settings Reset database.

Probable Cause

Unsupported event status for your current version of Meshery Server.

Suggested Remediation

Confirm that the status you are using is valid and a supported event status. Refer to Meshery Docs for a list of event statuses. Check for availability of a new version of Meshery Server. Try upgrading to the latest version.

Probable Cause

Event has been deleted or does not exist. The requested event status is invalid. Meshery Database is corrupt.

Suggested Remediation

Verify that the event still exists. Verify that the requested event status is supported. Visit Settings and reset the Meshery database.

Probable Cause

Event has been deleted or does not exist. Meshery Database is corrupt.

Suggested Remediation

Probable Cause

MeshSync might not be reachable from Meshery

Suggested Remediation

Make sure Meshery has connectivity to MeshSync Try restarting Meshery server

Probable Cause

Remote provider might be not reachable Remote provider doesn't support this capability

Suggested Remediation

Ensure you have required permissions or retry after sometime.

Probable Cause

Unable to retrieve the connections

Suggested Remediation

Check if the cluster is connected and healthy, you can check it from k8s switcher in header

Probable Cause

Insufficient permissions to write into file file might be corrupted

Suggested Remediation

check if sufficient permissions are givent to the file check if the file is corrupted

Probable Cause

unable to read source directory source directory is corrupted

Suggested Remediation

check if the source directory is valid and has sufficient permissions check if the source directory is not corrupted

Probable Cause

unable to read source directory source directory is corrupted unable to persist in requested location OCI img may be corrupted

Suggested Remediation

check if the source directory is valid and has sufficient permissions check if the source directory is not corrupted check if sufficient permissions are available to write in requested location check if the OCI img is not corrupted

Probable Cause

unable to read from io.Reader

Suggested Remediation

check if the io.Reader is valid

Probable Cause

unable to uncompress OCI artifact OCI artifact may be corrupted

Suggested Remediation

check if the OCI artifact is valid and not corrupted

Probable Cause

unable to walk local directory local directory may be corrupted

Suggested Remediation

check if the local directory is valid and not corrupted

Probable Cause

unable to convert k8s manifest to design k8s manifest may be corrupted incorrect source type selected

Suggested Remediation

check if the k8s manifest is valid and not corrupted check if the source type selected is Kubernetes Manifest

Probable Cause

unable to convert docker compose to design docker compose may be corrupted incorrect source type selected

Suggested Remediation

check if the docker compose is valid and not corrupted check if the source type selected is Docker Compose

Probable Cause

unable to marshal design into YAML design may be corrupted

Suggested Remediation

check if the design is valid and not corrupted

Probable Cause

unable to convert helm chart to design helm chart may be corrupted incorrect source type selected

Suggested Remediation

check if the helm chart is valid and not corrupted check if the source type selected is Helm Chart

Probable Cause

provided id is not a valid uuid

Suggested Remediation

provide a valid uuid

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not reachable from Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure the network connectivity is up between meshery server and the service endpoint

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Possible issues with Kubernetes cluster configuration or network connectivity.

Suggested Remediation

Check the Kubernetes cluster's configuration, ensure necessary resources are available, and verify network connectivity.

Probable Cause

Possible issues with Kubernetes cluster configuration or network connectivity.

Suggested Remediation

Check the Kubernetes cluster's configuration, ensure necessary resources are available, and verify network connectivity.

Probable Cause

Possible issues with Docker configuration, container networking, or resource availability.

Suggested Remediation

Check Docker configuration settings, ensure containers have proper networking access, and verify available resources.

Probable Cause

Possible issues with Docker configuration, container networking, or resource availability.

Suggested Remediation

Check Docker configuration settings, ensure containers have proper networking access, and verify available resources.

Probable Cause

Your platform is not supported for deploying Meshery Adapters

Suggested Remediation

Consider using a supported platform for deploying Meshery Adapters

Probable Cause

Current platform is not supported for undeploying Meshery Adapters

Suggested Remediation

Consider using a supported platform for undeploying Meshery Adapters

Probable Cause

Suggested Remediation

Kubernetes config is not initialized with Meshery

Probable Cause

Kubernetes config is not accessible to Meshery or not valid

Suggested Remediation

Upload your Kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to write MeshSync data to the Meshery Database

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

Invalid Query performed in Meshery Database

Probable Cause

Suggested Remediation

GraphQL subscription for MeshSync stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

Kubernetes config is not initialized with Meshery 1

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to create a broker subscription

Probable Cause

Could be a network issue Meshery Broker could have crashed

Suggested Remediation

Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster

Unable to create a broker publisher

Probable Cause

Could be a network issue Meshery Broker could have crashed

Suggested Remediation

Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster

Meshery Database handler is not accessible to perform operations

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

Probable Cause

Kubernetes cluster might not be connected Leftover resources from partial install

Suggested Remediation

Try reinstalling Try reconnecting your kubernetes cluster Clean up artifacts from preinstalled helm release manually

Meshery controller handlers may not be available

Probable Cause

Suggested Remediation

Make sure the controllers are deployed and their handlers are configured

Meshery controller handlers may not be available

Probable Cause

Suggested Remediation

Make sure the controllers are deployed and their handlers are configured

Kubernetes config is not initialized with Meshery 2

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to update MeshSync data to the Meshery Database

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

Unable to read MeshSync data to the Meshery Database

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

The Graphql query requested is invalid

Probable Cause

Suggested Remediation

Check the query parameters and syntax of the query being run

Kubernetes config is not initialized with Meshery

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

GraphQL subscription for MeshSync stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

GraphQL subscription for Operator stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

GraphQL subscription for Addons stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

GraphQL subscription for Control Plane stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Kubernetes config is not initialized with Meshery 1

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to create a broker publisher

Probable Cause

Could be a network issue Meshery Broker could have crashed

Suggested Remediation

Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster

MeshSync custom controller is not running in your kubernetes cluster

Probable Cause

Meshery Operator is not running in your cluster or is crashing

Suggested Remediation

Enable Meshery Operator from the settings page in the UI Check for logs in the meshery-operator pods from inside the application for more information

GraphQL subscription for Data Plane stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

Meshery Broker is not connected to Meshery Server

Probable Cause

Meshery Broker is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server has access to the Broker

Probable Cause

The table in the database might not exist

Suggested Remediation

Probable Cause

There might be something wrong with the Meshery or Meshery Cloud

Suggested Remediation

Try again, if still exist, please post an issue on Meshery repository

invalid oam type requested, supported types are workload, scope, trait

Probable Cause

Suggested Remediation

invalid kubernetes resource type or couldn't find the specified resource

Probable Cause

Suggested Remediation

Meshery is not able to get the current kubernetes context

Probable Cause

Meshery is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

GraphQL subscription for designs stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for Applications stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for Filters stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

There might be something wrong with the Meshery or Meshery Cloud

Probable Cause

Could be a network issue

Suggested Remediation

GraphQL subscription for ClusterResources Subscription stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Probable Cause

Table in the database might not exists

Suggested Remediation

GraphQL subscription for MeshModelSummary Subscription stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Probable Cause

Table in the database might not exists

Suggested Remediation

Probable Cause

Registry Manager might not exists

Suggested Remediation

Probable Cause

table in the database might be corrupted

Suggested Remediation

try resetting database from settings

Probable Cause

Suggested Remediation

GraphQL subscription for PerformanceProfiles stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for PerformanceResult stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Database operation failed. Please ensure that the database isn't corrupted

Probable Cause

Could be a db issue

Suggested Remediation

Confirm that database connection is working as expected.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Provided ID is not a valid uuid.

Suggested Remediation

Hard delete and reinitialise the connection process.

Probable Cause

The machine context has become invalid.

Suggested Remediation

Retry the opereation or try archiving and reinitializing the connection

Probable Cause

Provided ID is not a valid uuid.

Suggested Remediation

Hard delete and reinitialise the connection process.

Probable Cause

Suggested Remediation

Unable to initializes client for interacting with an instance of Grafana server

Probable Cause

Invalid Grafana Endpoint or API-Key

Suggested Remediation

Update your Grafana URL and API-Key from the settings page in the UI

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Given resultID is nil

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed has json tags

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed is a valid json

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Invalid URL Invalid API-Key

Suggested Remediation

Probable Cause

Grafana endpoint might not be reachable from Meshery Grafana endpoint is incorrect

Suggested Remediation

Check if your Grafana endpoint is correct Connect to Grafana from the settings page in the UI

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Name field is either not present or is not valid

Probable Cause

Suggested Remediation

Name field is either not present or is not valid

Probable Cause

Suggested Remediation

Name field is either not present or is not valid

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Value of JWKs is nil

Probable Cause

Suggested Remediation

JWK not found for the given KeyID

Probable Cause

Suggested Remediation

Token is invalid, it has expired

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed is a valid json

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Network connectivity to Remote Provider may not be available. Session might have expired; token could be invalid.

Suggested Remediation

Verify that the Remote Provider is available. Ensure that you have an active session / valid token.

You dont have access to the capability

Probable Cause

Not logged in to the vaild remote Provider

Suggested Remediation

Connect to the vaild remote Provider Ask the Provider Adim for access

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

User doesn't have permission to save content.\nDatabase unreachable.\nDatabase locked or corrupt.\nContent unsupported.

Suggested Remediation

Retry fetching content\nRetry sigining in\nLogin with correct user account\nRetry after deleting '~/.meshery/config'.

Probable Cause

Sample content does not exist.\nContent file format not supported.\nUser doesn't have permission to read sample content.\nContent file corrupt.

Suggested Remediation

Try restarting Meshery.\nTry fetching content again.

Probable Cause

The content is not present at the specified url endpoint HTTP requests failed

Suggested Remediation

Make sure the content is available at the endpoints Make sure that Github is reachable and the http requests are not failing

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Unable to find meshery broker in the cluster

Probable Cause

Invalid Grafana Endpoint or API-Key

Suggested Remediation

Update your Grafana URL and API-Key from the settings page in the UI

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Make sure meshery broker is healthy

Probable Cause

Suggested Remediation

Make sure meshery broker is healthy

kubernetes context already persisted with provider

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Make sure the configurations are correct

Probable Cause

Unable to revoke token. Token appears to be a malformed base64 token.

Suggested Remediation

Try logging out (again) in order to fully close your session (and revoke the session token).

Probable Cause

Invalid session token. Token has revoked.

Suggested Remediation

Probable Cause

email address provided might not be valid insufficient permission

Suggested Remediation

Ensure that you are the owner of the design you are sharing Try again later Try using an alternate email address

Probable Cause

Remote provider server may be down or not accepting requests.

Suggested Remediation

Make sure remote provider server is healthy and accepting requests.

Probable Cause

Email address provided might not be valid Verify that you have sufficient permission to share the filter. You should be the owner of the filter

Suggested Remediation

Verify the spelling of the email address. Try using an alternate email address. Ensure that you are the owner of the filter you are sharing or have sharing permission assigned.

Probable Cause

Database could be down or not reachable Meshery Database handler is not accessible to perform operations

Suggested Remediation

Restart Meshery Server or Perform Hard Reset

Probable Cause

The Kubernetes API server is not reachable. Credentials are invalid.

Suggested Remediation

Verify network connectivity and Kubernetes API responsiveness between Meshery Server and your cluster. Ensure client credential is not expired and is properly formed. Remove the cluster credential and enable 'insecure-skip-tls-verify'.

Probable Cause

Meshery Database handler is not accessible to perform operations

Suggested Remediation

Restart Meshery Server or Perform Hard Reset

Probable Cause

Connection was already deleted User might not have necessary privileges

Suggested Remediation

Try refresing, you might be seeing stale data on the dashboard Check if the user has necessary privileges

The record in the database does not exist.

Probable Cause

The record might have been deleted.

Suggested Remediation

Probable Cause

The credential object is not valid

Suggested Remediation

Ensure all the required fields are provided

Probable Cause

The connection object is not valid

Suggested Remediation

Ensure all the required fields are provided

Probable Cause

Prometheus endpoint might not be reachable from Meshery Prometheus endpoint is incorrect

Suggested Remediation

Check if your Prometheus endpoint are correct Connect to Prometheus from the settings page in the UI

Probable Cause

Grafana endpoint might not be reachable from Meshery Grafana endpoint is incorrect

Suggested Remediation

Check if your Grafana Endpoint is correct Connect to Grafana from the settings page in the UI

Probable Cause

Record already exist Database connection is not reachable

Suggested Remediation

Delete the record or try updating the record instead of recreating Rest the database connection

Probable Cause

component generation was canceled due to deletion or reload of K8s context Invalid kubeconfig Filters passed incorrectly in config Could not fetch API resources from Kubernetes server

Suggested Remediation

If there is the log "Starting to register ..." for the same contextID after this error means that for some reason the context was reloaded which caused this run to abort. In that case, this error can be ignored. Make sure that the configuration filters passed are in accordance with output from /openapi/v2

Probable Cause

Invalid kubeconfig Filters passed incorrectly in config Could not fetch API resources from Kubernetes server

Suggested Remediation

Make sure that the configuration filters passed are in accordance with output from /openapi/v2

Probable Cause

Ensure manifests are valid and also use the restricted YAML features like using only "strings" in the field names

Suggested Remediation

Ensure YAML is a valid Kubernetes Manifest

Probable Cause

Invalid Manifest Meshery doesn't identifies the Resource mentioned in the Manifest

Suggested Remediation

Check if all of the meshery adapters are running Check if Meshery has identified and registered Kubernetes components

Probable Cause

Invalid cytoscape body Service name is empty for one or more services _data does not have correct data

Suggested Remediation

Make sure cytoscape is valid Check if valid service name was passed in the request Make sure _data field has "settings" field

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

token is expired/revoked Remote Provider is not reachable or unavailable

Suggested Remediation

Try re-authenticating with the remote provider Verify remote provider for its reachability or availability.

Probable Cause

Requested resource is not reachable. Unable to instantiate TCP connection

Suggested Remediation

Ensure correct URL is specified Ensure network connectivity to the resource from your network

Probable Cause

Object has invalid yaml format

Suggested Remediation

Make sure to input a valid yaml object

Our server cannot provide live events streaming at the moment. This might be due to a technical issue with our system.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

callback URL might be empty

Suggested Remediation

Make sure the callback URL is not empty

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

The session data might be corrupted or not properly saved.

Suggested Remediation

Probable Cause

The session might not exist or could have been deleted.

Suggested Remediation

Check if the session data was correctly saved.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Make sure the URL is correct

Probable Cause

An error occurred while attempting to close response body reader.

Suggested Remediation

Ensure the response body reader is in a state that allows it to be closed.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Session might already been revoked Remote provider is not able to complete the request

Suggested Remediation

Close the tabs and open Meshery UI again. Optionally, try using a private/incognito browser window.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Possible causes include invalid Kubernetes context, missing configuration, or network issues.

Suggested Remediation

Verify the Kubernetes context configuration. Ensure the Kubernetes cluster is reachable and the configuration is correct.

Probable Cause

Possible causes include invalid Kubernetes context, missing or incorrect configuration, or network issues.

Suggested Remediation

Verify the Kubernetes context configuration. Ensure the Kubernetes cluster is reachable and the configuration is correct.

Probable Cause

Possible causes include invalid input data, database issues, or network problems.

Suggested Remediation

Verify the input data is correct. Ensure the database is reachable and properly configured.

Probable Cause

Possible causes include incorrect database file path, invalid database engine configuration, or insufficient permissions.

Suggested Remediation

Verify the database file path and ensure it is correct. Check the database engine configuration and ensure the application has the necessary permissions to access the database file.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to delete the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to create the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or resource not found.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to access the resource.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to delete the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource configuration, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource configuration and ensure it is correct. Ensure you have the necessary permissions to recreate the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource configuration, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource configuration and ensure it is correct. Ensure you have the necessary permissions to update the resource. Check network connectivity to the Kubernetes cluster.

Unable to find "token" cookie in the request.

Probable Cause

User is not authenticated with the selected Provider. Browser might be restricting use of cookies.

Suggested Remediation

Choose a Provider and login to establish an active session (receive a new token and cookie). Optionally, try using a private/incognito browser window. Verify that your browser settings allow cookies.

ActedUpon, Action, Category and Severity are required fields of an event

Probable Cause

Suggested Remediation

Ensure that ActedUpon, Action, Category and Severity are present in the event

Probable Cause

Given models may not be in accordance with Meshery's schema Internal(OS level) error while reading files

Suggested Remediation

Make sure the models being seeded are valid in accordance with Meshery's schema If it is an internal error, please try again after some time

Probable Cause

Entity definition might not be in accordance with schema Entity version might not be supported by Meshery

Suggested Remediation

See the registration logs (found at $HOME/.meshery/logs/registry/registry-logs.log) to find out which Entity failed to be imported with more specific error information.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Component might not have been registered The component might not be supported by default, in the version of Meshery you are currently using.

Suggested Remediation

Ensure component definition is valid JSON/YAML. Import the model and try again.

Probable Cause

Remote provider server may be down or not accepting requests.

Suggested Remediation

Make sure remote provider server is healthy and accepting requests.

Probable Cause

Suggested Remediation

Export design in one of the supported format.

Unable to locate the compressed file(.tar.gz) inside the OCI image.

Probable Cause

The OCI image does not contain a ziped file.

Suggested Remediation

Verify that the OCI image contains a ziped file.

Probable Cause

The provided file type is wrong

Suggested Remediation

Verify the file type

Probable Cause

Unable to create OPA instance, policies will not be evaluated.

Suggested Remediation

Ensure relationships are registered

Probable Cause

The server might be down or temporarily unavailable. There could be network connectivity issues between the client and the server. The API endpoint might be misconfigured, or the server is experiencing high load.

Suggested Remediation

Check if the server is online and operational. Verify network connectivity and ensure there are no firewalls or DNS issues blocking the request. Confirm the API endpoint is correct and functional.

Top

Meshery Server

Severity	Error Name - Code	Short Description	Discussion
Fatal	`ErrCreatingUUIDInstanceCode-1001`	Unable to create UUID instance	search forum

Long Description

Unable to create UUID instance:

Probable Cause

Suggested Remediation

Error registering local OAM traits:

Probable Cause

Suggested Remediation

Error registering local OAM workloads:

Probable Cause

Suggested Remediation

Unable to retrieve the user's home directory:

Probable Cause

Suggested Remediation

Unable to create the directory for storing user data at:

Probable Cause

Suggested Remediation

Unable to create a new MapPreferencePersister instance:

Probable Cause

Suggested Remediation

Unable to auto migrate to database:

Probable Cause

Suggested Remediation

is invalid url skipping provider

Probable Cause

Suggested Remediation

ListenAndServe Error:

Probable Cause

Suggested Remediation

Error cleaning up local provider:

Probable Cause

Suggested Remediation

Error closing database instance:

Probable Cause

Suggested Remediation

Probable Cause

could not migrate tables into the database

Suggested Remediation

make sure the database instance passed is not nil

Probable Cause

could not migrate tables into the database

Suggested Remediation

make sure the database instance passed is not nil

Kubernetes config is not initialized with Meshery

Probable Cause

Kubernetes config is not accessible to Meshery or not valid

Suggested Remediation

Upload your Kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Kubernetes config is not initialized with Meshery

Probable Cause

Kubernetes config is not accessible to Meshery or not valid

Suggested Remediation

Upload your Kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

User token might be invalid db might be corrupted

Suggested Remediation

Relogin to Meshery

Cannot find valid grafana endpoint in user pref

Probable Cause

Grafana endpoint might not be reachable from Meshery

Suggested Remediation

Setup your Grafana Endpoint via the settings dashboard

Cannot find valid Prometheus endpoint in user pref

Probable Cause

Prometheus endpoint might not be reachable from Meshery

Suggested Remediation

Setup your Prometheus Endpoint via the settings dashboard

Probable Cause

Grafana query did not get executed from Meshery Grafana query is invalid

Suggested Remediation

Check if your Grafana query is correct Connect to Grafana from the settings page in the UI

Probable Cause

Prometheus query did not get executed from Meshery Prometheus query is invalid

Suggested Remediation

Check if your Prometheus query is correct Connect to Prometheus and Grafana from the settings page in the UI

Probable Cause

Prometheus endpoint might not be reachable from Meshery Prometheus endpoint is incorrect

Suggested Remediation

Check if your Prometheus endpoint is correct Connect to Prometheus from the settings page in the UI

unable to get static board

Probable Cause

No boards could be available in grafana

Suggested Remediation

Probable Cause

Request body is empty or faulty

Suggested Remediation

Check if the request is sent with proper values

Probable Cause

Failed due to invalid value of :

Suggested Remediation

please provide a valid value for :

Probable Cause

Websocket is blocked in the network Meshery UI is not able to reach the Meshery server

Suggested Remediation

Ensure Meshery UI is able to reach the Meshery server

Probable Cause

Websocket is blocked in the network Meshery UI is not able to reach the Meshery server

Suggested Remediation

Ensure Meshery UI is able to reach the Meshery server

Probable Cause

Meshery Cloud is not functional or reachable

Suggested Remediation

Make sure Meshery cloud is up and reachable

Probable Cause

Plugin is not available in the location plugin does not match with Meshery version

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

Plugin is not available in the location

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

plugin does not match with Meshery version

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

The data provided could be invalid

Suggested Remediation

Make sure to enter valid parameters in the form

Probable Cause

Query parameter is not a part of the request

Suggested Remediation

Make sure to pass the query paramater in the request

Probable Cause

Result Identifier provided is not valid Result did not persist in the database

Suggested Remediation

Make sure to provide the correct identifier for the result

Probable Cause

The performance spec format is invalid

Suggested Remediation

Make sure to provide the correct spec

Probable Cause

SMI results did not get persisted Result identifier is invalid

Suggested Remediation

Make sure to provide the correct identifier for the result

Probable Cause

The kubeconfig file does not exist in the location

Suggested Remediation

Make sure to upload the correct kubeconfig file

Probable Cause

The kubeconfig file is empty or not valid

Suggested Remediation

Make sure to upload the correct kubeconfig file

Probable Cause

The kubeconfig file is empty or not valid

Suggested Remediation

Make sure to upload the correct kubeconfig file

Probable Cause

The file does not exist in the location

Suggested Remediation

Make sure to upload the correct file

Probable Cause

Kubernetes might not be reachable from Meshery

Suggested Remediation

Make sure Meshery has connectivity to Kubernetes

meshLocationURL is empty to add an adapter

Probable Cause

meshLocationURL cannot be empty to add an adapter

Suggested Remediation

please provide the meshLocationURL

Probable Cause

Adapter operation invalid

Suggested Remediation

Make sure adapter is reachable and running

unable to find a valid adapter for the given adapter URL

Probable Cause

Given adapter URL is not valid

Suggested Remediation

Please provide a valid Adapter URL

Probable Cause

Adapter operation invalid

Suggested Remediation

Make sure adapter is reachable and running

Unable to create a mesh client Unable to ping the mesh adapter

Probable Cause

Adapter could not be pinged

Suggested Remediation

Unable to connect to the Mesh adapter using the given config, please try again

Probable Cause

Adapter operation invalid

Suggested Remediation

Make sure adapter is reachable and running

Probable Cause

unable to retrieve the requested data

Suggested Remediation

Make sure adapter is reachable and running

Probable Cause

uploaded application source content might be converted incorrect source type selected

Suggested Remediation

Select the correct source type Make sure the uploaded application source content is valid

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed is a valid json

Probable Cause

User token could be expired

Suggested Remediation

Re-initiate login

Probable Cause

Provider Database could be down or not reachable

Suggested Remediation

Make sure provider is up and reachable

Probable Cause

Provider Database could be down or not reachable

Suggested Remediation

Make sure provider is up and reachable

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

please provide a valid value for gen (load generator)

Probable Cause

Plugin is not available in the location plugin does not match with Meshery version

Suggested Remediation

Make sure the plugin is compatible with Meshery server

Probable Cause

Yaml provided is not valid

Suggested Remediation

Make sure the yaml is valid and has the right parameters

Probable Cause

The format of the duration passed could be incorrect

Suggested Remediation

please refer to: https://docs.meshery.io/guides/mesheryctl#performance-management

Probable Cause

Load test endpoint could be not reachable

Suggested Remediation

Make sure load test endpoint is reachable

Probable Cause

Kubernetes might not be reachable from Meshery

Suggested Remediation

Make sure Meshery has connectivity to Kubernetes

Probable Cause

Meshery crashes

Suggested Remediation

Restart Meshery

Probable Cause

Load test name empty or not valid

Suggested Remediation

Provide a name for the test

Probable Cause

URL for load test could be invalid

Suggested Remediation

please refer to: https://docs.meshery.io/tasks/performance-management

Probable Cause

Suggested Remediation

Probable Cause

User session could be expired

Suggested Remediation

Re-initiate login

Probable Cause

Check Kubernetes

Suggested Remediation

Check your kubeconfig if valid Ensure Meshery is able to reach the Kubernetes cluster

Probable Cause

Workload Definition is invalid or unable to process

Suggested Remediation

Check Workload Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Trait Definition is invalid or unable to process

Suggested Remediation

Check Trait Definition

Probable Cause

Connection Error: There was an error connecting to the selected target platform (i.e. Kubernetes cluster(s)). This connection might not be assigned to the selected environment.

Suggested Remediation

Verify that the Kubernetes connection status is 'Connected' or try uploading a new kubeconfig. Assign the current Kubernetes connection to the selected environment.

Probable Cause

Insufficient permission Insufficient storage

Suggested Remediation

check if sufficient permissions are available to create dir check if sufficient storage is available to create dir

Probable Cause

Suggested Remediation

Probable Cause

Context Name might be invalid or not present in the uploaded kubeconfig

Suggested Remediation

Check the context name, if the context name is correct and is present in the kubeconfig then try uploading the kubeconfig again

Probable Cause

Invalid data passed Unable to connect with provider

Suggested Remediation

Pass valid values for preferences Make sure provider supports saving user preferences Make sure you're connected with provider Make sure extension provides these preferences

Probable Cause

Cannot get the filter with the given Filter ID

Suggested Remediation

Check if the given Filter ID is correct

Probable Cause

Cannot save the Filter due to wrong path or URL Filter is corrupted.

Suggested Remediation

Check if the given path or URL of the filter is correct Try uplaoding a different filter

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Cannot save the Filter due to wrong path or URL

Suggested Remediation

Check if the given path or URL of the Filter is correct

Probable Cause

Failed to retrieve the list of all the Filters

Suggested Remediation

Probable Cause

Failed to delete Filter with the given ID

Suggested Remediation

Check if the Filter ID is correct

Probable Cause

Cannot save the design due to an invalid path or URL

Suggested Remediation

Confirm the correct path / URL to the design

Probable Cause

Cannot save the Application due to wrong path or URL

Suggested Remediation

Check if the given path or URL of the Application is correct

Probable Cause

Cannot get the design with the given design ID

Suggested Remediation

Check if the given design ID is correct

Probable Cause

Failed to delete design with the given ID

Suggested Remediation

Check if the design ID is correct

Probable Cause

Failed to retrieve the list of all the designs

Suggested Remediation

Probable Cause

Cannot save the design due to wrong path or URL

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Meshery handler failed to find a valid Kubernetes config for the deployment

Suggested Remediation

Try uploading a new kubeconfig and also ensure that Meshery can reach Kubernetes API server

Probable Cause

There might be a network disruption or the Meshery server does not have valid credentials.

Suggested Remediation

Try uploading a new kubeconfig. Check the network connection and Kubernetes cluster status. Verify that the Meshery server has valid and updated credentials to access the Kubernetes cluster.

Probable Cause

Meshery handler failed to find a valid Kubernetes context for the deployment

Suggested Remediation

Try uploading a new kubeconfig and also ensure that Meshery can reach Kubernetes API server

Probable Cause

unable to validate the value against given schema either value or schema might not be a valid cue expression

Suggested Remediation

Make sure that the schema and value provided are valid cue values Make sure both schema and value are sent Make sure appropriate value types are sent

Probable Cause

Remote provider might be not reachable Remote provider doesn't support this capability

Suggested Remediation

Ensure you have required permissions or retry after sometime.

Probable Cause

Suggested Remediation

Probable Cause

Failed to clone design with the given ID

Suggested Remediation

Check if the design ID is correct and the design is published

Probable Cause

Failed to clone Filter with the given ID

Suggested Remediation

Check if the Filter ID is correct and the Filter is published

Probable Cause

Suggested Remediation

Make sure the payload is valid

Probable Cause

Failed to publish catalog design

Suggested Remediation

Check if the design ID is correct and you are admin

Probable Cause

Failed to publish catalog filter

Suggested Remediation

Check if the filter ID is correct and you are admin

Probable Cause

Meshmodel entity could not be converted into valid json data in the registry was inconsistent

Suggested Remediation

make sure correct and consistent data is present inside the registry drop the Meshmodel tables and restart Meshery server

Probable Cause

User details could not be fetched from provider Your provider may not be reachable No user exists for the provided token

Suggested Remediation

Make sure provider is reachable Make sure you are logged in Make sure you are using a valid token

Probable Cause

The rego evaluation engine failed to resolve policies Design-File/Application-File is in incorrect format The policy query is invalid The evaluation engine response is unexpected for the code written

Suggested Remediation

Make sure the design-file/application-file is a valid yaml Make sure you're proving correct rego query Make sure the server is evaluating the query correctly, add some logs

Probable Cause

Suggested Remediation

Probable Cause

Insufficient permission Insufficient storage

Suggested Remediation

check if sufficient permissions are available to create file check if sufficient storage is available to create file

Probable Cause

Remote provider might be not reachable

Suggested Remediation

try running performance profile test without using certificates, update the profile without certificates

Probable Cause

might be due to insufficient permissions file was deleted manually

Suggested Remediation

please delete the file if present, path:

Probable Cause

Ensure that DB is not corrupted Ensure Remote Provider is working properly Ensure Meshery Server is working properly and connected to remote provider

Suggested Remediation

Try restarting Meshery server

Probable Cause

Invalid profile ID

Suggested Remediation

Check if the profile ID is correct

Probable Cause

Load test endpoint could be not reachable

Suggested Remediation

Make sure load test endpoint is reachable

Probable Cause

Remote provider might be not reachable. Token might have expired.

Suggested Remediation

Refresh your browser

Probable Cause

Application might already have been deleted You might not have enough permissions to perform the operation.

Suggested Remediation

Check the owner of the application.

Probable Cause

Request contains unknown query variables. Database is not reachable or corrupt.

Suggested Remediation

Check the request URL and try again.

Probable Cause

Provided event status not supported Event has been deleted or does not exist Database is corrupt.

Suggested Remediation

Verify event filter settings Reset database.

Probable Cause

Event might have been deleted and doesn't exist Database is corrupt.

Suggested Remediation

Verify event filter settings Reset database.

Probable Cause

Unsupported event status for your current version of Meshery Server.

Suggested Remediation

Probable Cause

Event has been deleted or does not exist. The requested event status is invalid. Meshery Database is corrupt.

Suggested Remediation

Verify that the event still exists. Verify that the requested event status is supported. Visit Settings and reset the Meshery database.

Probable Cause

Event has been deleted or does not exist. Meshery Database is corrupt.

Suggested Remediation

Probable Cause

MeshSync might not be reachable from Meshery

Suggested Remediation

Make sure Meshery has connectivity to MeshSync Try restarting Meshery server

Probable Cause

Remote provider might be not reachable Remote provider doesn't support this capability

Suggested Remediation

Ensure you have required permissions or retry after sometime.

Probable Cause

Unable to retrieve the connections

Suggested Remediation

Check if the cluster is connected and healthy, you can check it from k8s switcher in header

Probable Cause

Insufficient permissions to write into file file might be corrupted

Suggested Remediation

check if sufficient permissions are givent to the file check if the file is corrupted

Probable Cause

unable to read source directory source directory is corrupted

Suggested Remediation

check if the source directory is valid and has sufficient permissions check if the source directory is not corrupted

Probable Cause

unable to read source directory source directory is corrupted unable to persist in requested location OCI img may be corrupted

Suggested Remediation

Probable Cause

unable to read from io.Reader

Suggested Remediation

check if the io.Reader is valid

Probable Cause

unable to uncompress OCI artifact OCI artifact may be corrupted

Suggested Remediation

check if the OCI artifact is valid and not corrupted

Probable Cause

unable to walk local directory local directory may be corrupted

Suggested Remediation

check if the local directory is valid and not corrupted

Probable Cause

unable to convert k8s manifest to design k8s manifest may be corrupted incorrect source type selected

Suggested Remediation

check if the k8s manifest is valid and not corrupted check if the source type selected is Kubernetes Manifest

Probable Cause

unable to convert docker compose to design docker compose may be corrupted incorrect source type selected

Suggested Remediation

check if the docker compose is valid and not corrupted check if the source type selected is Docker Compose

Probable Cause

unable to marshal design into YAML design may be corrupted

Suggested Remediation

check if the design is valid and not corrupted

Probable Cause

unable to convert helm chart to design helm chart may be corrupted incorrect source type selected

Suggested Remediation

check if the helm chart is valid and not corrupted check if the source type selected is Helm Chart

Probable Cause

provided id is not a valid uuid

Suggested Remediation

provide a valid uuid

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource

Probable Cause

Kubernetes API server might not be reachable from the Meshery server Requested resource might not reachable from Meshery server

Suggested Remediation

Make sure kubernetes API server is reachable from meshery server Make sure the network connectivity is up between meshery server and the service endpoint

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Possible issues with Kubernetes cluster configuration or network connectivity.

Suggested Remediation

Check the Kubernetes cluster's configuration, ensure necessary resources are available, and verify network connectivity.

Probable Cause

Possible issues with Kubernetes cluster configuration or network connectivity.

Suggested Remediation

Check the Kubernetes cluster's configuration, ensure necessary resources are available, and verify network connectivity.

Probable Cause

Possible issues with Docker configuration, container networking, or resource availability.

Suggested Remediation

Check Docker configuration settings, ensure containers have proper networking access, and verify available resources.

Probable Cause

Possible issues with Docker configuration, container networking, or resource availability.

Suggested Remediation

Check Docker configuration settings, ensure containers have proper networking access, and verify available resources.

Probable Cause

Your platform is not supported for deploying Meshery Adapters

Suggested Remediation

Consider using a supported platform for deploying Meshery Adapters

Probable Cause

Current platform is not supported for undeploying Meshery Adapters

Suggested Remediation

Consider using a supported platform for undeploying Meshery Adapters

Probable Cause

Suggested Remediation

Kubernetes config is not initialized with Meshery

Probable Cause

Kubernetes config is not accessible to Meshery or not valid

Suggested Remediation

Upload your Kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to write MeshSync data to the Meshery Database

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

Invalid Query performed in Meshery Database

Probable Cause

Suggested Remediation

GraphQL subscription for MeshSync stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

Kubernetes config is not initialized with Meshery 1

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to create a broker subscription

Probable Cause

Could be a network issue Meshery Broker could have crashed

Suggested Remediation

Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster

Unable to create a broker publisher

Probable Cause

Could be a network issue Meshery Broker could have crashed

Suggested Remediation

Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster

Meshery Database handler is not accessible to perform operations

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

Probable Cause

Kubernetes cluster might not be connected Leftover resources from partial install

Suggested Remediation

Try reinstalling Try reconnecting your kubernetes cluster Clean up artifacts from preinstalled helm release manually

Meshery controller handlers may not be available

Probable Cause

Suggested Remediation

Make sure the controllers are deployed and their handlers are configured

Meshery controller handlers may not be available

Probable Cause

Suggested Remediation

Make sure the controllers are deployed and their handlers are configured

Kubernetes config is not initialized with Meshery 2

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to update MeshSync data to the Meshery Database

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

Unable to read MeshSync data to the Meshery Database

Probable Cause

Meshery Database is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

The Graphql query requested is invalid

Probable Cause

Suggested Remediation

Check the query parameters and syntax of the query being run

Kubernetes config is not initialized with Meshery

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

GraphQL subscription for MeshSync stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

GraphQL subscription for Operator stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

GraphQL subscription for Addons stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

GraphQL subscription for Control Plane stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Kubernetes config is not initialized with Meshery 1

Probable Cause

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Unable to create a broker publisher

Probable Cause

Could be a network issue Meshery Broker could have crashed

Suggested Remediation

Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster

MeshSync custom controller is not running in your kubernetes cluster

Probable Cause

Meshery Operator is not running in your cluster or is crashing

Suggested Remediation

Enable Meshery Operator from the settings page in the UI Check for logs in the meshery-operator pods from inside the application for more information

GraphQL subscription for Data Plane stopped

Probable Cause

Could be a network issue

Suggested Remediation

Check if meshery server is reachable from the browser

Meshery Broker is not connected to Meshery Server

Probable Cause

Meshery Broker is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server has access to the Broker

Probable Cause

The table in the database might not exist

Suggested Remediation

Probable Cause

There might be something wrong with the Meshery or Meshery Cloud

Suggested Remediation

Try again, if still exist, please post an issue on Meshery repository

invalid oam type requested, supported types are workload, scope, trait

Probable Cause

Suggested Remediation

invalid kubernetes resource type or couldn't find the specified resource

Probable Cause

Suggested Remediation

Meshery is not able to get the current kubernetes context

Probable Cause

Meshery is crashed or not reachable

Suggested Remediation

Restart Meshery Server Please check if Meshery server is accessible to the Database

GraphQL subscription for designs stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for Applications stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for Filters stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

There might be something wrong with the Meshery or Meshery Cloud

Probable Cause

Could be a network issue

Suggested Remediation

GraphQL subscription for ClusterResources Subscription stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Probable Cause

Table in the database might not exists

Suggested Remediation

GraphQL subscription for MeshModelSummary Subscription stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Probable Cause

Table in the database might not exists

Suggested Remediation

Probable Cause

Registry Manager might not exists

Suggested Remediation

Probable Cause

table in the database might be corrupted

Suggested Remediation

try resetting database from settings

Probable Cause

Suggested Remediation

GraphQL subscription for PerformanceProfiles stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for PerformanceResult stopped

Probable Cause

Could be a network issue

Suggested Remediation

Confirm that Meshery Server is reachable from your browser.

Database operation failed. Please ensure that the database isn't corrupted

Probable Cause

Could be a db issue

Suggested Remediation

Confirm that database connection is working as expected.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Provided ID is not a valid uuid.

Suggested Remediation

Hard delete and reinitialise the connection process.

Probable Cause

The machine context has become invalid.

Suggested Remediation

Retry the opereation or try archiving and reinitializing the connection

Probable Cause

Provided ID is not a valid uuid.

Suggested Remediation

Hard delete and reinitialise the connection process.

Probable Cause

Suggested Remediation

Unable to initializes client for interacting with an instance of Grafana server

Probable Cause

Invalid Grafana Endpoint or API-Key

Suggested Remediation

Update your Grafana URL and API-Key from the settings page in the UI

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Given resultID is nil

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed has json tags

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed is a valid json

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Invalid URL Invalid API-Key

Suggested Remediation

Probable Cause

Grafana endpoint might not be reachable from Meshery Grafana endpoint is incorrect

Suggested Remediation

Check if your Grafana endpoint is correct Connect to Grafana from the settings page in the UI

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Name field is either not present or is not valid

Probable Cause

Suggested Remediation

Name field is either not present or is not valid

Probable Cause

Suggested Remediation

Name field is either not present or is not valid

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Value of JWKs is nil

Probable Cause

Suggested Remediation

JWK not found for the given KeyID

Probable Cause

Suggested Remediation

Token is invalid, it has expired

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed is a valid json

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Network connectivity to Remote Provider may not be available. Session might have expired; token could be invalid.

Suggested Remediation

Verify that the Remote Provider is available. Ensure that you have an active session / valid token.

You dont have access to the capability

Probable Cause

Not logged in to the vaild remote Provider

Suggested Remediation

Connect to the vaild remote Provider Ask the Provider Adim for access

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

User doesn't have permission to save content.\nDatabase unreachable.\nDatabase locked or corrupt.\nContent unsupported.

Suggested Remediation

Retry fetching content\nRetry sigining in\nLogin with correct user account\nRetry after deleting '~/.meshery/config'.

Probable Cause

Sample content does not exist.\nContent file format not supported.\nUser doesn't have permission to read sample content.\nContent file corrupt.

Suggested Remediation

Try restarting Meshery.\nTry fetching content again.

Probable Cause

The content is not present at the specified url endpoint HTTP requests failed

Suggested Remediation

Make sure the content is available at the endpoints Make sure that Github is reachable and the http requests are not failing

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Unable to find meshery broker in the cluster

Probable Cause

Invalid Grafana Endpoint or API-Key

Suggested Remediation

Update your Grafana URL and API-Key from the settings page in the UI

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Make sure meshery broker is healthy

Probable Cause

Suggested Remediation

Make sure meshery broker is healthy

kubernetes context already persisted with provider

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Make sure the configurations are correct

Probable Cause

Unable to revoke token. Token appears to be a malformed base64 token.

Suggested Remediation

Try logging out (again) in order to fully close your session (and revoke the session token).

Probable Cause

Invalid session token. Token has revoked.

Suggested Remediation

Probable Cause

email address provided might not be valid insufficient permission

Suggested Remediation

Ensure that you are the owner of the design you are sharing Try again later Try using an alternate email address

Probable Cause

Remote provider server may be down or not accepting requests.

Suggested Remediation

Make sure remote provider server is healthy and accepting requests.

Probable Cause

Email address provided might not be valid Verify that you have sufficient permission to share the filter. You should be the owner of the filter

Suggested Remediation

Verify the spelling of the email address. Try using an alternate email address. Ensure that you are the owner of the filter you are sharing or have sharing permission assigned.

Probable Cause

Database could be down or not reachable Meshery Database handler is not accessible to perform operations

Suggested Remediation

Restart Meshery Server or Perform Hard Reset

Probable Cause

The Kubernetes API server is not reachable. Credentials are invalid.

Suggested Remediation

Probable Cause

Meshery Database handler is not accessible to perform operations

Suggested Remediation

Restart Meshery Server or Perform Hard Reset

Probable Cause

Connection was already deleted User might not have necessary privileges

Suggested Remediation

Try refresing, you might be seeing stale data on the dashboard Check if the user has necessary privileges

The record in the database does not exist.

Probable Cause

The record might have been deleted.

Suggested Remediation

Probable Cause

The credential object is not valid

Suggested Remediation

Ensure all the required fields are provided

Probable Cause

The connection object is not valid

Suggested Remediation

Ensure all the required fields are provided

Probable Cause

Prometheus endpoint might not be reachable from Meshery Prometheus endpoint is incorrect

Suggested Remediation

Check if your Prometheus endpoint are correct Connect to Prometheus from the settings page in the UI

Probable Cause

Grafana endpoint might not be reachable from Meshery Grafana endpoint is incorrect

Suggested Remediation

Check if your Grafana Endpoint is correct Connect to Grafana from the settings page in the UI

Probable Cause

Record already exist Database connection is not reachable

Suggested Remediation

Delete the record or try updating the record instead of recreating Rest the database connection

Probable Cause

component generation was canceled due to deletion or reload of K8s context Invalid kubeconfig Filters passed incorrectly in config Could not fetch API resources from Kubernetes server

Suggested Remediation

Probable Cause

Invalid kubeconfig Filters passed incorrectly in config Could not fetch API resources from Kubernetes server

Suggested Remediation

Make sure that the configuration filters passed are in accordance with output from /openapi/v2

Probable Cause

Ensure manifests are valid and also use the restricted YAML features like using only "strings" in the field names

Suggested Remediation

Ensure YAML is a valid Kubernetes Manifest

Probable Cause

Invalid Manifest Meshery doesn't identifies the Resource mentioned in the Manifest

Suggested Remediation

Check if all of the meshery adapters are running Check if Meshery has identified and registered Kubernetes components

Probable Cause

Invalid cytoscape body Service name is empty for one or more services _data does not have correct data

Suggested Remediation

Make sure cytoscape is valid Check if valid service name was passed in the request Make sure _data field has "settings" field

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

token is expired/revoked Remote Provider is not reachable or unavailable

Suggested Remediation

Try re-authenticating with the remote provider Verify remote provider for its reachability or availability.

Probable Cause

Requested resource is not reachable. Unable to instantiate TCP connection

Suggested Remediation

Ensure correct URL is specified Ensure network connectivity to the resource from your network

Probable Cause

Object has invalid yaml format

Suggested Remediation

Make sure to input a valid yaml object

Our server cannot provide live events streaming at the moment. This might be due to a technical issue with our system.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

callback URL might be empty

Suggested Remediation

Make sure the callback URL is not empty

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

The session data might be corrupted or not properly saved.

Suggested Remediation

Probable Cause

The session might not exist or could have been deleted.

Suggested Remediation

Check if the session data was correctly saved.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Make sure the URL is correct

Probable Cause

An error occurred while attempting to close response body reader.

Suggested Remediation

Ensure the response body reader is in a state that allows it to be closed.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Session might already been revoked Remote provider is not able to complete the request

Suggested Remediation

Close the tabs and open Meshery UI again. Optionally, try using a private/incognito browser window.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Possible causes include invalid Kubernetes context, missing configuration, or network issues.

Suggested Remediation

Verify the Kubernetes context configuration. Ensure the Kubernetes cluster is reachable and the configuration is correct.

Probable Cause

Possible causes include invalid Kubernetes context, missing or incorrect configuration, or network issues.

Suggested Remediation

Verify the Kubernetes context configuration. Ensure the Kubernetes cluster is reachable and the configuration is correct.

Probable Cause

Possible causes include invalid input data, database issues, or network problems.

Suggested Remediation

Verify the input data is correct. Ensure the database is reachable and properly configured.

Probable Cause

Possible causes include incorrect database file path, invalid database engine configuration, or insufficient permissions.

Suggested Remediation

Verify the database file path and ensure it is correct. Check the database engine configuration and ensure the application has the necessary permissions to access the database file.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to delete the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to create the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or resource not found.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to access the resource.

Probable Cause

Possible causes include invalid resource name or namespace, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource name and namespace are correct. Ensure you have the necessary permissions to delete the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource configuration, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource configuration and ensure it is correct. Ensure you have the necessary permissions to recreate the resource. Check network connectivity to the Kubernetes cluster.

Probable Cause

Possible causes include invalid resource configuration, insufficient permissions, or network issues.

Suggested Remediation

Verify the resource configuration and ensure it is correct. Ensure you have the necessary permissions to update the resource. Check network connectivity to the Kubernetes cluster.

Unable to find "token" cookie in the request.

Probable Cause

User is not authenticated with the selected Provider. Browser might be restricting use of cookies.

Suggested Remediation

Choose a Provider and login to establish an active session (receive a new token and cookie). Optionally, try using a private/incognito browser window. Verify that your browser settings allow cookies.

ActedUpon, Action, Category and Severity are required fields of an event

Probable Cause

Suggested Remediation

Ensure that ActedUpon, Action, Category and Severity are present in the event

Probable Cause

Given models may not be in accordance with Meshery's schema Internal(OS level) error while reading files

Suggested Remediation

Make sure the models being seeded are valid in accordance with Meshery's schema If it is an internal error, please try again after some time

Probable Cause

Entity definition might not be in accordance with schema Entity version might not be supported by Meshery

Suggested Remediation

See the registration logs (found at $HOME/.meshery/logs/registry/registry-logs.log) to find out which Entity failed to be imported with more specific error information.

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Component might not have been registered The component might not be supported by default, in the version of Meshery you are currently using.

Suggested Remediation

Ensure component definition is valid JSON/YAML. Import the model and try again.

Probable Cause

Remote provider server may be down or not accepting requests.

Suggested Remediation

Make sure remote provider server is healthy and accepting requests.

Probable Cause

Suggested Remediation

Export design in one of the supported format.

Unable to locate the compressed file(.tar.gz) inside the OCI image.

Probable Cause

The OCI image does not contain a ziped file.

Suggested Remediation

Verify that the OCI image contains a ziped file.

Probable Cause

The provided file type is wrong

Suggested Remediation

Verify the file type

Probable Cause

Unable to create OPA instance, policies will not be evaluated.

Suggested Remediation

Ensure relationships are registered

Probable Cause

Suggested Remediation

Check if the server is online and operational. Verify network connectivity and ensure there are no firewalls or DNS issues blocking the request. Confirm the API endpoint is correct and functional.

Top

meshery-adapter-library library

Severity	Error Name - Code	Discussion
	`ErrGetNameCode-1000`	search forum

Long Description

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Top

meshkit library

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrGetCrdNamesCode-1001`	Error getting crd names	search forum

Long Description

Probable Cause

Could not execute kubeopenapi-jsonschema correctly

Suggested Remediation

Make sure the binary is valid and correct Make sure the filter passed is correct

Probable Cause

Schemas Json could not be produced from given crd.

Suggested Remediation

Make sure the filter passed is correct

Probable Cause

Api version could not be parsed

Suggested Remediation

Make sure the filter passed is correct

Probable Cause

Api group could not be parsed

Suggested Remediation

Make sure the filter passed is correct

Probable Cause

Yaml could not be populated with the returned manifests

Suggested Remediation

Probable Cause

ItrFilter or ItrSpecFilter is either not passed or empty

Suggested Remediation

Pass the correct ItrFilter and ItrSpecFilter

Probable Cause

database name is empty

Suggested Remediation

Input a name for the database

Probable Cause

Database is unreachable

Suggested Remediation

Make sure your database is reachable

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Invalid database instance passed.

Suggested Remediation

Make sure the DB handler has a valid database instance.

Probable Cause

Manifest could be invalid

Suggested Remediation

Make sure manifest yaml is valid

Probable Cause

Network not reachable to the service

Suggested Remediation

Make sure the endpoint is reachable

Probable Cause

Chart could be invalid

Suggested Remediation

Make sure to apply valid chart

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Discovery resource is invalid or doesnt exist

Suggested Remediation

Makes sure the you input valid resource for discovery

Probable Cause

Informer is invalid or doesnt exist

Suggested Remediation

Makes sure the you input valid resource for the informer

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Kubernetes config is not accessible to meshery or not valid

Suggested Remediation

Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Invalid object format

Suggested Remediation

Make sure to input a valid JSON object

Probable Cause

Invalid object format

Suggested Remediation

Make sure to input a valid JSON object

Probable Cause

Invalid object format

Suggested Remediation

Make sure to input a valid JSON object

Probable Cause

Invalid object format

Suggested Remediation

Make sure to input a valid JSON object

Probable Cause

Invalid object format

Suggested Remediation

Make sure to input a valid JSON object

Probable Cause

Invalid object format

Suggested Remediation

Make sure to input a valid JSON object

Probable Cause

Invalid object format

Suggested Remediation

Make sure to input a valid JSON object

Probable Cause

Not a valid boolean

Suggested Remediation

Make sure it is a boolean

Probable Cause

Network protocol is incorrect

Suggested Remediation

Make sure to specify the right network protocol

Probable Cause

File doesnt exist in the location File name is incorrect

Suggested Remediation

Make sure to input the right file name and location

Probable Cause

File doesnt exist in the location File name is incorrect

Suggested Remediation

Make sure to input the right file name and location

Probable Cause

File doesnt exist in the location File name is incorrect

Suggested Remediation

Make sure to input the right file name and location

Probable Cause

Viper is crashing

Suggested Remediation

Make sure viper is configured properly

Probable Cause

In memory map is crashing

Suggested Remediation

Make sure map is configured properly

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Could not read the file while walking the repo

Probable Cause

Given file size is either 0 or exceeds the limit of 50 MB

Suggested Remediation

Probable Cause

Suggested Remediation

Top

Meshery Adapter for meshery-nginx-sm

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrEmptyConfigCode-1000`	Config is empty	search forum

Long Description

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Object is not a valid json object

Suggested Remediation

Make sure if the object passed is a valid json

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Kubernetes client is nil

Probable Cause

kubernetes client not initialized

Suggested Remediation

Reconnect the adaptor to Meshery server

Probable Cause

Suggested Remediation

Error occurred while parsing application component in the OAM request made by Meshery Server

Probable Cause

Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct

Suggested Remediation

Error occurred while parsing configuration in the request made by Meshery Server

Probable Cause

Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Trying to access a namespace which is not available

Suggested Remediation

Verify presence of namespace. Confirm Meshery ServiceAccount permissions

Top

Meshery Adapter for nsm

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrEmptyConfigCode-1000`	Config is empty	search forum

Long Description

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Top

Meshery Adapter for meshery-osm

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrInstallOSMCode-1000`	Error with osm operation	search forum

Long Description

Error occurred while installing osm mesh through osmctl

Probable Cause

Suggested Remediation

Probable Cause

The gzip might be corrupt

Suggested Remediation

Retry the operation

Error getting MeshSpecKey config from in-memory configuration

Probable Cause

Suggested Remediation

Reconnect the adaptor to the meshkit server

Probable Cause

Corrupted istioctl binary Command might be invalid

Suggested Remediation

Error occurred while download osm binary from its github release

Probable Cause

Checkout https://docs.github.com/en/rest/reference/repos#releases for more details

Suggested Remediation

Probable Cause

Corrupted osm release binary Invalid installation location

Suggested Remediation

Error occurred while trying to install a sample application using manifests

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reconnect your adapter to meshery server to refresh the kubeclient

Error occurred while applying custom manifest to the cluster

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reupload the kubconfig in the Meshery Server and reconnect the adapter

Error occurred while applying manifest to create a namespace

Probable Cause

Invalid kubeclient config Invalid manifest

Suggested Remediation

Reupload the kubeconfig in the Meshery Server and reconnect the adapter

Probable Cause

Corrupted binary Invalid operation

Suggested Remediation

Check if the adaptor is executing a deprecated command

Error occurred while injecting sidercar using osm(ctl) osm namespace add/remove \<name\>

Probable Cause

Corrupted binary Invalidoperation

Suggested Remediation

Check if the adaptor is executing a deprecated command

Istio adapter received an invalid operation from the meshey server

Probable Cause

The operation is not supported by the adapter Invalid operation name

Suggested Remediation

Check if the operation name is valid and supported by the adapter

Probable Cause

Suggested Remediation

Kubernetes client is nil

Probable Cause

kubernetes client not initialized

Suggested Remediation

Reconnect the adaptor to Meshery server

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while parsing application component in the OAM request made by Meshery server

Probable Cause

Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct

Suggested Remediation

Error occurred while parsing configuration in the request made by Meshery Server

Probable Cause

Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct

Suggested Remediation

Probable Cause

Latest version could not be found at the specified url

Suggested Remediation

Probable Cause

Trying to access a namespace which is not available

Suggested Remediation

Verify presence of namespace. Confirm Meshery ServiceAccount permissions

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Top

Meshery Adapter for meshery-traefik-mesh

Severity	Error Name - Code	Short Description	Discussion
Alert	`ErrApplyHelmChartCode-1012`	Error occurred while applying Helm Chart	search forum

Long Description

Probable Cause

Suggested Remediation

Kubernetes client is nil

Probable Cause

kubernetes client not initialized

Suggested Remediation

Reconnect the adapter to Meshery server

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Error occurred while parsing application component in the OAM request made by Meshery Server

Probable Cause

Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct

Suggested Remediation

Error occurred while parsing configuration in the request made by Meshery Server

Probable Cause

Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct

Suggested Remediation

Probable Cause

Latest version could not be found at the specified url

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Probable Cause

Suggested Remediation

Top

Error Code Reference

Error Code Reference

Error Codes and Troubleshooting

Error codes are combination of component type, component name, event moniker and numberic code

See Also

Error Code Categories by Component

Meshery Adapter for CILIUM

Meshery Adapter for meshery-consul

Meshery Adapter for meshery-istio

Meshery Adapter for meshery-kuma

Meshery Adapter for meshery-linkerd

Meshery Server

Meshery Server

meshery-adapter-library library

meshkit library

Meshery Adapter for meshery-nginx-sm

Meshery Adapter for nsm

Meshery Adapter for meshery-osm

Meshery Adapter for meshery-traefik-mesh