Error Code Reference

Error occurred while installing Cilium mesh through Cilium

The gzip might be corrupt

Retry the operation

Error getting MeshSpecKey config from in-memory configuration

Reconnect the adaptor to the meshkit server

Corrupted cilium binary Command might be invalid

Error occurred while download Cilium binary from its github release

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

Corrupted Cilium release binary Invalid installation location

Error occurred while trying to install a sample application using manifests

Invalid kubeclient config Invalid manifest

Reconnect your adapter to Meshery Server to refresh the kubeclient

Error occurred while applying custom manifest to the cluster

Invalid kubeclient config Invalid manifest

Upload the kubconfig in the Meshery Server and reconnect the adapter

Error occurred while applying manifest to create a namespace

Invalid kubeclient config Invalid manifest

Upload the kubeconfig in the Meshery Server and reconnect the adapter

Corrupted binary Invalid operation

Check if the adaptor is executing a deprecated command

Cilium adapter received an invalid operation from the meshey server

The operation is not supported by the adapter Invalid operation name

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

Kubernetes client is nil

kubernetes client not initialized

Reconnect the adaptor to Meshery server

Error occurred while prasing application component in the OAM request made

Invalid OAM component passed in OAM request

Check if your request has vaild OAM components

Error occurred while prasing component config in the OAM request made

Invalid OAM config passed in OAM request

Check if your request has vaild OAM config

Latest version could not be found at the specified url

Download might be corrupted.

Please retry operation.

Trying to access a namespace which is not available

Verify presence of namespace. Confirm Meshery ServiceAccount permissions

The gzip might be corrupt

Please retry operation.

File might be corrupt

Please retry operation.

Error occurred while download cilium tar from its release url

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

Latest version could not be found at the specified url

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

versions for cilium could not be fetched

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

make sure adapter is reachable

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

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

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

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

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

Chart could be invalid

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

Error getting MeshSpecKey config from in-memory configuration

API version or Kind passed is empty

Make sure API version and Kind are not empty

Could not marshall generated component to YAML

Unable to get the latest release info from the GithubAPI

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

Invalid release format

Error occurred while installing istio mesh through istioctl

File might be corrupt

/The gzip might be corrupt

Error getting MeshSpecKey config from in-memory configuration

Corrupted istioctl binary Command might be invalid

Error occurred while trying to install a sample application using manifests

Invalid kubeclient config Invalid manifest

Reconnect your adapter to meshery server to refresh the kubeclient

Error occurred while trying to install a sample application using manifests

Invalid kubeclient config Invalid manifest

Reconnect your adapter to meshery server to refresh the kubeclient

Error occurred while applying custom manifest to the cluster

Invalid kubeclient config Invalid manifest

Invalid profile passed

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

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

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

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

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

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

Kubernetes client is nil

kubernetes client not initialized

Reconnect the adaptor to Meshery server

Istio adapter received an invalid operation from the meshey server

The operation is not supported by the adapter Invalid operation name

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

Istio only supports Windows, Linux and Darwin

versions for istio could not be fetched

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

make sure adapter is reachable to github

Unable to get the latest release info from the GithubAPI

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

Invalid release format

Kuma adapter received an invalid operation from the meshey server

The operation is not supported by the adapter Invalid operation name

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

Error occurred while installing kuma mesh through kumactl

Error getting MeshSpecKey config from in-memory configuration

Reconnect the adapter to the Meshery Server

Error occurred while trying to install a sample application using manifests

Invalid kubeclient config Invalid manifest

Reconnect your adapter to Meshery Server to refresh the kubeclient

Error occurred while downloading`kumactl` and moving it to .meshery/bin]

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

Error occurred while download kuma binary from its release url

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

Error occurred while installing kuma mesh through kumactl

The gzip might be corrupt

Retry the operation

Error occurred in the process of untaring a compressed file

The compressed file might be corrupted

Clear the cache and retry the operation

Meshery adapter might not have write access

