Skip to content
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
    • Kong Konnect
    • Kong Mesh
    • Plugin Hub
    • decK
    • Kubernetes Ingress Controller
    • Insomnia
    • Kuma

    • Docs contribution guidelines
  • Plugin Hub
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kubernetes Ingress Controller
  • Insomnia
  • Kuma

  • Docs contribution guidelines
    • Overview of Konnect
    • Architecture
    • Network Resiliency and Availability
    • Port and Network Requirements
    • Compatibility
    • Stages of Software Availability
    • Release Notes
      • Control Plane Upgrades FAQ
      • Supported Installation Options
    • Overview
    • Access a Konnect Account
    • Set up a Runtime
    • Configure a Service
    • Implement and Test the Service
      • Publish and Consume Services
      • Register Applications
    • Import Kong Gateway Entities into Konnect
    • Overview
      • Overview
      • Dashboard
      • Manage Runtime Groups with UI
      • Manage Runtime Groups with decK
      • Installation Options
      • Install with Docker
      • Install on Kubernetes
      • Install on Linux
      • Install on AWS
      • Install on Azure
      • Upgrade a Runtime Instance to a New Version
      • Renew Certificates
      • Runtime Parameter Reference
    • Create Consumer Groups
      • Overview
      • Set Up and Use a Vault in Konnect
    • Kong Gateway Configuration in Konnect
    • Plugin Ordering Reference
    • Troubleshoot
    • Overview
    • Manage Service Documentation
      • Overview
      • Configure a Plugin on a Service
      • Configure a Plugin on a Route
    • Overview
    • Access the Dev Portal
    • Sign Up for a Dev Portal Account
      • Manage Developer Access
      • Manage Application Registration Requests
      • Manage Application Connections
      • Auto Approve Dev and App Registrations
      • Azure OIDC
      • Application Overview
      • Enable and Disable App Registration
        • Overview
        • Okta
        • Curity
        • Auth0
      • Create, Edit, and Delete an Application
      • Register an Application with a Service
      • Generate Credentials for an Application
    • Customize Dev Portal
    • Troubleshoot
    • Introduction to Analytics
    • Analyze Services and Routes
    • Reports Use Cases
    • Reports Reference
    • Troubleshoot
      • Manage a Konnect Account or Plan
      • Change to a Different Plan
      • Manage Payment Methods and Invoices
      • Overview
        • Overview
        • Manage Teams
        • Teams Reference
        • Roles Reference
      • Manage Users
      • Manage System Accounts
      • Set up SSO with OIDC
      • Set up SSO with Okta
      • Login Sessions Reference
    • Account and Org Deactivation
    • Troubleshoot
    • Overview
      • API Documentation
      • Identity Integration Guide
      • API Documentation
      • API Documentation
      • Portal RBAC Guide
      • Overview
      • Nodes
      • Data Plane Certificiates
        • Services
        • Routes
        • Consumers
        • Plugins
        • Upstreams
        • Certificates
        • CA Certificates
        • SNIs
        • Targets
        • Vaults
      • API Spec
      • Filtering
    • Labels

github-edit-pageEdit this page

report-issueReport an issue

enterprise-switcher-iconSwitch to OSS

On this page
  • Out of sync runtime instance
  • Missing functionality
  • Version compatibility
Kong Konnect
  • Home
  • Kong Konnect
  • Runtime Manager
  • Troubleshoot Runtime Instances

Troubleshoot Runtime Instances

Out of sync runtime instance

Occasionally, a Kong Gateway runtime instance might get out of sync with the Konnect control plane. If this happens, you will see the status Out of sync on the Runtime Instances page, meaning the control plane can’t communicate with the instance.

Troubleshoot the issue using the following methods:

  • Ensure the runtime instance is running. If it’s not running, start it; if it is running, restart it.

    Check the sync status in the Runtime Manager.

  • Check the logs of the runtime that’s appearing as Out of sync. The default directory for Kong Gateway logs is /usr/local/kong/logs.

    If you find any of the following errors:

    • Runtime instance failed to connect to the control plane.
    • Runtime instance failed to ping the control plane.
    • Runtime instance failed to receive a ping response from the control plane.

    You may have an issue on the host network where the instance resides. Diagnose and resolve the issue, then restart the instance and check the sync status in the Runtime Manager.

  • If the logs show a license issue, contact Kong Support.

If you are unable to resolve sync issues using the above methods, contact Kong Support.

Missing functionality

If a Konnect feature isn’t working on your runtime instance, the version may be out of date.

