错误码
|
HTTP status code |
错误码 |
错误信息 |
描述 |
操作 |
| 403 | APIG.ErrorCode.Forbidden | Not allowed to perform the operation. | 操作禁止，无操作权限。 | 诊断 |
| 500 | APIG.ErrorCode.InternalError | Internal error. | 系统内部错误 | 诊断 |
| 409 | Conflict.ApiDebugProtocolMismatch | Domain %s protocol mismatch, got: %s, want: %s. | 域名%s支持的协议与调试请求的协议不匹配，调试协议为%s，域名支持的协议为%s。 | 诊断 |
| 409 | Conflict.ApiNameDuplicated | API name %s duplicated. | API%s已存在，请修改名称。 | 诊断 |
| 409 | Conflict.ApiOperationQuotaExceed | The number of operations per api cannot exceed %s. Current: %s. | 每个 API 的 Operation 数量不能超过 %s 个，当前数量为 %s，请提升您的配额。 | 诊断 |
| 409 | Conflict.ApiPublishDuplicatedPathFound | Duplicated path found, key: %s, apiId: %s ,operationId: %s, environmentId: %s, conflict domains: %s. | API路径冲突，冲突键为%s，冲突的API ID为%s，接口 ID为%s，环境 ID为%s，冲突的域名为%s。 | 诊断 |
| 409 | Conflict.ApiPublished | API %s is published in %s. | API：%s已经被发布到环境：%s，请先取消发布。 | 诊断 |
| 409 | Conflict.ApiPublishServiceTypeNotSupported | Service type %s is not supported. | 不支持的服务类型：%s，请检查您的配置。 | 诊断 |
| 409 | Conflict.ApiVersionDuplicated | API version %s duplicated. | API版本%s，已存在，请更换版本号。 | 诊断 |
| 409 | Conflict.ApiVersionMustEnabled | API has more than one version, can not disable version. | API已存在多个版本，不能关闭版本管理功能。 | 诊断 |
| 409 | Conflict.AppClusterIsAlreadyInChanging | App cluster is already in changing. Retry after some minutes. | 网关实例正在变更中，请稍后重试操作。 | 诊断 |
| 409 | Conflict.ConsumerAuthorizationForbidden | Consumer has authorized to resource %s. | 消费者已授权资源%s，请勿重复授权。 | 诊断 |
| 409 | Conflict.DebugRequestFailed | Create debug request for %s failed, please check httpApi / gatewayRoute / ingressRoute settings. | 创建调试请求失败，请检查您的配置，请求URL为：%s。 | 诊断 |
| 409 | Conflict.DeleteHttpApiForbidden | The current API %s has already deployments of routes and cannot be deleted. | 当前API %s 存在已经%s个部署的路由， 不能删除。 | 诊断 |
| 409 | Conflict.DeleteRouteForbidden | The route %s cannot be deleted when its status is %s. | 路由%s 状态为%s，不允许删除。 | 诊断 |
| 409 | Conflict.DeployRouteForbidden | The route %s cannot be deployed when its status is %s. | 路由%s状态为%s，不允许部署。 | 诊断 |
| 409 | Conflict.DomainCannotDelete | Domain %s has online api or route, can not delete. | 域名%s还存在关联的已发布API或路由，无法删除，请下线相关资源后再执行操作。 | 诊断 |
| 409 | Conflict.DomainExisted | Domain %s is existed. | 域名%s已存在。 | 诊断 |
| 409 | Conflict.DomainQuotaPerGatewayExceed | The number of bound domain per gateway cannot exceed %s. Current: %s. | 单个网关关联域名数量不能超过%s，当前数量为%s，请提升您的配额。 | 诊断 |
| 409 | Conflict.EnvironmentCannotDelete | Environment %s has online api, can not delete. | 环境%s存在关联的已发布的API或路由，无法删除，请下线相关资源后再执行操作。 | 诊断 |
| 409 | Conflict.EnvironmentExisted | Environment %s is existed. | 已经存在名称为%s的环境，请更换环境名称。 | 诊断 |
| 409 | Conflict.EnvironmentGatewayNotReady | The gateway %s in the environment %s is not ready, please wait for the gateway to be ready before proceeding. | 环境 %s 里的网关 %s 未就绪，请等网关就绪后再操作。 | 诊断 |
| 409 | Conflict.EnvironmentPublishing | Environment %s is publishing, please retry later. | 环境%s正处于发布中，请稍后重试。 | 诊断 |
| 409 | Conflict.Fc2NotSupported | The FC integration solution has been upgraded. Please re-create the FC service before publishing the API/route. | FC集成方案已升级，请重新创建FC服务后再发布API/路由。 | 诊断 |
| 409 | Conflict.GatewayEnvironmentLimitExceeded | The number of environment per gateway cannot exceed %s, current: %s. | 每个网关关联的环境不应超过%s个，当前为%s个，请提升您的配额。 | 诊断 |
| 409 | Conflict.GatewayIsDeleted | The gateway %s is deleted. | 网关%s已删除。 | 诊断 |
| 409 | Conflict.GatewayNotSupportedWAF | The gateway %s does not support enabling WAF protection. Please upgrade to a version of the gateway that supports it. | 网关%s不支持开启WAF防护，请升级到支持的网关版本。 | 诊断 |
| 409 | Conflict.GatewayStatusInvalidForbidden | The operation is not allowed in the current gateway status. Wait until the gateway is in the running state and try again. | 网关当前不支持操作，请等网关正常运行时再做操作。 | 诊断 |
| 409 | Conflict.GatewayStatusNotExpected | The status of the gateway %s is not the expected status %s. | 网关的状态%s不是期望的状态%s。 | 诊断 |
| 409 | Conflict.HttpApiTypeNotSupportedForRoute | Only APIs of type Http, HttpIngress, and Websocket support route. | 只有类型为Http, HttpIngress, Websocket的API支持路由。 | 诊断 |
| 409 | Conflict.HttpIngressApiExistedWhenDeleteSource | The service source is used by http ingress api, please delete the corresponding HTTP Ingress API before removing the service source. The associated HTTP Ingress API ID is %s. | 存在http ingress api使用该来源，请先删除对应http ingress api后再删除服务来源，关联的http ingress api ID为%s。 | 诊断 |
| 409 | Conflict.K8sServiceSourceExisted | The k8s service source of %s is existed. | 网关已存在%s集群的K8s服务来源。 | 诊断 |
| 409 | Conflict.K8sServiceSourceLimitExceeded | The number of k8s service source per gateway cannot exceed %s. Current: %s. | 单个网关的K8s服务来源数量不能超过%s，当前数量为%s，请提升您的配额。 | 诊断 |
| 409 | Conflict.OnlineOperationQuotaPerGatewayExceed | The number of online operation per gateway cannot exceed %s. Current: %s. | 单个网关在线接口数量不能超过%s，当前数量为%s，请提升您的配额。 | 诊断 |
| 409 | Conflict.OperationNameDuplicated | Operation name %s duplicated. | 接口%s已存在，请修改名称。 | 诊断 |
| 409 | Conflict.OperationQuotaExceed | The number of operations per region cannot exceed %s. Current: %s. | 接口总数量不能超过%s，当前数量为%s，请提升您的配额。 | 诊断 |
| 409 | Conflict.OssRequestError | Failed to access OSS, please check the parameter configuration or your account RAM permissions. | 访问OSS失败，请检查参数配置或您的账户RAM权限 | 诊断 |
| 409 | Conflict.PluginClassNotReady | Plugin class %s is not ready. | 插件%s尚未就绪，请稍后重试安装。 | 诊断 |
| 409 | Conflict.PluginCountExceed | Plugin count exceed %s. | 插件数量超过配额，当前插件数量为%s个。 | 诊断 |
| 409 | Conflict.PluginHasAttachedRule | Plugin %s is using. Please check api/operation/route/domain/gateway whether config enabled plugin rule, stop these plugin rules and retry. | 插件%s 可能在API/接口、路由、域名或网关实例上开启，无法卸载，请检查并停用对应资源上的插件规则再试。 | 诊断 |
| 409 | Conflict.PluginInstalled | Plugin class %s installed, you must uninstall first. | 插件%s已安装到网关实例，请先卸载相关网关实例的插件再进行删除。 | 诊断 |
| 409 | Conflict.PluginInstallGatewayNotReady | Gateway %s is not ready. | 网关实例%s状态未就绪，请稍后再安装插件。 | 诊断 |
| 409 | Conflict.PluginNameExisted | Plugin name %s existed. | 插件%s已存在，请修改名称。 | 诊断 |
| 409 | Conflict.PluginOtherVersionInstalled | Plugin class %s version %s installed, you must uninstall old version first. | 插件%s的%s版本已经安装，请先卸载后再重试。 | 诊断 |
| 409 | Conflict.PluginPublishSameVersion | Plugin %s version %s has been published. | 插件%s的%s版本已发布，请勿重复发布。 | 诊断 |
| 409 | Conflict.PluginPublishVersionOnlyIncrement | Plugin %s version %s must be larger than history version. | 插件%s的版本%s不合法，版本只能向上递增，并超过所有历史版本。 | 诊断 |
| 409 | Conflict.PluginWasmFileIllegal | Plugin wasm file %s illegal. | 插件WASM文件非法，文件名为%s。 | 诊断 |
| 409 | Conflict.PolicyAttachExceedLimit | Resource can not attach 2 same class policy. | 一个资源上不能挂两个相同类型的策略。 | 诊断 |
| 409 | Conflict.PolicyExisted | Policy %s is existed. | 策略%s已存在，无法重复启用。 | 诊断 |
| 409 | Conflict.RouteBackServiceProtocolNotSupported | The route currently does not support the service protocol %s. | 路由暂时不支持服务协议%s。 | 诊断 |
| 409 | Conflict.RouteNameDuplicated | Route name %s is duplicated. | 路由%s已存在，请修改名称。 | 诊断 |
| 409 | Conflict.RouteQuotaPerGatewayExceed | The number of route per gateway cannot exceed %s. Current: %s. | 单个网关的路由数量不能超过%s，当前数量为%s，请提升您的配额。 | 诊断 |
| 409 | Conflict.SdkGenerating | SDK is generating, please retry later. | SDK生成中，请稍后重试。 | 诊断 |
| 409 | Conflict.SecurityGroupRulesLimitExceeded | The security group rule ports count cannot be greater than 5. | 网关的安全组规则数量不能超过5条。 | 诊断 |
| 409 | Conflict.ServiceExisted | the service %s is existed. | 已存在名为%s的服务，请修改服务名称。 | 诊断 |
| 409 | Conflict.ServiceIsReferencedWhenDelete | There are other resources referencing this service. Please unbind it before deleting the service. The associated resources are %s. | 存在其他资源引用此服务，请先解绑后再删除服务，关联的资源为%s。 | 诊断 |
| 409 | Conflict.ServiceQuotaPerGatewayExceed | The number of service per gateway cannot exceed %s. Current: %s. | 单个网关的服务数量不能超过%s，当前数量为%s，请提升您的配额。 | 诊断 |
| 409 | Conflict.ServicesExistedWhenDeleteSource | The service source is used by services %s. | 服务来源还存在服务，请先删除对应服务后再删除服务来源，关联的服务ID为%s。 | 诊断 |
| 409 | Conflict.ServiceSourceUpdateIsDisabled | The service source is allowed to update when it's type must be K8S. | 仅允许修改K8s类型的服务来源。 | 诊断 |
| 409 | Conflict.ServiceUpdateIsDisabled | The service is allowed to update when it's source type must be DNS or VIP. | 仅允许修改DNS和固定地址类的服务。 | 诊断 |
| 409 | Conflict.ServiceVersionExisted | Service version %s already exists, please change the service version name. | 服务版本 %s 已存在，请更换服务版本名称。 | 诊断 |
| 409 | Conflict.SourceExistedWhenCreateIngressApi | The service source %s is already being used by another HTTP Ingress API. Please use a different service source to create the HTTP Ingress API. | 该服务来源 %s已经被其他HTTP Ingress API使用，请使用其他的服务来源来创建HTTP Ingress API。 | 诊断 |
| 409 | Conflict.UndeployRouteForbidden | Route %s cannot be updeployed when its status is %s. | 路由%s 状态为%s, 不允许取消部署。 | 诊断 |
| 409 | Conflict.UpdateRouteEnvironmentForbidden | The route %s cannot be allowed to change the environment when its status is %s. | 当前路由%s状态为%s不允许更改环境。如需修改，可以先将路由部署，待完成后再更换环境。 | 诊断 |
| 409 | Conflict.UpdateRouteForbidden | The route %s cannot be updated when its status is %s. | 路由 %s 状态为 %s, 不允许更新。 | 诊断 |
| 409 | Conflict.WafAttachConditionNotMatch | WAF should be enabled on gateway instance first. | 您必须先在网关实例启用WAF后才能配置WAF策略。 | 诊断 |
| 400 | InvalidParameter.ConsumerAkLengthExceed | Consumer AK length can not exceed %s. Current %s. | 消费者AK长度超限，不能超过%s，当前%s。 | 诊断 |
| 400 | InvalidParameter.ConsumerApiKeyLengthExceed | Consumer ApiKey length can not exceed %s. Current %s. | 消费者ApiKey长度超限，限制%s，当前%s。 | 诊断 |
| 400 | InvalidParameter.ConsumerNameExceedLimit | Consumer name length can not exceed 64 characters, now %s. | 消费者名称长度不能超过64个字符，现在 %s。 | 诊断 |
| 400 | InvalidParameter.ConsumerNameStartOrEndFormatIllegal | consumer name must start and end with an alphanumeric character, now %s. | 消费者名称必须以字母或者数字开头或者结尾，当前%s。 | 诊断 |
| 400 | InvalidParameter.ConsumerSkLengthExceed | Consumer SK length can not exceed %s. Current %s. | 消费者sk长度超限，限制长度%s，当前%s。 | 诊断 |
| 400 | InvalidParameter.DomainNameExceedLimit | Domain name length can not exceed 128 characters, now %s. | 域名长度为%s，超过长度限制，最大允许的域名长度为128位。 | 诊断 |
| 409 | InvalidParameter.EnvironmentAliasLengthExceedUpLimit | Environment alias can not exceed than 50 characters, now %s. | 当前环境别名长度为%s，至多应不超过50个字符。 | 诊断 |
| 400 | InvalidParameter.EnvironmentAliasStartOrEndFormatIllegal | Environment alias must start with an alphanumeric or Chinese character, now %s. | 环境别名：%s不合法，应当以字母或汉字作为环境别名的开头。 | 诊断 |
| 400 | InvalidParameter.EnvironmentFormatIllegal | Environment name can only contain alphanumeric characters, dashes, dots, now %s. | 环境名称：%s不合法，应当仅包含字母，数字，点号与中划线。 | 诊断 |
| 400 | InvalidParameter.EnvironmentNameStartOrEndFormatIllegal | Environment name must start and end with an alphanumeric character, now %s. | 环境名称：%s不合法，应当以字母和数字作为环境名称的开头与结尾。 | 诊断 |
| 400 | InvalidParameter.FailToBindBody | Fail to bind body. | 解析请求内容失败，请检查参数数据类型是否有误。 | 诊断 |
| 400 | InvalidParameter.HttpApiTypeNotSupported | The HTTP API type %s is not supported. | HTTP API类型%s不支持。 | 诊断 |
| 400 | InvalidParameter.HttpTriggerRequired | Function %s version %s doesn't have a http trigger. | 函数%s/%s没有配置HTTP触发器，无法作为API和路由的后端服务，请为函数添加HTTP触发器。 | 诊断 |
| 400 | InvalidParameter.InvalidGatewaySpecification | The specification for upgrading or downgrading is invalid. Please make a different selection. | 升配或降配的配置不合法，请重新选择。 | 诊断 |
| 400 | InvalidParameter.IsEmpty | Required parameter should not be empty. | 必填参数为空 | 诊断 |
| 400 | InvalidParameter.OasSpecParseFailed | OpenAPI Schema parse failed, due to %s. | OpenAPI定义解析失败，失败原因为：%s。 | 诊断 |
| 400 | InvalidParameter.PluginNameExist | The plugin name already exists. | 已存在同名的插件。 | 诊断 |
| 400 | InvalidParameter.PolicyNotSupportedType | Not supported global policy type %s. | %s不是被支持的全局策略类型。 | 诊断 |
| 400 | InvalidParameter.RouteConfigHostnamesIsEmpty | The parameter is not valid, the domain list cannot be empty. | 参数不合法，域名列表不能为空。 | 诊断 |
| 400 | InvalidParameter.SwaggerSpecParseFailed | Swagger definition parse failed, due to %s. | Swagger定义解析失败，失败原因为：%s。 | 诊断 |
| 400 | InvalidParameter.WithDetail | Invalid parameter value. | 无效的请求参数 | 诊断 |
| 404 | NotFound.CsClusterNotFound | CS cluster %s is not found. | 容器服务集群%s不存在，请检查配置。 | 诊断 |
| 404 | NotFound.EnvironmentNotFound | Environment %s is not found. | 环境%s不存在，请检查请求参数。 | 诊断 |
| 404 | NotFound.GatewayNotFound | Gateway %s is not found. | 您所查询的网关实例不存在，实例ID：%s。 | 诊断 |
| 404 | NotFound.GatewayVersionNotConfig | The gateway version is not configured. | 未找到网关版本的配置。 | 诊断 |
| 404 | NotFound.SAEK8SServiceNotFound | The SAE K8S service %s in the namespace %s is not found. | SAE K8S Service %s不存在，命名空间为%s。 | 诊断 |
| 404 | NotFound.ServiceNotFound | The service %s is not found. | 未找到指定的服务，ID为%s。 | 诊断 |
| 404 | NotFound.ServiceSourceNotFound | The service source %s is not found. | 未找到指定的服务来源，ID为%s。 | 诊断 |
| 404 | NotFound.ServiceVersionNotFound | Service version %s not found, please confirm that the service version name is correct. | 服务版本 %s 未找到，请确认服务版本名称正确。 | 诊断 |
| 400 | CloudProductInactive.LogDeliveryNotEnabled | SLS log delivery configuration is not enabled. | 网关未开启 SLS 日志投递功能 | 诊断 |
| 409 | Conflict.DomainIsProcessing | The domain %s is currently being deployed. Please try again later. | 目标环境域名正在部署中 | 诊断 |
| 404 | NotFound.ConsumerAuthorizationRule | The ConsumerAuthorizationRule '%s' does not exist under Consumer '%s'. | 查询的消费者授权规则不存在 | 诊断 |
| 400 | InvalidParameter.BothEmpty | Parameter ResourceId and Tag should not both be empty. At least one must be provided. | ResourceId 和 Tag 均未提供 | 诊断 |
| 400 | InternalError | The request processing has failed due to some unknown error. | 参数值大小写不匹配 | 诊断 |
| 404 | DatabaseError.RecordNotFound | The specified QuotaRule '%s' does not exist. | 配额规则 ID 不存在或已被删除 | 诊断 |
| 404 | NotFound.ExternalResponseNotFound | The request to the external API failed | 创建 MSE_NACOS 服务来源时，指定的 Nacos 实例不存在或当前地域不可访问 | 诊断 |
| 500 | ServiceInternalError.CreateMigrationTaskFailed | api type not match | 创建迁移任务时指定的 httpApiId 不是 HttpIngress 类型的 API。 | 诊断 |
| 500 | ServiceInternalError.FailToRequestCs | Request to cs failed | 请求容器服务集群失败，网关无法访问指定的 K8s 集群 | 诊断 |
| 500 | ServiceInternalError.UnknownError | An unknown error occurred. Please submit a ticket to contact an engineer for processing. | 未分类的服务端内部错误兜底码，响应不区分具体失败原因。 | 诊断 |
| 409 | Conflict.GatewayNotSupportAutoMaintenance | Auto maintenance is not supported for this gateway. | 该网关不支持自动维护时间窗口配置。 | 诊断 |
| 404 | ApiReplaced.UseUpdateAuthorizationRule | This API has been deprecated and replaced. Please use UpdateAuthorizationRule at /v1/authorization-rules/{consumerAuthorizationRuleId} instead. | 该 API 已废弃并被替代，请改用 UpdateAuthorizationRule（PUT /v1/authorization-rules/{consumerAuthorizationRuleId}）。 | 诊断 |
| 500 | GatewayIsDeleted.GetMigrationNamespacedServicesFailed | The gateway associated with migration task has been deleted. Please create a new migration task with an active gateway. | 迁移任务关联的网关已被删除，请使用处于正常状态的网关重新创建迁移任务。 | 诊断 |
| 404 | DatabaseError.RecordNotFound | Record not found. | 请求引用的记录不存在：迁移任务关联的后端记录不可用，请先确认任务与集群状态 | 诊断 |
| 403 | CodeupService.NotAuthorized | The caller has not authorized APIG to access Codeup, or no Codeup organization exists. Please authorize APIG to access your Codeup account and ensure at least one Codeup organization is created before calling this API. | 调用方未授权 APIG 访问云效 Codeup，或账号下不存在 Codeup 组织 | 诊断 |
| 403 | Forbidden.AccessDenied | Not allowed to perform the operation. | 没有权限执行该操作。 | 诊断 |
该文章对您有帮助吗？