Error occurred while applying custom manifest to the cluster

Invalid kubeclient config Invalid manifest

Reupload the kubconfig in the Meshery Server and reconnect the adapter

Kubernetes client is nil

Kubernetes client not initialized

Reconnect the adapter to Meshery Server

Error occurred while applying Helm Chart

Invalid helm chart configuration

Latest version could not be found at the specified url

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

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

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

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

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

Trying to access a namespace which is not available

Verify presence of namespace. Confirm Meshery ServiceAccount permissions

Unable to get the latest release info from the GithubAPI

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

Invalid release format

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

Error occurred while trying to install a sample application using manifests

Invalid kubeclient config Invalid manifest

Reconnect your adapter to meshery server to refresh the kubeclient

Error occurred while applying custom manifest to the cluster

Invalid kubeclient config Invalid manifest

Make sure to apply a valid Kubernetes manifest

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

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

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

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

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

Kubernetes client is nil

Kubernetes client not initialized

Reconnect the Meshery Adapter to Meshery Server

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

Version passed is invalid

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

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

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

Make sure the cluster is reachable

versions for linkerd could not be fetched

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

make sure adapter is reachable to github

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

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

Unable to create UUID instance:

Error registering local OAM traits:

Error registering local OAM workloads:

Unable to retrieve the user's home directory:

Unable to create the directory for storing user data at:

Unable to create a new MapPreferencePersister instance:

Unable to auto migrate to database:

is invalid url skipping provider

ListenAndServe Error:

Error cleaning up local provider:

Error closing database instance:

could not migrate tables into the database

make sure the database instance passed is not nil

could not migrate tables into the database

make sure the database instance passed is not nil

Kubernetes config is not initialized with Meshery

Kubernetes config is not accessible to Meshery or not valid

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

Kubernetes config is not accessible to Meshery or not valid

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

User token might be invalid db might be corrupted

Relogin to Meshery

Cannot find valid grafana endpoint in user pref

Grafana endpoint might not be reachable from Meshery

Setup your Grafana Endpoint via the settings dashboard

Cannot find valid Prometheus endpoint in user pref

Prometheus endpoint might not be reachable from Meshery

Setup your Prometheus Endpoint via the settings dashboard

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

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

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

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

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

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

unable to get static board

No boards could be available in grafana

Request body is empty or faulty

Check if the request is sent with proper values

Failed due to invalid value of :

please provide a valid value for :

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

Ensure Meshery UI is able to reach the Meshery server

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

Ensure Meshery UI is able to reach the Meshery server

Meshery Cloud is not functional or reachable

Make sure Meshery cloud is up and reachable

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

Make sure the plugin is compatible with Meshery server

Plugin is not available in the location

Make sure the plugin is compatible with Meshery server

plugin does not match with Meshery version

Make sure the plugin is compatible with Meshery server

The data provided could be invalid

Make sure to enter valid parameters in the form

Query parameter is not a part of the request

Make sure to pass the query paramater in the request

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

Make sure to provide the correct identifier for the result

The performance spec format is invalid

Make sure to provide the correct spec

SMI results did not get persisted Result identifier is invalid

Make sure to provide the correct identifier for the result

The kubeconfig file does not exist in the location.

Make sure to upload the correct kubeconfig file.

The kubeconfig file is empty or not valid.

Make sure to upload the correct kubeconfig file.

The kubeconfig file is empty or not valid

Make sure to upload the correct kubeconfig file

The file does not exist in the location.

Make sure to upload the correct file.

Kubernetes might not be reachable from Meshery.

Make sure Meshery has connectivity to Kubernetes.

meshLocationURL is empty to add an adapter

meshLocationURL cannot be empty to add an adapter

please provide the meshLocationURL

Adapter operation invalid

Make sure adapter is running and reachable by Meshery Server.

unable to find a valid adapter for the given adapter URL

Given adapter URL is not valid

Please provide a valid Adapter URL

Adapter operation invalid

Make sure adapter is reachable and running

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