Verify that your instance versions are up to date:

  1. Open runtimes icon Runtime Manager, then open your runtime group.

  2. Click + Add runtime instance and check the Kong Gateway version in the code block. This is the version that the Konnect control plane is running.

  3. Return to the runtime instances page.

  4. Check the runtime instance versions in the table. If you see an instance running an older version of Kong Gateway, your runtime instance may need upgrading.

If your version is up to date but the feature still isn’t working, contact Kong Support.

Version compatibility

We recommend running one major version (2.x or 3.x) of a runtime instance per runtime group, unless you are in the middle of version upgrades to the data plane.

If you mix major runtime instance versions, the control plane will support the least common subset of configurations across all the versions connected to the Konnect control plane. For example, if you are running 2.8.1.3 on one runtime instance and 3.0.0.0 on another, the control plane will only push configurations that can be used by the 2.8.1.3 runtime instance.

If you experience compatibility errors, upgrade your data planes to match the version of the highest-versioned runtime instance in your runtime group.

Possible compatibility errors:

Error code Severity Description Resolution References

D100

error

Plugin jq is not available in Kong Gateway versions < 2.6.0.0.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

jq plugin

D101

error

For the canary plugin, one or more of the following config fields are set: hash_header but Kong Gateway versions < 2.6.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

Canary plugin

D102

error

For the canary plugin, config.hash field has been set to header. This is not supported in Kong Gateway versions < 2.6.0.0. The plugin configuration has been changed to config.hash=consumer in the data-plane.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

Canary plugin

D103

error

For the kafka-log plugin, one or more of the following config fields are set: authentication, keepalive_enabled, security but Kong Gateway versions < 2.6.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

Kafka Log plugin

D104

error

For the kafka-upstream plugin, one or more of the following config fields are set: authentication, keepalive_enabled, security but Kong Gateway versions < 2.6.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

Kafka Upstream plugin

D105

error

For the rate-limiting-advanced plugin, either config.strategy is set to local or config.identifier is set to path or both. These settings are not supported in Kong Gateway versions < 2.6.0.0. In the data-plane, the plugin configuration has one or more of the following changes: (a) config.strategy has been updated to redis, (b) config.sync_rate has been updated to 1, (c) config.identifier has been updated to path.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

Rate Limiting Advanced plugin

D106

error

For the openid-connect plugin, one or more of the following unsupported config fields or values for a config field are in use: by_username_ignore_case, disable_session, downstream_introspection_jwt_header, downstream_user_info_jwt_header, introspection_accept, introspection_check_active, upstream_introspection_jwt_header, upstream_user_info_jwt_header, userinfo_accept, userinfo_headers_client, userinfo_headers_names, userinfo_headers_values, userinfo_query_args_client, userinfo_query_args_names, userinfo_query_args_values, auth_methods array field with value userinfo, ignore_signature array field with value introspection, ignore_signature array field with value userinfo, login_methods array field with value userinfo, token_headers_grants array field with value refresh_token.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

OpenID Connect plugin

D107

error

For the rate-limiting-advanced plugin, one or more of the following config fields are set: path but Kong Gateway versions < 2.6.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

Rate Limiting Advanced plugin

D108

error

For the forward-proxy plugin, one or more of the following config fields are set: auth_username, auth_password but Kong Gateway versions < 2.7.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.7.0.0 or above.

Forward Proxy plugin

D109

error

For the mocking plugin, one or more of the following config fields are set: random_examples but Kong Gateway versions < 2.7.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.7.0.0 or above.

Mocking plugin

D110

error

For the rate-limiting-advanced plugin, one or more of the following config fields are set: enforce_consumer_groups, consumer_groups but Kong Gateway versions < 2.7.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.7.0.0 or above.

Rate Limiting Advanced plugin

D111

error

For the rate-limiting-advanced plugin, one or more of the following config fields are set: redis.username, redis.sentinel_username but Kong Gateway versions < 2.8.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Rate Limiting Advanced plugin

D112

error

For the proxy-cache-advanced plugin, one or more of the following config fields are set: redis.username, redis.sentinel_username but Kong Gateway versions < 2.8.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Proxy Cache Advanced plugin

D113

error

For the canary plugin, one or more of the following config fields are set: canary_by_header_name but Kong Gateway versions < 2.8.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Canary plugin

D114

error

For the forward-proxy plugin, one or more of the following config fields are set: https_proxy_host, https_proxy_port but Kong Gateway versions < 2.8.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Forward Proxy plugin

D115

warning

N/A

N/A

D116

error

For the openid-connect plugin, one or more of the following config fields are set: session_redis_username, resolve_distributed_claims but Kong Gateway versions < 2.8.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

OpenID Connect plugin

D118

error

For the kafka-log plugin, one or more of the following config fields are set: cluster_name but Kong Gateway versions < 2.8.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Kafka Log plugin

