错误码
|
HTTP status code |
错误码 |
错误信息 |
描述 |
操作 |
| 400 | CacheReserveDomain.EffectiveScopeEmpty | Effective scope is empty. | 缓存保持域名没有关联生效范围 | 诊断 |
| 400 | CacheReserveDomain.Vpc.Maximum | CacheReserveDomain bound vpc count exceed the maximum. | 缓存保持域名绑定vpc数量超过最大数量限制 | 诊断 |
| 400 | CustomLine.InUsed | customLine is in used can not delete.%s | 自定义线路被引用无法删除 | 诊断 |
| 400 | CustomLine.IpOverlap | customLine ip is overlap.%s | 自定义线路ip段重叠 | 诊断 |
| 400 | EdgeDns.CallEdgeDnsServerFailed | Call edge dns server failed. | 调用自建DNS服务器失败。 | 诊断 |
| 400 | Edgedns.Cluster.AppVersionExpired | Edge dns cluster app version is expired. | 自建DNS集群软件版本已过期。 | 诊断 |
| 400 | EdgeDns.Cluster.BindCountExceedLimit | The number of clusters bound to the resource exceeds the limit. | 资源关联的自建DNS解析集群超过上限。 | 诊断 |
| 400 | EdgeDns.Cluster.CacheReserveDomainDuplicate | Edge dns cluster is bind to same domain name. | 自建DNS集群关联了同名的缓存保持域名。 | 诊断 |
| 400 | Edgedns.Cluster.ForbiddenRetryResourceActionJob | Access forbidden to retry resource action job. | 已有进行中的数据同步任务，禁止重复提交。 | 诊断 |
| 400 | EdgeDns.Cluster.NoNodes | Cluster does not have nodes. | 自建DNS集群下无有效节点。 | 诊断 |
| 400 | EdgeDns.Cluster.NotBelongToUser | Cluster does not belong to user. | 自建DNS集群不属于当前用户。 | 诊断 |
| 400 | EdgeDns.Cluster.NotExists | Cluster does not exist. | 自建DNS集群不存在 | 诊断 |
| 400 | Edgedns.Cluster.NotSupportCurrentEnv | Edge dns cluster not support current env. | 自建DNS集群环境属性非法。 | 诊断 |
| 400 | Edgedns.Cluster.NotSupportOperator | Edge dns cluster not support operator. | 不支持操作自建DNS运维集群 | 诊断 |
| 400 | EdgeDns.Cluster.ResolveRuleDuplicate | Edge dns cluster is bind to same forward zone name. | 自建DNS集群关联了同名的转发规则。 | 诊断 |
| 400 | EdgeDns.Cluster.ZoneDuplicate | Edge dns cluster is bind to same authority zone name. | 自建DNS集群关联了同名权威Zone | 诊断 |
| 400 | EdgeDns.InvalidResourceType | The resource type is invalid. | 自建DNS删除节点时，查询的资源类型不合法 | 诊断 |
| 400 | EdgeDns.InvalidUserId | The user id is invalid. | 用户id不合法 | 诊断 |
| 400 | InboundEndpoint.InvalidId | The inboundEndpoint id is invalid. | 入站终端节点Id无效 | 诊断 |
| 400 | InboundEndpoint.InvalidSecurityGroupId | The specified security group id is invalid. | 入站终端节点安全组id无效 | 诊断 |
| 400 | InboundEndpoint.InvalidSpecVersion | The inboundEndpoint spec version is invalid. | 入站终端节点规格版本无效 | 诊断 |
| 400 | InboundEndpoint.InvalidStatus | The inboundEndpoint status is invalid. | 入站终端节点设置状态无效 | 诊断 |
| 400 | InboundEndpoint.InvalidUserId | The UserId parameter is invalid. | 入站终端节点用户Id无效 | 诊断 |
| 400 | InboundEndpoint.InvalidVpcId | The specified vpc is invalid. | 入站终端节点vpc id无效 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.BelowMinimum | The number of source IP addresses that are specified for outbound traffic below minimum. | 入站终端节点服务IP地址数量低于最小限制 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.DuplicateIp | The specific ip has duplicated with exist one. | 入站终端节点服务IP地址重复 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.DuplicateIpWithForwardIp | The specific IP has duplicated with forward IP. | 入站终端节点服务IP与同VPC内出站终端节点关联的转发规则目的IP重复 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.DuplicateIpWithResolverEndpointIp | The specific IP has duplicated with resolver endpoint IP. | 入站终端节点服务IP与同VPC内出站终端节点服务P重复 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.ExceedsLimit | The number of source IP addresses that are specified for outbound traffic exceeds the upper limit. | 入站终端节点服务IP地址数量超过最大限制 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.InvalidAzId | The specified az id is invalid. | 入站终端节点服务IP地址的可用区id无效 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.InvalidCidrBlock | The specified cidrBlock is invalid. | 入站终端节点服务IP地址的子网掩码无效 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.InvalidIp | The specified IP address is invalid. | 入站终端节点服务IP地址无效 | 诊断 |
| 400 | InboundEndpoint.Ipconfig.InvalidVSwitch | The specified vswitch is invalid. | 入站终端节点服务IP地址的交换机id无效 | 诊断 |
| 400 | InboundEndpoint.Name.Duplicate | The specified endpoint name is the same as an existing endpoint name. | 入站终端节点名称重复 | 诊断 |
| 400 | InboundEndpoint.Name.ExceedsLength | The maximum length of an endpoint name is reached. | 入站终端节点名称超过长度限制 | 诊断 |
| 400 | InboundEndpoint.NotExsits | The inboundEndpoint is not Exsit. | 入站终端节点不存在 | 诊断 |
| 400 | InboundEndpoint.Num.ExceedsLimit | The maximum number of endpoints is reached. | 入站终端节点数量超过最大限制 | 诊断 |
| 400 | InboundEndpoint.OperationForbidden.Status | The specific status of endpoint is unsupported for operation. | 入站终端节点处于不可操作的状态 | 诊断 |
| 400 | InboundEndpoint.Region.Unsupported | The specific region is unsupported for resolver. | 入站终端节点不支持该region | 诊断 |
| 400 | InboundEndpoint.SystemAssignUnsupportedOperation | The system assign inboundEndpoint unsupported operation. | 系统分配入站终端节点不支持该操作 | 诊断 |
| 400 | InternalError | The request processing has failed due to some unknown error, exception or failure. | 内部错误 | 诊断 |
| 400 | InvalidRegionId | Invalid region id. | 无效的地域ID参数。 | 诊断 |
| 400 | InvalidVpcId | Invalid vpc id. | 无效的VPC ID。 | 诊断 |
| 400 | InvalidVpcType | Invalid vpc type. | 无效的VPC类型 | 诊断 |
| 400 | InvalidVpcUserId | Invalid vpc user id. | 无效的VpcUserId参数 | 诊断 |
| 400 | PostBusiness.InvalidService | post business service not activated. | 后付费服务没有开通 | 诊断 |
| 400 | PostBusiness.InvalidServiceModule | post business service module not activated. | 后付费服务模块没有开通 | 诊断 |
| 400 | ResolveAnalysis.Duplicate.RegionId | Resolve analysis regionId is duplicate. | 流量分析日志转存地域ID重复 | 诊断 |
| 400 | ResolveAnalysis.Forbidden.AliyunInnerUid | Aliyun Inner account, operation prohibited. | 阿里云内部账号禁止操作，请联系云解析DNS团队处理。 | 诊断 |
| 400 | ResolveAnalysis.Forbidden.NotSupportCurrentEnv | Forbidden operation, not support current env. | 环境级别和配置不相符 | 诊断 |
| 400 | ResolveAnalysis.Forbidden.UpdateLogDeliveryConfig | Forbidden to update log delivery config. | 禁止更新流量分析配置 | 诊断 |
| 400 | ResolveAnalysis.Invalid.LogProcessMode | Log process mode is invalid. | 无效的日志处理模式参数 | 诊断 |
| 400 | ResolveAnalysis.LogDeliveryRegionMustContainAllAnalysisRegion | Log delivery region must contain all analysis region. | 日志转存地域必须包含全部的流量分析地域 | 诊断 |
| 400 | ResolverEndpoint.Id.Invalid | The endpoint id invalid. | 终端节点ID无效 | 诊断 |
| 400 | ResolverEndpoint.IpConfig.DuplicateIpWithInbound | The specific Ip has duplicated with inbound endpoint Ip. | 出站终端节点ip与入站终端节点ip重复 | 诊断 |
| 400 | ResolverRule.BindEdgeDnsCluster | The forwarding rule is already bound to a edge dns cluster. | 转发规则已关联自建集群 | 诊断 |
| 400 | ResolverRule.Endpoint.RegionNotConsistent | The region of the endpoint of the forwarding rule is inconsistent with the region bound to the VPC. | 转发规则终端节点地域和绑定Vpc的地域不一致 | 诊断 |
| 400 | ResolverRule.ForwardIps.InboundForbidden | The specified destination IP address is forbidden for the inbound. | 转发规则外部DNS系统的IP地址与入站终端节点ip重复，禁止添加 | 诊断 |
| 400 | ResolverRule.PriorityForwardConfig.AtLeastOneAddressWhenEnable | The priority forward configuration must have at least one address. | 配置启用转发规则优先转发时，需要配置至少一个HttpDNS地址。 | 诊断 |
| 400 | ResolverRule.PriorityForwardConfig.CustomAddressInvalid | The custom address of the priority forward configuration is invalid. | 优先转发配置的自定义HttpDNS地址非法 | 诊断 |
| 400 | ResolverRule.PriorityForwardConfig.PriorityInvalid | The priority of the priority forward configuration is invalid. | 优先转发配置的优先级参数非法 | 诊断 |
| 400 | ResolverRule.PriorityForwardConfig.ProtocolInvalid | The protocol of the priority forward configuration is invalid. | 优先转发配置的协议参数非法 | 诊断 |
| 400 | ResolverRule.PriorityForwardConfig.ServiceAddressInvalid | The service address of the priority forward configuration is invalid. | 优先转发配置的云解析HttpDNS服务地址参数非法 | 诊断 |
| 400 | ResolverRule.PriorityForwardConfig.StatusInvalid | The status of the priority forward configuration is invalid. | 优先转发配置的状态参数非法 | 诊断 |
| 400 | Resource.EffectiveScope.OperationTypeInvalid | Invalid operation type. | 操作类型无效。 | 诊断 |
| 400 | SlaveDns.BoundVPCandClusterForbidden | Zone that support secondary DNS cannot bind both VPC and cluster. | 配置辅助DNS的ZONE不能同时绑定VPC与自建DNS集群 | 诊断 |
| 400 | SlaveDns.EdgeClusterAdded | Secondary DNS of cluster has already been added. Please delete it before the operation. | ZONE已经配置辅助DNS功能，请删除后再进行绑定自建DNS集群 | 诊断 |
| 400 | SlaveDns.RegionVpcAdded | Secondary DNS of private zone has already been added. Please delete it before the operation. | ZONE已经配置辅助DNS功能，请删除后再进行绑定VPC | 诊断 |
| 400 | Sys.SpeedLimit.OutOfLimit | The accept speed is out of limit. | 访问频率超过限制 | 诊断 |
| 400 | Throttling.User | Request was denied due to user flow control. | 由于请求频次达到阈值，请求被拒绝，请稍后重试。 | 诊断 |
| 400 | Zone.BindEdgeDnsCluster | Zone is already bound to a edge dns cluster. | 权威Zone已绑定该集群，不可操作。 | 诊断 |
| 400 | Zone.BindEdgeDnsCluster.OnlySupportFastZone | Binding an Edge DNS cluster is only supported for Fast Zones. | 仅快速区权威Zone支持关联自建DNS集群。 | 诊断 |
| 400 | Zone.BindEdgeDnsCluster.RecordCountExceed | You cannot bind the cluster, because record count exceed the maximum. | 权威Zone下解析记录数量超过上限。禁止关联自建DNS集群。 | 诊断 |
| 400 | Zone.DnsGroupChange.Forbidden | You cannot change dns group. | 禁止切换位置区 | 诊断 |
| 400 | Zone.DnsGroupChange.Forbidden4FastZone | You cannot change dns group, because can only use fast zone. | 当前zone被禁止进行位置区切换，因为用户只能使用快速区。 | 诊断 |
| 400 | Zone.Invalid.Id | Zone id is invalid. | Zone的ID不正确 | 诊断 |
该文章对您有帮助吗？