Adapter could not be pinged

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

Adapter operation invalid

Make sure adapter is reachable and running

Unable to retrieve the requested data.

Make sure adapter is reachable and running.

uploaded application source content might be converted incorrect source type selected

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

Object is not a valid json object

Make sure if the object passed is a valid json

User token could be expired

Re-initiate login

Provider Database could be down or not reachable

Make sure provider is up and reachable

Provider Database could be down or not reachable

Make sure provider is up and reachable

please provide a valid value for gen (load generator)

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

Make sure the plugin is compatible with Meshery server.

Yaml provided is not valid

Make sure the yaml is valid and has the right parameters

The format of the duration passed could be incorrect

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

Load test endpoint might be not reachable.

Make sure load test endpoint is reachable by Meshery Server.

Kubernetes might not be reachable from Meshery.

Make sure Meshery has connectivity to Kubernetes.

Meshery crashed.

Restart Meshery.

Load test name empty or not valid.

Provide a name for the test.

URL for load test could be invalid.

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

User session could be expired.

Re-initiate login.

Check Kubernetes

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

Workload Definition is invalid or unable to process

Check Workload Definition

Trait Definition is invalid or unable to process

Check Trait Definition

Trait Definition is invalid or unable to process

Check Trait Definition

Trait Definition is invalid or unable to process

Check Trait Definition

Trait Definition is invalid or unable to process

Check Trait Definition

Trait Definition is invalid or unable to process

Check Trait Definition

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.

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

Insufficient permission Insufficient storage

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

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

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

Invalid data passed Unable to connect with provider

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

Cannot get the filter with the given Filter ID

Check if the given Filter ID is correct

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

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

Cannot save the Filter due to wrong path or URL

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

Failed to retrieve the list of all the Filters

Failed to delete Filter with the given ID

Check if the Filter ID is correct

Cannot save the design due to an invalid path or URL

Verify that you have an active user session. Try logging and in again. Confirm that you have sufficient permissions to save the design. Try reducing the size of the design file by removing the number of images, using alternative image formats or removing other non-critical components from the design. See https://docs.layer5.io/kanvas/advanced/performance/.

Cannot save the Application due to wrong path or URL.

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

Cannot get the design with the given design ID

Check if the given design ID is correct

Failed to delete design with the given ID

Check if the design ID is correct

Failed to retrieve the list of all the designs

Cannot save the design due to wrong path or URL

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'.

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

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

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

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.

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

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

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

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

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

Ensure you have required permissions or retry after sometime.

Failed to clone design with the given ID

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

Failed to clone Filter with the given ID

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

Make sure the payload is valid

Failed to publish catalog design

Check if the design ID is correct and you are admin

Failed to publish catalog filter

Check if the filter ID is correct and you are admin

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

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

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

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

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

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

Insufficient permission Insufficient storage

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

Remote provider might be not reachable

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

might be due to insufficient permissions file was deleted manually

please delete the file if present, path:

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

Try restarting Meshery server

Invalid profile ID

Check if the profile ID is correct

Load test endpoint could be not reachable

Make sure load test endpoint is reachable

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

Refresh your browser

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

Check the owner of the application.

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

Check the request URL and try again.

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

Verify event filter settings Reset database.

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

Verify event filter settings Reset database.

Unsupported event status for your current version of Meshery Server.

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.

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

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

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

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. Visit Settings and reset the Meshery database.

MeshSync might not be reachable from Meshery

Make sure Meshery has connectivity to MeshSync Try restarting Meshery server

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

Ensure you have required permissions or retry after sometime.

Unable to retrieve the connections

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

Insufficient permissions to write into file file might be corrupted

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

unable to read source directory source directory is corrupted

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

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

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

unable to read from io.Reader

check if the io.Reader is valid

unable to uncompress OCI artifact OCI artifact may be corrupted

check if the OCI artifact is valid and not corrupted

unable to walk local directory local directory may be corrupted

check if the local directory is valid and not corrupted

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

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

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

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