D119

error

For the kafka-upstream plugin, one or more of the following config fields are set: cluster_name but Kong Gateway versions < 2.8.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Kafka Upstream plugin

D120

error

For the kafka-log plugin config.authentication.mechanism is set to SCRAM-SHA-512. This is not supported in Kong Gateway versions < 2.8.1.1. The value for the field has been changed to SCRAM-SHA-256 in the data-plane.

Please upgrade Kong Gateway to version 2.8.1.1 or above.

Kafka Log plugin

D121

error

For the kafka-upstream plugin config.authentication.mechanism is set to SCRAM-SHA-512. This is not supported in Kong Gateway versions < 2.8.1.1. The value for the field has been changed to SCRAM-SHA-256 in the data-plane.

Please upgrade Kong Gateway to version 2.8.1.1 or above.

Kafka Upstream plugin

D122

error

For the mtls-auth plugin, one or more of the following config fields are set: http_proxy_host, http_proxy_port, https_proxy_host, https_proxy_port but Kong Gateway versions < 2.8.1.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8.1.1 or above.

mTLS Authentication plugin

D123

error

It seems you are using Konnect Developer Portal with Kong Gateway. For the Developer Portal’s application registration feature to work correctly, konnect-application-auth plugin is required but this plugin is not available on Kong Gateway versions < 3.0. The feature is not working as intended and can cause severe security issues including authentication and authorization not being enforced in the Gateway.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Not applicable

D124

error

For the ldap-auth-advanced plugin, one or more of the following config fields are set: group_required but Kong Gateway versions < 3.0.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

LDAP Authentication Advanced plugin

D125

error

For the opa plugin, one or more of the following config fields are set: include_body_in_opa_input, include_parsed_json_body_in_opa_input, ssl_verify but Kong Gateway versions < 3.0.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

OPA plugin

D126

error

For the statsd-advanced plugin, one or more of the following config fields are set: consumer_identifier_default, service_identifier_default, workspace_identifier_default but Kong Gateway versions < 3.0.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

StatsD Advanced plugin

D127

error

For the rate-limiting-advanced plugin, config.sync_rate was set to a float value less than 1.0. This configuration is not supported in Kong Gateway versions < 2.6.0.0. The configuration has been changed with config.sync_rate set to value of 1.

Please upgrade Kong Gateway to version 2.6.0.0 or above.

Rate Limiting Advanced plugin

D128

error

For the openid-connect plugin, config.anonymous field has been set to a string value that is not a UUID, possibly to reference a consumer via username. This feature is not supported in Kong Gateway versions < 3.0. The plugin configuration has been changed to remove the config.anonymous field.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

OpenID Connect plugin

D129

error

Konnect cloud’s Developer Portal’s application registration workflow requires features introduced in Kong Gateway 3.0. Some features of the Developer Portal are not working as intended.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Application Registration plugin

D130

error

For the Plugin entity, the ordering field has been set but Kong Gateway versions < 3.0 do not support plugin re-ordering. The ordering field has been removed from the configuration; plugins are executing based on the priorities coded into plugins.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Plugin entity

D131

error

For the service entity, protocol field has been set to ws or wss. This is not supported in Kong Gateway versions < 3.0.0.0. The service and all associated route(s) and plugin(s) have been removed in the data-plane.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Service entity

D132

error

For the route entity or associated service, protocol field has been set to ws or wss. This is not supported in Kong Gateway versions < 3.0.0.0. The route and all associated plugin(s) have been removed in the data-plane.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Route entity

D133

error

For the plugin entity, protocol field has been set to ws or wss. This is not supported in Kong Gateway versions < 3.0.0.0. The plugin has been removed in the data-plane.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Plugin entity

D134

error

Plugin websocket-validator is not available in Kong Gateway versions < 3.0.0.0.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Websocket Validator plugin

D135

error

Plugin websocket-size-limit is not available in Kong Gateway versions < 3.0.0.0.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

Websocket Size Limit plugin

D136

error

Plugin tls-handshake-modifier is not available in Kong Gateway versions < 3.0.0.0.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

TLS Handshake Modifier plugin

D137

error

Plugin tls-metadata-headers is not available in Kong Gateway versions < 3.0.0.0.

Please upgrade Kong Gateway to version 3.0.0.0 or above.

TLS Metadata Headers plugin

D138

error

For the forward-proxy plugin, one or more of the following config fields are set: x_headers but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

Forward Proxy plugin

D139

error

For the mtls-auth plugin, one or more of the following config fields are set: send_ca_dn but Kong Gateway versions < 3.1.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

mTLS Authentication plugin

D140

error