unable to marshal design into YAML design may be corrupted

check if the design is valid and not corrupted

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

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

provided id is not a valid uuid

provide a valid uuid

Kubernetes config is not accessible to meshery or not valid

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

Kubernetes config is not accessible to meshery or not valid

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

Kubernetes config is not accessible to meshery or not valid

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

Kubernetes API server might not be reachable from the Meshery server

Make sure kubernetes API server is reachable from meshery server

Kubernetes API server might not be reachable from the Meshery server

Make sure kubernetes API server is reachable from meshery server

Kubernetes API server might not be reachable from the Meshery server

Make sure kubernetes API server is reachable from meshery server

Kubernetes API server might not be reachable from the Meshery server

Make sure kubernetes API server is reachable from meshery server

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

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

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

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

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

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

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

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

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

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

Possible issues with Kubernetes cluster configuration or network connectivity.

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

Possible issues with Kubernetes cluster configuration or network connectivity.

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

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

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

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

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

Your platform is not supported for deploying Meshery Adapters

Consider using a supported platform for deploying Meshery Adapters

Current platform is not supported for undeploying Meshery Adapters

Consider using a supported platform for undeploying Meshery Adapters

Kubernetes config is not initialized with Meshery

Kubernetes config is not accessible to Meshery or not valid

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

Meshery Database is crashed or not reachable

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

Invalid Query performed in Meshery Database

GraphQL subscription for MeshSync stopped

Could be a network issue

Check if meshery server is reachable from the browser

Kubernetes config is not initialized with Meshery 1

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

Could be a network issue Meshery Broker could have crashed

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

Could be a network issue Meshery Broker could have crashed

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

Meshery Database is crashed or not reachable

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

Kubernetes cluster might not be connected Leftover resources from partial install

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

Meshery controller handlers may not be available

Make sure the controllers are deployed and their handlers are configured

Meshery controller handlers may not be available

Make sure the controllers are deployed and their handlers are configured

Kubernetes config is not initialized with Meshery 2

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

Meshery Database is crashed or not reachable

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

Unable to read MeshSync data to the Meshery Database

Meshery Database is crashed or not reachable

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

The Graphql query requested is invalid

Check the query parameters and syntax of the query being run

Kubernetes config is not initialized with Meshery

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

GraphQL subscription for MeshSync stopped

Could be a network issue

Check if meshery server is reachable from the browser

GraphQL subscription for Operator stopped

Could be a network issue

Check if meshery server is reachable from the browser

GraphQL subscription for Addons stopped

Could be a network issue

Check if meshery server is reachable from the browser

GraphQL subscription for Control Plane stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

Kubernetes config is not initialized with Meshery 1

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

Could be a network issue Meshery Broker could have crashed

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

Meshery Operator is not running in your cluster or is crashing

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

Could be a network issue

Check if meshery server is reachable from the browser

Meshery Broker is not connected to Meshery Server

Meshery Broker is crashed or not reachable

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

The table in the database might not exist

There might be something wrong with the Meshery or Meshery Cloud

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

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

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

Meshery is not able to get the current kubernetes context

Meshery is crashed or not reachable

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

GraphQL subscription for designs stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for Applications stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for Filters stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

There might be something wrong with the Meshery or Meshery Cloud

Could be a network issue

GraphQL subscription for ClusterResources Subscription stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

Table in the database might not exists

GraphQL subscription for MeshModelSummary Subscription stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

Table in the database might not exists

Registry Manager might not exists

table in the database might be corrupted

try resetting database from settings

GraphQL subscription for PerformanceProfiles stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

GraphQL subscription for PerformanceResult stopped

Could be a network issue

Confirm that Meshery Server is reachable from your browser.

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

Could be a db issue

Confirm that database connection is working as expected.

Provided ID is not a valid uuid.

Hard delete and reinitialise the connection process.

The machine context has become invalid.

Retry the opereation or try archiving and reinitializing the connection

Provided ID is not a valid uuid.