For the route-transformer-advanced plugin config.escape_path is set. This is not supported in Kong Gateway versions < 2.8.2.0 and in Kong Gateway versions > 3.0.x. Plugin features that rely on this field are not working as intended.

Please upgrade Kong Gateway to version 2.8.2.0 or above, excluding versions 3.0.0.x and 3.0.1.x

Route Transformer Advanced plugin

D141

error

Plugin app-dynamics is not available in Kong Gateway versions < 3.1.0.0.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

App Dynamics plugin

D142

error

Plugin saml is not available in Kong Gateway versions < 3.1.0.0.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

SAML plugin

D143

error

Plugin jwe-decrypt is not available in Kong Gateway versions < 3.1.0.0.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

Kong JWE Decrypt plugin

D144

error

Plugin xml-threat-protection is not available in Kong Gateway versions < 3.1.0.0.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

XML Threat Protection plugin

D145

error

For the rate-limiting-advanced plugin, one or more of the following config fields are set: error_code, error_message, disable_penalty but Kong Gateway versions < 3.1.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

Rate Limiting Advanced plugin

D146

error

For the vaults entity, one or more of the following schema fields are set: auth_method, kube_role, kube_api_token_file but Kong Gateway versions < 3.1.0.0 do not support these fields.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

Vaults entity

D147

error

The consumer_group entity is being used, but Kong Gateway versions < 2.8.0.0 do not support this entity.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Consumer Groups entity

D148

error

As part of the Consumer Groups feature, some Consumers have been set to belong to one or more of such groups but Kong Gateway versions < 2.8 do not support Consumer Groups. The group membership for consumers has been removed from the configuration.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Consumer Groups entity

D149

error

As part of the Consumer Groups feature, some Rate Limiting Advanced overrides have been to one of such groups but Kong Gateway versions < 2.8 do not support Consumer Groups. These overrides have been removed from the configuration; Rate Limiting policies are governed by global configuration.

Please upgrade Kong Gateway to version 2.8.0.0 or above.

Consumer Groups entity

D150

error

For the mocking plugin, one or more of the following config fields are set: included_status_codes, random_status_code but Kong Gateway versions < 3.1.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

Mocking plugin

D151

error

For the oauth2-introspection plugin, config.anonymous field has been set to a string value that is not a UUID, possibly to reference a consumer via username. This feature is not supported in Kong Gateway versions < 3.1. The plugin configuration has been changed to remove the config.anonymous field.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

OAuth 2.0 Introspection plugin

D152

error

For the mtls-auth plugin, config.anonymous field has been set to a string value that is not a UUID, possibly to reference a consumer via username. This feature is not supported in Kong Gateway versions < 3.1. The plugin configuration has been changed to remove the config.anonymous field.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

mTLS Authentication plugin

D153

error

For the ldap-auth-advanced plugin, config.anonymous field has been set to a string value that is not a UUID, possibly to reference a consumer via username. This feature is not supported in Kong Gateway versions < 3.1. The plugin configuration has been changed to remove the config.anonymous field.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

LDAP Authentication Advanced plugin

D154

error

For the request-transformer-advanced plugin, one or more of the following config fields are set: dots_in_keys, replace.json_types, append.json_types, add.json_types but Kong Gateway versions < 3.1.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

Request Transformer Advanced plugin

D156

warning

For the openid-connect plugin, config.authorization_cookie_same_site has been set to Default. This is not supported in Kong Gateway versions < 3.2.0.0. The plugin configuration has been changed to config.authorization_cookie_same_site=Lax in the data-plane (default value).

Please upgrade Kong Gateway to version 3.2.0.0 or above.

OpenID Connect plugin

D157

warning

For the openid-connect plugin, config.session_cookie_same_site has been set to Default. This is not supported in Kong Gateway versions < 3.2.0.0. The plugin configuration has been changed to the config.session_cookie_same_site=Lax in the data-plane (default value).

Please upgrade Kong Gateway to version 3.2.0.0 or above.

OpenID Connect plugin

D158

warning

For the openid-connect plugin, one or more config fields are set but Kong Gateway versions < 3.2.0.0 do not support these fields. The plugin configuration has been updated and these fields have been mapped to their old names: session_cookie_http_only => session_cookie_httponly, session_memcached_prefix => session_memcache_prefix, session_redis_cluster_max_redirections => session_redis_cluster_maxredirections, authorization_cookie_same_site => authorization_cookie_samesite, authorization_cookie_http_only => authorization_cookie_httponly, session_rolling_timeout => session_cookie_lifetime, session_idling_timeout => session_cookie_idletime, session_cookie_same_site => session_cookie_samesite, session_memcached_socket => session_memcache_socket, session_memcached_host => session_memcache_host, session_memcached_port => session_memcache_port, authorization_rolling_timeout => authorization_cookie_lifetime

Please upgrade Kong Gateway to version 3.2.0.0 or above.

OpenID Connect plugin

D159

error

For the openid-connect plugin, one or more of the following config fields are set: session_audience, session_remember, session_remember_cookie_name, session_remember_rolling_timeout, session_remember_absolute_timeout, session_absolute_timeout, session_store_metadata, session_response_headers, session_request_headers, session_enforce_same_subject, session_hash_subject, session_hash_storage_key but Kong Gateway versions < 3.2.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.2.0.0 or above.

OpenID Connect plugin

D160

error

For the openid-connect plugin, one or more of the following config fields are set: session_cookie_renew, session_cookie_maxsize, session_strategy, session_compressor but Kong Gateway versions >= 3.2.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please remove these fields from the plugin configuration.

OpenID Connect plugin

D161

warning

For the openid-connect plugin, config.session_storage field has been set to memcached. This is not supported in Kong Gateway versions < 3.2.0.0. The plugin configuration has been changed to config.session_storage=memcache in the data-plane.

Please upgrade Kong Gateway to version 3.2.0.0 or above.

OpenID Connect plugin

D162

error

For the saml plugin, one or more of the following config fields are set: session_audience, session_remember, session_remember_cookie_name, session_remember_rolling_timeout, session_remember_absolute_timeout, session_store_metadata, session_response_headers, session_request_headers, session_enforce_same_subject, session_hash_subject, session_hash_storage_key but Kong Gateway versions < 3.2.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.2.0.0 or above.

SAML plugin

D163

warning

For the saml plugin, one or more config fields are set but Kong Gateway versions < 3.2.0.0 do not support these fields. The plugin configuration has been updated and these fields have been mapped to their old names: session_idling_timeout => session_cookie_idletime, session_memcached_host => session_memcache_host, session_memcached_port => session_memcache_port, session_redis_cluster_max_redirections => session_redis_cluster_maxredirections, session_rolling_timeout => session_cookie_lifetime, session_cookie_same_site => session_cookie_samesite, session_cookie_http_only => session_cookie_httponly, session_memcached_prefix => session_memcache_prefix, session_memcached_socket => session_memcache_socket

Please upgrade Kong Gateway to version 3.2.0.0 or above.

SAML plugin

D164

error

For the saml plugin, one or more of the following config fields are set: session_cookie_renew, session_auth_ttl, session_cookie_maxsize, session_strategy, session_compressor but Kong Gateway versions >= 3.2.0.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please remove these fields from the plugin configuration.

SAML plugin

D165

warning

For the saml plugin, config.session_storage field has been set to memcached. This is not supported in Kong Gateway versions < 3.2.0.0. The plugin configuration has been changed to config.session_storage=memcache in the data-plane.

Please upgrade Kong Gateway to version 3.2.0.0 or above.

SAML plugin

D166

warning

For the saml plugin, config.session_cookie_same_site has been set to Default. This is not supported in Kong Gateway versions < 3.2.0.0. The plugin configuration has been changed to config.session_cookie_same_site=Lax in the data-plane (default value).

Please upgrade Kong Gateway to version 3.2.0.0 or above.

SAML plugin

D167

error

For the app-dynamics plugin, instances have been configured on a specific consumer. This is not supported in Kong Gateway versions < 3.2. The plugin has been removed in the data-plane.

Unset the consumer fields for the plugin, or upgrade Kong Gateway to a version

= 3.2.

App Dynamics

D168

error

Plugin oas-validation is not available in Kong Gateway versions < 3.1.0.0.

Please upgrade Kong Gateway to version 3.1.0.0 or above.

OAS Validation plugin

D169

error

For the service entity, one of tls_verify, tls_verify_depth, ca_certificates or client_certificate fields has been set with protocol set to TLS. This is not supported in Kong Gateway versions < 3.2.0.0. These fields have been removed from the service configuration in the data-plane and the service has been disabled.

Please upgrade Kong Gateway to version 3.2.0.0 or above.

Service entity

D170

error

For the rate-limiting-advanced plugin, config.strategy field has been set to cluster. This is not supported in Kong Gateway versions < 3.2.0.0. The plugin configuration has been changed to config.strategy=local and sync_rate=null in the data-plane and might not work as intended.

Please upgrade Kong Gateway to version 3.2.0.0 or above.

rate-limiting-advanced plugin

D171

error

For the service entity, one of tls_verify, tls_verify_depth, ca_certificates or client_certificate fields has been set with protocol set to TLS. This is not supported in Kong Gateway versions < 3.2.0.0. These services and the associated plugins and routes have been removed from the configuration in the data-plane.