Hard delete and reinitialise the connection process.

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

Invalid Grafana Endpoint or API-Key

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

Given resultID is nil

Object is not a valid json object

Make sure if the object passed has json tags

Object is not a valid json object

Make sure if the object passed is a valid json

Invalid URL Invalid API-Key

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

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

Name field is either not present or is not valid

Name field is either not present or is not valid

Name field is either not present or is not valid

Value of JWKs is nil

JWK not found for the given KeyID

Token is invalid, it has expired

JWTs are encoded and signed, ensuring the integrity and authenticity of the claims they contain.

Object is not a valid json object

Make sure if the object passed is a valid json

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

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

You dont have access to the capability

Not logged in to the vaild remote Provider

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

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

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

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

Try restarting Meshery.\nTry fetching content again.

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

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

Unable to find meshery broker in the cluster

Invalid Grafana Endpoint or API-Key

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

Make sure meshery broker is healthy

Make sure meshery broker is healthy

kubernetes context already persisted with provider

Make sure the configurations are correct

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

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

Invalid session token. Token has revoked.

Login again to establish a new session with valid token.

email address provided might not be valid insufficient permission

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

Remote provider server may be down or not accepting requests.

Make sure remote provider server is healthy and accepting requests.

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

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.

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

Restart Meshery Server or Perform Hard Reset

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

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'.

Meshery Database handler is not accessible to perform operations

Restart Meshery Server or Perform Hard Reset

Connection was already deleted User might not have necessary privileges

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.

The record might have been deleted.

The credential object is not valid

Ensure all the required fields are provided

The connection object is not valid

Ensure all the required fields are provided

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

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

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

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

Record already exist Database connection is not reachable

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

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

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

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

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

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

Ensure YAML is a valid Kubernetes Manifest

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

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

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

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

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

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

Requested resource is not reachable. Unable to instantiate TCP connection

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

Object has invalid yaml format

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.

callback URL might be empty

Make sure the callback URL is not empty

The session data might be corrupted or not properly saved.

The session might not exist or could have been deleted.

Check if the session data was correctly saved.

Make sure the URL is correct

An error occurred while attempting to close response body reader.

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

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

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

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

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

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

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

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

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

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

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.

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

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.

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

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.

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

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

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

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.

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

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.

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

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.

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

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

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

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

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

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

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.

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

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

Remote provider server may be down or not accepting requests.

Make sure remote provider server is healthy and accepting requests.

Export design in one of the supported format.

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

The OCI image does not contain a ziped file.

Verify that the OCI image contains a ziped file.

The provided file type is wrong

Verify the file type

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

Ensure relationships are registered

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.

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.

not deployed operator issue with connection to broker

check that operator is deployed check that server can establish connection to broker

Fail to resync resources for the machine

Check if machine supports resource resync

Fail to resync resources for the kubernetes machine

Check if machine context is assign to machine Check if machine context contains a reference to MesheryControllersHelper

Fail to perform connect action for the kubernetes machine

Check if token is passed machine from golang context correctly Check if there is connection data stored in database for this kubernetes machine

Invalid design file

Check your design URL/file path

Invalid design source type due to wrong type/passing

design source type (-s) is invalid or not passed.

Ensure you pass a valid source type. \nAllowed source types: %s

Unable to onboard design due to empty path

File path or design name not provided.

Provide a file path/design name. \n\n%v

Unable to offboard design due to empty path

File path or design name not provided.

Provide a file path/design name. \n\n%v

Wrong use of command flags

-a/all flag is being used while an design is specified

-a/-all cannot be used when [design name|id] is specified

No manifest file path detected

Manifest path not provided

Provide the path to the design manifest. \n\n%v

Loading the Invalid MeshConfig data caused error

Make sure that your 'config.yaml' file in your '.meshery' is valid

Unable to Update config file

Ensure that you have the correct context in your meshconfig at `$HOME/.meshery/config.yaml`.

Error processing config

Unable to create config file