Please upgrade Kong Gateway to version 3.2.0.0 or above.

Service entity

P101

error

For the acme plugin, one or more of the following config fields are set: preferred_chain, storage_config.vault.auth_method, storage_config.vault.auth_path, storage_config.vault.auth_role, storage_config.vault.jwt_path but Kong Gateway versions < 2.6 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6 or above.

ACME plugin

P102

error

For the aws-lambda plugin, one or more of the following config fields are set: base64_encode_body but Kong Gateway versions < 2.6 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6 or above.

AWS Lambda plugin

P103

error

For the grpc-web plugin, one or more of the following config fields are set: allow_origin_header but Kong Gateway versions < 2.6 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6 or above.

gRPC Web plugin

P104

error

For the request-termination plugin, one or more of the following config fields are set: echo, trigger but Kong Gateway versions < 2.6 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.6 or above.

Request Termination plugin

P105

error

For the datadog plugin, one or more of the following config fields are set: service_name_tag, status_tag, consumer_tag but Kong Gateway versions < 2.7 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.7 or above.

Datadog plugin

P106

error

For the datadog plugin, distribution metric type is not support in Kong gateway versions < 2.7. Distribution metrics will not be emitted by the gateway.

Please upgrade Kong Gateway to version 2.7 or above.

Datadog plugin

P107

error

For the ip-restriction plugin, one or more of the following config fields are set: status, message but Kong Gateway versions < 2.7 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.7 or above.

IP Restriction plugin

P108

error

For the rate-limiting plugin, one or more of the following config fields are set: redis_ssl, redis_ssl_verify, redis_server_name but Kong Gateway versions < 2.7 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.7 or above.

Rate Limiting plugin

P109

error

For the zipkin plugin, config.header_type field has been set to ignore. This is not supported in Kong Gateway versions < 2.7. The plugin configuration has been changed to config.header_type=preserve in the data-plane.

Please upgrade Kong Gateway to version 2.7 or above.

Zipkin plugin

P110

error

For the zipkin plugin, one or more of the following config fields are set: local_service_name but Kong Gateway versions < 2.7 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.7 or above.

Zipkin plugin

P111

error

For the acme plugin, one or more of the following config fields are set: rsa_key_size but Kong Gateway versions < 2.8 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8 or above.

ACME plugin

P112

error

For the rate-limiting plugin, one or more of the following config fields are set: redis_username but Kong Gateway versions < 2.8 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8 or above.

Rate Limiting plugin

P113

error

For the response-ratelimiting plugin, one or more of the following config fields are set: redis_username but Kong Gateway versions < 2.8 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 2.8 or above.

Response Rate Limiting plugin

P114

error

For the response-ratelimiting plugin, one or more of the following config fields are set: redis_username but Kong Gateway versions < 2.8 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

Response Rate Limiting plugin

P115

error

Plugin opentelemetry is not available in Kong gateway versions < 3.0.

Please upgrade Kong Gateway to version 3.0 or above.

OpenTelemetry plugin

P116

error

For the zipkin plugin, one or more of the following config fields are set: http_span_name, connect_timeout, send_timeout, read_timeout but Kong Gateway versions < 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

Zipkin plugin

P117

error

For the prometheus plugin, one or more of the following config fields are set: status_code_metrics, latency_metrics, bandwidth_metrics, upstream_health_metrics but Kong Gateway versions < 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

Prometheus plugin

P118

error

For the acme plugin, one or more of the following config fields are set: allow_any_domain but Kong Gateway versions < 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

ACME plugin

P119

error

For the Service entity, enabled field has been set to true but Kong Gateway versions < 2.7 do not support this feature. The Service has been left enabled in the Kong Gateway, and the traffic for the Service is being routed by Kong Gateway. This is a critical error and may result in unwanted traffic being routed to the upstream Services via Kong Gateway.

Please upgrade Kong Gateway to version 2.7 or above.

Service entity

P120

error

For the aws-lambda plugin, one or more of the following config fields are set: proxy_scheme but Kong Gateway versions >= 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please use config.proxy_url instead of config.proxy_scheme field.

AWS Lambda plugin

P121

error

For the aws-lambda plugin, config.aws_region and config.host fields are set. These fields were mutually exclusive for Kong gateway versions < 3.0. The plugin configuration has been changed to remove the config.host field.

Please upgrade Kong Gateway to version 3.0 or above.

AWS Lambda plugin

P122

error

For the pre-function plugin, config.functions field has been used. This is not supported in Kong Gateway versions >= 3.0. The plugin configuration has been updated to rename config.functions to config.access in the data-plane.

Please update the configuration to use config.access field instead of config.functions.

Serverless Functions plugin

P123

error

For the post-function plugin, config.functions field has been used. This is not supported in Kong Gateway versions >= 3.0. The plugin configuration has been updated to rename config.functions to config.access in the data-plane.

Please update the configuration to use config.access field instead of config.functions.

Serverless Functions plugin

P124

warning

For the pre-function plugin, config.functions field has been used. This field is deprecated and it is no longer supported in Kong Gateway versions >= 3.0.

Please update the plugin configuration to use config.access field in place of config.functions field

Serverless Functions plugin

P125

warning

For the post-function plugin, config.functions field has been used. This field is deprecated and it is no longer supported in Kong Gateway versions >= 3.0.

Please update the plugin configuration to use config.access field in place of config.functions field

Serverless Functions plugin

P125

warning

For the post-function plugin, config.functions field has been used. This field is deprecated and it is no longer supported in Kong Gateway versions >= 3.0.

Please update the plugin configuration to use config.access field in place of config.functions field

Serverless Functions plugin

P126

error

For the upstream entity, one or more of the following schema fields are set: hash_on_query_arg, hash_fallback_query_arg, hash_on_uri_capture, hash_fallback_uri_capture but Kong Gateway versions < 3.0 do not support these fields.

Please upgrade Kong Gateway to version 3.0 or above.

Upstream entity

P127

error

For the upstream entity, one or more of the hash_on, hash_fallback schema fields are set with one of the following values: path, query_arg, uri_capture, but Kong Gateway versions < 3.0 do not support these values. Because of this, hash_on and hash_fallback'have been changed in the data-plane to none` and hashing is not working as expected.

Please upgrade Kong Gateway to version 3.0 or above.

Upstream entity

P128

warning

For the paths field used in route a regex pattern usage was detected. This field has been back-ported by stripping the prefix ~. Routes which rely on regex parsing may not work as intended on Kong gateway versions < 3.0. If upgrading to version 3.0 is not possible, using paths without the ~ prefix will avoid this warning.

Please upgrade Kong Gateway to version 3.0 or above.

Route entity

P129

warning

For the paths field used in route a regex pattern usage was detected. Kong gateway versions 3.0 and above require that regular expressions start with a ~ character to distinguish from simple prefix match.

To define a regular expression based path for routing, please prefix the path with ~ character.

Route entity

P130

error

For the statsd plugin, one or more of the following metrics are being used: shdict_usage, status_count_per_user_per_route, status_count_per_workspace, but Kong Gateway versions < 3.0 do not support these. These metrics have been removed from the statsd plugin configuration and features that rely on them are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

StatsD plugin

P131

error

For the statsd plugin, one or more metrics have one or more of the following fields set: workspace_identifier, service_identifier. These fields are unsupported in Kong Gateway versions < 3.0 and have been removed. Features that rely on these removed fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

StatsD plugin

P132

error

For the statsd plugin, one or more metrics don’t have the consumer_identifier field set. For these metrics, the value of the consumer_identifier field has been set to custom_id.

Explicitly set the consumer_identifier field for all metrics or upgrade Kong Gateway to a version >= 3.0.

StatsD plugin

P133

error

For the statsd plugin, one or more of the following config fields are set: allow_status_codes, udp_packet_size, use_tcp, hostname_in_prefix, consumer_identifier_default, service_identifier_default, workspace_identifier_default but Kong Gateway versions < 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

StatsD plugin

P134

error

Tags that contain space characters ( ) are not supported on Kong gateway versions < 3.0. As such, all tag values that contain space characters have been removed.

Please upgrade Kong Gateway to version 3.0 or above.

Tags

P135

error

The vaults entity is being used, but Kong Gateway versions < 3.1 do not support this entity.

Please upgrade Kong Gateway to version 3.1 or above.

Vaults entity

P136

error

For the zipkin plugin, one or more of the following config fields are set: http_response_header_for_traceid but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

Zipkin plugin

P137

error

For the rate-limiting plugin, one or more of the following config fields are set: error_code, error_message but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

Rate Limiting plugin

P138

error

For the acme plugin, one or more of the following config fields are set: storage_config.redis.ssl, storage_config.redis.ssl_verify, storage_config.redis.ssl_server_name but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

ACME plugin

P139

error

For the response-ratelimiting plugin, one or more of the following config fields are set: redis_ssl, redis_ssl_verify, redis_server_name but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

Response Ratelimiting plugin

P140

error

For the aws-lambda plugin, one or more of the following config fields are set: aws_assume_role_arn, aws_role_session_name but Kong Gateway versions < 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

AWS Lambda plugin

P141

error

The key entity is being used, but Kong Gateway versions < 3.1 do not support this entity.

Please upgrade Kong Gateway to version 3.1 or above.

Keys entity

P142

error

The key-set entity is being used, but Kong Gateway versions < 3.1 do not support this entity.

Please upgrade Kong Gateway to version 3.1 or above.

Key Sets entity

P144

error

For the pre-function plugin, one or more of the following config fields are set: ws_handshake, ws_client_frame, ws_upstream_frame, ws_close but Kong Gateway versions < 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

Serverless Functions plugin

P145

error

For the pre-function plugin, one or more of the following config fields are set: ws_handshake, ws_client_frame, ws_upstream_frame, ws_close but Kong Gateway versions < 3.0 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.0 or above.

Serverless Functions plugin

P146

error

For the acme plugin, one or more of the following config fields are set: enable_ipv4_common_name but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

ACME plugin

P147

error

For the datadog plugin, one or more of the following config fields are set: retry_count, queue_size, flush_timeout but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

Datadog plugin

P148

error

For the session plugin, one or more of the following config fields are set: cookie_persistent but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

Session plugin

P149

error

For the plugin entity, one or more of the following schema fields are set: instance_name but Kong Gateway versions < 3.2 do not support these fields.

Please upgrade Kong Gateway to version 3.2 or above.

Plugin entity

P150

error

For the zipkin plugin, one or more of the following config fields are set: phase_duration_flavor but Kong Gateway versions < 3.2 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.2 or above.

Zipkin plugin

P151

error

For the upstream entity, the algorithm field is set to latency'but Kong Gateway versions < 3.2 do not support this value.Because of this, algorithm has been set to the default value round-robin and features depending on the latency` algorithm may not work as expected.

Please upgrade Kong Gateway to version 3.2 or above.

Upstream entity

P152

error

For the statsd plugin, one or more of the following config fields are set: retry_count, queue_size, flush_timeout but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.1 or above.

StatsD plugin

P153

error

For the statsd plugin, one or more of the following config fields are set: tag_style but Kong Gateway versions < 3.2 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.2 or above.

StatsD plugin

P154

error

For the statsd plugin, one or more default metrics have been configured with a non-default stat_type. This is not supported in Kong Gateway versions < 3.1.

Please upgrade Kong Gateway to version 3.1 or above.

StatsD plugin

P155

error

For the session plugin, one or more of the following config fields are set: audience, absolute_timeout, remember_cookie_name, remember_rolling_timeout, remember_absolute_timeout, response_headers, request_headers but Kong Gateway versions < 3.2 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.2 or above.

Session plugin

P156

warning

For the session plugin, one or more config fields are set but Kong Gateway versions < 3.2 do not support these fields. The plugin configuration has been updated and these fields have been mapped to their old names: rolling_timeout => cookie_lifetime, idling_timeout => cookie_idletime, stale_ttl => cookie_discard, cookie_same_site => cookie_samesite, cookie_http_only => cookie_httponly

Please upgrade Kong Gateway to version 3.2 or above.

Session plugin

P157

error

For the session plugin, one or more of the following config fields are set: cookie_renew but Kong Gateway versions >= 3.2 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please remove these fields from the plugin configuration.

Session plugin

P158

warning

For the session plugin, one or more config fields are set but Kong Gateway versions < 3.2 do not support these fields. The plugin configuration has been updated and these fields have been mapped to their old names: remember => cookie_persistent

Please upgrade Kong Gateway to version 3.2 or above.

Session plugin

P159

error

For the session plugin, one or more of the following config fields are set: remember but Kong Gateway versions < 3.1 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please remove these fields from the plugin configuration.

Session plugin

P160

warning

For the session plugin, config.cookie_same_site has been set to Default. This is not supported in Kong Gateway versions < 3.2. The plugin configuration has been changed to the config.cookie_same_site=Lax in the data-plane (default value).

Please upgrade Kong Gateway to version 3.2 or above.

Session plugin

P161

error

For the aws-lambda plugin, one or more of the following config fields are set: aws_imds_protocol_version but Kong Gateway versions < 3.2 do not support these fields. Plugin features that rely on these fields are not working as intended.

Please upgrade Kong Gateway to version 3.2 or above.

AWS Lambda plugin

P162

error

For the opentelemetry plugin, instances have been configured on a specific service, route, or consumer. This is not supported in Kong Gateway versions < 3.2. The plugin has been removed in the data-plane.

Unset the service, route, and consumer fields for the plugin, or upgrade Kong Gateway to a version >= 3.2.

OpenTelemetry plugin

Thank you for your feedback.
Was this page useful?
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2023