Errors Reference
Code | Message |
---|---|
ERR_NGROK_100 | Invalid metadata length: |
ERR_NGROK_102 | The last payment for the |
ERR_NGROK_103 | The account |
ERR_NGROK_105 | The authtoken you specified does not look like a proper ngrok tunnel authtoken.
Your authtoken: |
ERR_NGROK_106 | The authtoken you specified is an ngrok v1 authtoken, but you're using ngrok v2.
Your authtoken: |
ERR_NGROK_107 | The authtoken you specified is properly formed, but it is invalid.
Your authtoken:
|
ERR_NGROK_108 | Your account is limited to |
ERR_NGROK_109 | The authentication payload you specified is not valid.
This usually indiciates a bug in the client's protocol implementation.
The parsing error encountered was:
|
ERR_NGROK_110 | The session cookie you specified is not valid. This usually indiciates a bug in the client's protocol implementation. |
ERR_NGROK_111 | The heartbeat interval you specified is not valid.
It must be at least |
ERR_NGROK_112 | The heartbeat tolerance you specified is not valid.
It must be at least |
ERR_NGROK_115 | Your IP |
ERR_NGROK_116 | Your IP |
ERR_NGROK_118 | Only Enterprise accounts can use the enterprise tunnel ingress feature.
Your account |
ERR_NGROK_119 | The agent specified an invalid semantic version string: |
ERR_NGROK_120 | Your |
ERR_NGROK_121 | Your |
ERR_NGROK_122 | Your account is not permitted to use the agent ingress " |
ERR_NGROK_123 | The account " |
ERR_NGROK_124 | Your agent provided an invalid UserAgent: |
ERR_NGROK_125 | The analytics payload you specified is not valid.
This usually indiciates a bug in the client's protocol implementation.
The parsing error encountered was:
|
ERR_NGROK_126 | The agent ingress " |
ERR_NGROK_127 | Your account is not permitted to use the agent ingress via " |
ERR_NGROK_200 | The ngrok API requires that you set the Authorization header for authentication. Your API keys and instructions are available on your dashboard: https://dashboard.ngrok.com/api-keys |
ERR_NGROK_201 | The ngrok API requires that you use Basic or Bearer authentication via the Authorization header. It could not parse the header in this request. Authorization Header: |
ERR_NGROK_202 | The API authentication you specified does not look like a valid credential. Your credential: |
ERR_NGROK_203 | The API authentication you specified is properly formed, but it is invalid. Your authentication: |
ERR_NGROK_204 | This is a valid API token, but the account |
ERR_NGROK_205 | The account |
ERR_NGROK_206 | The authentication you specified is actually a tunnel credential. Your credential: |
ERR_NGROK_207 | The authentication you specified is actually a tunnel credential, not an API key token. Your key: |
ERR_NGROK_208 | The authentication you specified is actually an API key ID, not an API key token. Your credential: |
ERR_NGROK_210 | The content type you specified |
ERR_NGROK_211 | The |
ERR_NGROK_212 | The server was unable to read the complete request body. Please check your API client implementation and review the API documentation: https://ngrok.com/docs/api#service-api. |
ERR_NGROK_213 | The |
ERR_NGROK_214 | The request parameter |
ERR_NGROK_215 | The value provided for the request parameter |
ERR_NGROK_216 | You did not provide a Content-Type with your request. Please check your API client implementation and use one of the supported content types: https://ngrok.com/docs/api#content-types |
ERR_NGROK_217 | The provided API version |
ERR_NGROK_218 | Your request has not specified an API version. Please include the version you wish to use in the Ngrok-Version header. Supported versions: |
ERR_NGROK_219 |
|
ERR_NGROK_220 | Your IP does not match the IP Policy for this Account. Please authenticate from an IP in the correct range or update your IP Restrictions from the ngrok dashboard. https://dashboard.ngrok.com/ip-restrictions |
ERR_NGROK_221 | This is a valid API token, but the account |
ERR_NGROK_223 |
|
ERR_NGROK_224 | The value |
ERR_NGROK_225 | Your account is limited to |
ERR_NGROK_226 | Your account is rate limited to |
ERR_NGROK_227 | The ID |
ERR_NGROK_228 | The ID |
ERR_NGROK_229 | The ID |
ERR_NGROK_230 | The query part of the requested URI is invalid: |
ERR_NGROK_231 | The query part of the requested URI includes unknown parameters: |
ERR_NGROK_232 | The request must specify only a single value for the |
ERR_NGROK_233 | The page size limit must be between 1 and |
ERR_NGROK_235 | The Format |
ERR_NGROK_236 | The destination target is invalid. Expected fields include one of the following: |
ERR_NGROK_238 | The provided event type: |
ERR_NGROK_239 | The provided field: |
ERR_NGROK_240 | The provided event destination auth is invalid. |
ERR_NGROK_241 | The value " |
ERR_NGROK_242 | The ID |
ERR_NGROK_243 | The ID |
ERR_NGROK_244 | The page size limit must be a number between 1 and |
ERR_NGROK_247 | The account |
ERR_NGROK_300 | The authtoken credential |
ERR_NGROK_301 | The bind payload you specified is not valid.
This usually indiciates a bug in the client's protocol implementation.
The parsing error encountered was:
|
ERR_NGROK_302 | TCP tunnels are only available to registered users. Sign up for free at: https://dashboard.ngrok.com/signup If you have already signed up, make sure your authtoken is installed. Your authtoken is available on your dashboard: https://dashboard.ngrok.com/get-started/your-authtoken |
ERR_NGROK_303 | TLS tunnels are only available for Enterprise or Pay-as-you-go plans. Sign up at: https://dashboard.ngrok.com/signup If you have already signed up, make sure your authtoken is installed. Your authtoken is available on your dashboard: https://dashboard.ngrok.com/get-started/your-authtoken |
ERR_NGROK_304 | HTTP auth is only available to registered users. Failed to bind a tunnel with HTTP authentication for an unauthenticated client. Sign up at: https://dashboard.ngrok.com/signup If you have already signed up, make sure your authtoken is installed. Your authtoken is available on your dashboard: https://dashboard.ngrok.com/get-started/your-authtoken |
ERR_NGROK_305 | Binding custom subdomains is a feature for paid accounts.
Failed to bind the custom subdomain |
ERR_NGROK_306 | Only Personal, Pro, Enterprise, and Pay-as-you-go plans may use custom hostnames.
Failed to bind the custom hostname |
ERR_NGROK_307 | You must reserve an address for your account before it can be bound.
Failed to bind the address |
ERR_NGROK_308 | The credential ACL policy does not permit binding this address.
Credential ID: |
ERR_NGROK_309 | This address is reserved for another account.
Failed to bind the address |
ERR_NGROK_310 | Only Personal, Pro, Enterprise, and Pay-as-you-go plans may bind reserved addresses.
Failed to bind the address |
ERR_NGROK_311 | This address is allocated for a different region.
Failed to bind the address |
ERR_NGROK_312 | Failed to bind a TLS tunnel for the account |
ERR_NGROK_313 | Custom subdomains are a feature on ngrok's paid plans.
Failed to bind the custom subdomain |
ERR_NGROK_314 | Only Personal, Pro, Enterprise, and Pay-as-you-go plans may bind custom hostnames.
Failed to bind the custom hostname |
ERR_NGROK_315 | Wildcard domains are a feature reserved for ngrok's Enterprise plan.
Failed to bind the wildcard name |
ERR_NGROK_316 | The credential ACL policy does not permit binding this name.
Credential ID: |
ERR_NGROK_317 | You cannot bind the domain |
ERR_NGROK_318 | You must reserve a wildcard domain for your account before it can be bound.
Failed to bind the wildcard domain |
ERR_NGROK_319 | You must reserve a custom hostname for your account before it can be bound.
Failed to bind the domain |
ERR_NGROK_320 | This domain is reserved for another account.
Failed to bind the domain |
ERR_NGROK_321 | Wildcard names must be reserved exactly.
Failed to bind the wildcard domain |
ERR_NGROK_322 | This name is reserved in a different region.
Failed to bind the domain |
ERR_NGROK_323 | You may not run more than |
ERR_NGROK_324 | Your account may not run more than |
ERR_NGROK_326 | Invalid character |
ERR_NGROK_327 | Domain has an invalid character sequence. Valid domains may not contain repeated periods '..'. Failed to bind the domain |
ERR_NGROK_328 | Domain part |
ERR_NGROK_329 | Domain part |
ERR_NGROK_330 | Domain has an invalid character sequence. Valid domains may not contain '--' in positions 3 and 4 unless the domain has a punycode prefix of 'xn--'. Failed to bind the domain |
ERR_NGROK_331 | You may not bind a domain with the TLD |
ERR_NGROK_332 |
|
ERR_NGROK_333 | No tunnel found with the ID |
ERR_NGROK_334 | The tunnel |
ERR_NGROK_335 | The bind cookie you specified is malformed. This usually indicates a bug in the client's protocol implementation. |
ERR_NGROK_336 | Could not find an account while creating this tunnel. This is either an internal server error or you deleted your account. |
ERR_NGROK_337 | The last payment for the |
ERR_NGROK_338 | The account |
ERR_NGROK_339 | Forwarding to a local file:/// URL is only available after you sign up. Sign up at: https://dashboard.ngrok.com/signup If you have already signed up, make sure your authtoken is installed. Your authtoken is available on your dashboard: https://dashboard.ngrok.com/get-started/your-authtoken |
ERR_NGROK_340 | Forwarding to local port 443 or a local https:// URL is only available after you sign up. Sign up at: https://dashboard.ngrok.com/signup If you have already signed up, make sure your authtoken is installed. Your authtoken is available on your dashboard: https://dashboard.ngrok.com/get-started/your-authtoken |
ERR_NGROK_341 | IP Policy with ID |
ERR_NGROK_343 | Endpoint configuration |
ERR_NGROK_344 | Endpoint configuration |
ERR_NGROK_345 | Endpoint configuration
|
ERR_NGROK_346 | Endpoint configuration
|
ERR_NGROK_347 | Domain has invalid punycode: |
ERR_NGROK_348 | Your account is limited to |
ERR_NGROK_349 | Your account is rate limited for adding |
ERR_NGROK_350 | Your account is limited to |
ERR_NGROK_351 | Your account is rate limited for adding |
ERR_NGROK_352 | Unauthenticated sessions are limited to |
ERR_NGROK_353 | Unauthenticated sessions are rate limited for adding |
ERR_NGROK_354 | Failed to bind |
ERR_NGROK_355 | Invalid '_' in domain name. Valid domains may not contain underscores. Failed to bind the domain |
ERR_NGROK_356 | The credential ACL policy does not permit binding random TCP addresses.
Credential ID: |
ERR_NGROK_357 | Labeled tunnels are only available after you sign up. Sign up at: https://dashboard.ngrok.com/signup If you have already signed up, make sure your authtoken is configured. Your authtoken is available on your dashboard: https://dashboard.ngrok.com/get-started/your-authtoken |
ERR_NGROK_358 | Your account doesn't have permission to create labeled tunnels. |
ERR_NGROK_359 | Invalid basic auth credential. Username must not be zero length. |
ERR_NGROK_360 | Invalid basic auth credential. Password must be between |
ERR_NGROK_361 | Invalid circuit breaker configuration, error threshold percentage must be between 0.0 and 1.0 inclusive, was |
ERR_NGROK_362 | Invalid IP restriction configuration, invalid CIDR: |
ERR_NGROK_363 | You must specify a supported provider name. Supported providers: [ |
ERR_NGROK_364 | Webhook provider |
ERR_NGROK_365 | OAuth provider |
ERR_NGROK_366 | You may not authorize more than |
ERR_NGROK_367 | You may not authorize more than |
ERR_NGROK_368 | You may not request more than |
ERR_NGROK_370 | Added request header should be in key:value format, got |
ERR_NGROK_371 | Added response header should be in key:value format, got |
ERR_NGROK_372 |
|
ERR_NGROK_373 |
|
ERR_NGROK_374 |
|
ERR_NGROK_375 | Duplicate 'add' header, |
ERR_NGROK_376 | Exceeded the maximum number of added headers. You specified |
ERR_NGROK_377 | The header beginning with |
ERR_NGROK_378 | The header value for |
ERR_NGROK_379 | The sendgrid verification key is not a base64 encoded ecdsa public key. The following error was encountered while trying to parse it: " |
ERR_NGROK_380 | The resource |
ERR_NGROK_381 | The host |
ERR_NGROK_382 | The account " |
ERR_NGROK_383 | You may not specify an OAuth Client ID without also specifying a Client Secret. Specify both or neither. |
ERR_NGROK_384 | You may not specify an OAuth Client Secret without also specifying a Client ID. Specify both or neither. |
ERR_NGROK_385 | You must specify an OIDC Client ID. |
ERR_NGROK_386 | You must specify an OIDC Client Secret. |
ERR_NGROK_387 | You must specify the OIDC Issuer URL. |
ERR_NGROK_388 | You may not request more than |
ERR_NGROK_389 | You must specify an OAuth client ID and secret for a custom application or neither client ID nor a secret for the ngrok-managed OAuth application. |
ERR_NGROK_390 | You must use your own OAuth application, specifying its client ID and secret, in order to specify scopes. |
ERR_NGROK_391 | You may not request an individual OAuth scope with length greater than |
ERR_NGROK_392 | You may not request an individual OIDC scope with length greater than |
ERR_NGROK_393 | When specifying CIDRs to deny, you must specify at least one CIDR to allow. Otherwise all traffic will be denied. Use 0.0.0.0/0 and ::0/0 to accept all traffic not explicitly blocked by your deny rules. |
ERR_NGROK_394 | Each tunnel must specify either a protocol or labels, but neither was set. |
ERR_NGROK_395 | Bind rules in authtoken ACLs are not supported with labeled tunnels at this time. |
ERR_NGROK_396 | Domain |
ERR_NGROK_397 | Domain |
ERR_NGROK_398 | The |
ERR_NGROK_399 | The credential ACL policy does not permit binding this label.
Credential ID: |
ERR_NGROK_400 | The region you specified, |
ERR_NGROK_401 | Only Personal, Pro, Enterprise, or Pay-as-you-go accounts can reserve domains. Your account can't reserve domains. Upgrade to a paid plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_402 | Only the first part of a reserved domain may be a '*' wildcard. Failed to reserve |
ERR_NGROK_403 | The first subdomain of a wildcard domain must be a single '*' character. Failed to reserve |
ERR_NGROK_404 | You may not reserve names on ngrok.com. Please use an ngrok.io suffix. Failed to reserve |
ERR_NGROK_405 | You may not reserve a domain with the suffix |
ERR_NGROK_406 | Invalid character |
ERR_NGROK_407 | Domain part |
ERR_NGROK_408 | Domain part |
ERR_NGROK_409 | Domain has an invalid character sequence. Valid domains may not contain repeated periods '..'. Failed to reserve |
ERR_NGROK_410 | Domain has an invalid character sequence. Valid domains may not contain '--' in positions 3 and 4 unless the domain has a punycode prefix of 'xn--'. Failed to reserve |
ERR_NGROK_411 | You may not reserve a name on the TLD |
ERR_NGROK_412 | Only Personal, Pro, Enterprise, or Pay-as-you-go accounts can reserve tunnels on custom domains.
Your account cannot reserve tunnels on custom domains ( |
ERR_NGROK_413 | This domain is already reserved for your account. Failed to reserve |
ERR_NGROK_414 | This domain is already reserved for another account. Failed to reserve |
ERR_NGROK_415 | Your account is limited to |
ERR_NGROK_416 | You may not register a wildcard for all |
ERR_NGROK_417 | This wildcard domain would conflict with a domain reserved for another account. Failed to reserve |
ERR_NGROK_418 | Your account is limited to |
ERR_NGROK_419 | Only Enterprise accounts can reserve wildcard domains. Upgrade to an Enterprise plan at https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_420 | A description is limited to |
ERR_NGROK_421 | Metadata is limited to |
ERR_NGROK_422 | The reserved domain name update failed because no values were provided. Specify at least one value. |
ERR_NGROK_423 | The reserved domain name is limited to |
ERR_NGROK_424 | Domain |
ERR_NGROK_425 | Domain |
ERR_NGROK_426 | Domain |
ERR_NGROK_427 | Domain |
ERR_NGROK_428 | You may not assign endpoint configuration |
ERR_NGROK_429 | Domain has invalid punycode: |
ERR_NGROK_430 | Another account is running an active tunnel on the domain |
ERR_NGROK_431 | Your account is limited to |
ERR_NGROK_432 | Your account is rate limited for adding |
ERR_NGROK_433 | Your account is limited to |
ERR_NGROK_434 | Either a certificate or a certificate management policy may be specified, not both |
ERR_NGROK_435 | Invalid authority specified in managed certificate policy. |
ERR_NGROK_436 | The certificate of a reserved domain with a managed certificate policy can not be detached directly, instead the managed certificate policy itself should be detached. |
ERR_NGROK_438 | Invalid '_' in domain name. Valid domains may not contain underscores. Failed to reserve |
ERR_NGROK_439 | The certificate_management_policy field must be null for domains owned by ngrok. |
ERR_NGROK_440 | Uploaded certificates are not allowed for domains owned by ngrok. |
ERR_NGROK_441 | Domain |
ERR_NGROK_442 | Domain |
ERR_NGROK_443 | ACME Challenge |
ERR_NGROK_444 | ACME Challenge |
ERR_NGROK_445 | There was an error looking up the DNS |
ERR_NGROK_446 | The domain |
ERR_NGROK_447 | Managed certificates are not allowed on direct subdomains of |
ERR_NGROK_448 | The domain |
ERR_NGROK_449 | You may only specify one of 'name' or 'domain'. |
ERR_NGROK_450 | You are not allowed to reserve subdomains of |
ERR_NGROK_451 | You are not allowed to change the region of |
ERR_NGROK_455 | This subdomain is covered by |
ERR_NGROK_456 | You are not allowed to specify duplicate regions. Region |
ERR_NGROK_457 | Custom error template URLs are limited to |
ERR_NGROK_500 | The region you specified, |
ERR_NGROK_501 | Only Personal, Pro, Enterprise, or Pay-as-you-go accounts can reserve addresses. Your account can't reserve addresses. Upgrade to a paid plan at https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_502 | Your account is limited to |
ERR_NGROK_503 | No available reserved addresses in region |
ERR_NGROK_504 | A description is limited to |
ERR_NGROK_505 | Metadata is limited to |
ERR_NGROK_506 | The reserved address update failed because no values were provided. Specify at least one value. |
ERR_NGROK_507 | You may not assign endpoint configuration |
ERR_NGROK_508 | Your account is limited to |
ERR_NGROK_509 | Your account is rate limited for adding |
ERR_NGROK_511 | The domain |
ERR_NGROK_512 | The domain |
ERR_NGROK_513 | The domain |
ERR_NGROK_514 | The domain |
ERR_NGROK_600 | Invalid ACL rule. An ACL rule must be '*' or start with 'bind:'. The bind value must match the format of a domain, address, or label. You specified: |
ERR_NGROK_601 | This credential is your tunnel token and cannot be deleted, only rotated.
Credential ID: |
ERR_NGROK_602 | Your account is limited to |
ERR_NGROK_603 | Your account is limited to |
ERR_NGROK_604 | A description is limited to |
ERR_NGROK_605 | Metadata is limited to |
ERR_NGROK_606 | The credentials update failed because no values were provided. Specify at least one value. |
ERR_NGROK_607 | SSH tunnel feature is not enabled on your account. |
ERR_NGROK_608 | Your account is limited to |
ERR_NGROK_609 | The public key |
ERR_NGROK_610 | The public key |
ERR_NGROK_611 | Public key is missing or empty. |
ERR_NGROK_612 | Invalid public key |
ERR_NGROK_613 | Your account is limited to |
ERR_NGROK_614 | Your account is rate limited for adding |
ERR_NGROK_615 | Your account is limited to |
ERR_NGROK_617 | Your account is limited to |
ERR_NGROK_619 | Your account is not authorized to use this ACL rule type. You specified: |
ERR_NGROK_620 | Only Enterprise or Pay-as-you-go plans can use tunnel ACL rules. Your account is not authorized to use tunnel ACL rules. Upgrade to an Enterprise or Pay-as-you-go plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_622 | Only Enterprise or Pay-as-you-go plans can use SSH ACL rules. Your account is not authorized to use SSH ACL rules. Upgrade to an Enterprise or Pay-as-you-go plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_627 | The auth token is already owned by a user and cannot be re-assigned ownership. |
ERR_NGROK_628 | The API key is already owned by a user and cannot be re-assigned ownership. |
ERR_NGROK_629 | The SSH public key is already owned by a user and cannot be re-assigned ownership. |
ERR_NGROK_630 | You must be an admin to set credential ownership. |
ERR_NGROK_631 | You may specify owner_id or owner_email, but not both. |
ERR_NGROK_632 | You may specify owner or membership, but not both. |
ERR_NGROK_633 | Your account is not authorized to specify credential ownership. |
ERR_NGROK_634 | No credential owner could be determined. |
ERR_NGROK_635 | API access requires that the owner of the API key has write privileges. |
ERR_NGROK_636 | The credential owner is marked as inactive on the account. |
ERR_NGROK_637 | This credential cannot be deleted because it is the default authtoken tied to |
ERR_NGROK_638 | Your account is not allowed to create credentials with pre-computed tokens. To create a new credential, omit pre-computed token field and let ngrok generate one for you. Its value will be available as part of the response. |
ERR_NGROK_702 | Too many connections! The tunnel session |
ERR_NGROK_703 | Too many connections! The account hosting this endpoint has violated the rate-limit policy of |
ERR_NGROK_708 | This URL has expired. Please sign up for a free ngrok account to create URLs that do not expire. You can also restart the ngrok agent which will create a new URL that will expire after the same amount of time. |
ERR_NGROK_714 | This ngrok account has reached its simultaneous connections limit. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_715 | You have exceeded your limit on connections per minute. This limit will reset within 1 minute. If you expect to continually exceed these limits, please reach out to support (support@ngrok.com) |
ERR_NGROK_716 | This unauthenticated ngrok session has reached its simultaneous connections limit. Please sign up for a free account at https://ngrok.com for a higher limit. |
ERR_NGROK_717 | This unauthenticated ngrok session has reached its connection rate limit. Please sign up for a free account at https://ngrok.com for a higher limit. |
ERR_NGROK_718 | Your account is rate limited to |
ERR_NGROK_719 | Unauthenticated sessions are rate limited to |
ERR_NGROK_720 | Your account is rate limited to |
ERR_NGROK_721 | Unauthenticated sessions are rate limited to |
ERR_NGROK_722 | internal server error |
ERR_NGROK_724 | No backend is available to serve requests for endpoint |
ERR_NGROK_725 | This ngrok account has reached its network bandwidth limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_726 | This ngrok account has reached its connections limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_727 | This ngrok account has reached its HTTP requests limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_728 | This ngrok account has reached its HTTP connections limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_729 | This ngrok account has reached its TCP connections limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_730 | This ngrok account has reached its TLS connections limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_731 | This ngrok account has reached its HTTPS connections limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_732 | This ngrok account has reached its traffic policy request limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_733 | This ngrok account has reached its traffic policy connection limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_734 | You have exceeded your limit of |
ERR_NGROK_735 | This ngrok account has reached its Advanced traffic policy request limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_736 | This ngrok account has reached its Basic traffic policy request limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_737 | This ngrok account has reached its Enterprise traffic policy request limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_738 | This ngrok account has reached its Advanced traffic policy request limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_739 | This ngrok account has reached its Basic traffic policy connection limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_740 | This ngrok account has reached its Enterprise traffic policy connection limit for the month. Please log into https://dashboard.ngrok.com to view your options. |
ERR_NGROK_741 | Internal server error. |
ERR_NGROK_800 | Unknown stream type: |
ERR_NGROK_801 | The request payload you specified is not valid.
This usually indiciates a bug in the client's protocol implementation.
The parsing error encountered was:
|
ERR_NGROK_802 | internal server error |
ERR_NGROK_803 | The server process is shutting down and refusing new requests. |
ERR_NGROK_804 | This ngrok agent does not support remote restarting: |
ERR_NGROK_805 | This ngrok agent does not support remote stopping: |
ERR_NGROK_806 | This ngrok agent does not support remote updating: |
ERR_NGROK_807 | The remote ngrok agent failed to stop because of an error: |
ERR_NGROK_808 | The remote ngrok agent failed to restart because of an error: |
ERR_NGROK_809 | The remote ngrok agent failed to update because of an error: |
ERR_NGROK_810 | There was a networking error while trying to send this operation to the ngrok agent or trying to read the response. This usually indicates that the ngrok agent was in the process of shutting down or reconnecting, but it could also result from a networking timeout or failure. It is possible, but unlikely, that the operation succeeded. |
ERR_NGROK_811 | Could not negotiate a protocol version. Requested: " |
ERR_NGROK_812 | Your request exceeded the maximum size of |
ERR_NGROK_813 | Your message " |
ERR_NGROK_1000 | Your billing address is too long: |
ERR_NGROK_1001 | Your tax ID is too long: |
ERR_NGROK_1002 | Your account is limited to |
ERR_NGROK_1003 | The billing email |
ERR_NGROK_1004 | The billing email is too long: |
ERR_NGROK_1005 | The billing email address |
ERR_NGROK_1006 | There was a problem with your credit card: |
ERR_NGROK_1007 | Your subscription was updated, but we failed to charge your card: |
ERR_NGROK_1008 | Your account is limited to |
ERR_NGROK_1010 | The email address " |
ERR_NGROK_1011 | Your account is currently past due. You may only enter a payment method to pay your overdue invoice or switch to the free plan. |
ERR_NGROK_1012 | You may not purchase fewer licenses than users. Your account currently has |
ERR_NGROK_1013 | Yearly plans can only be downgraded or canceled in their final month. Try again after |
ERR_NGROK_1014 | You may only purchase one license product at a time. |
ERR_NGROK_1015 | You are on an old custom subscription. Please contact support@ngrok.com for help with changing your subscription. |
ERR_NGROK_1016 | Cannot charge customer that has no active payment source. |
ERR_NGROK_1017 | Accounts in bad standing may only switch to a free plan or update their payment method. |
ERR_NGROK_1018 | You may only purchase |
ERR_NGROK_1019 | The |
ERR_NGROK_1020 | Addon selections for |
ERR_NGROK_1021 | The billing email address |
ERR_NGROK_1022 | Your invoice tax ID type |
ERR_NGROK_1023 | Your invoice tax ID country |
ERR_NGROK_1024 | Your invoice billing address country is too long: |
ERR_NGROK_1025 | Your invoice billing address state is too long: |
ERR_NGROK_1026 | Your invoice billing address city is too long: |
ERR_NGROK_1027 | Your invoice billing address line1 is too long: |
ERR_NGROK_1028 | Your invoice billing address line2 is too long: |
ERR_NGROK_1029 | Your invoice billing address postal code is too long: |
ERR_NGROK_1030 | Your invoice billing address name is too long: |
ERR_NGROK_1031 | Tax information is incomplete: Missing Type for Tax ID. Please update or remove your tax information before making any changes to your account's subscription. |
ERR_NGROK_1032 | Missing Tax ID for Type. You must supply both the Tax ID and its Type or remove both |
ERR_NGROK_1100 | No public keys were sent for this SSH tunnel. Configure SSH with public key authentication and register your keys at https://dashboard.ngrok.com/ssh-keys Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription to enable SSH tunnels. |
ERR_NGROK_1101 | Too many public keys sent for this SSH tunnel (sent |
ERR_NGROK_1102 | Could not find your account based on the public keys sent for this SSH tunnel. Anonymous SSH tunneling is not supported. Check your SSH configuration and register your keys at https://dashboard.ngrok.com/ssh-keys |
ERR_NGROK_1103 | The account |
ERR_NGROK_1104 | Multiplexing is not supported with SSH tunneling |
ERR_NGROK_1105 | Only one port forward per tunneling session is supported. |
ERR_NGROK_1106 | Could not find |
ERR_NGROK_1107 | No tunnel type specified. The SSH command specifies the type of tunnel to create, one of 'http', 'tls', or 'tcp'. |
ERR_NGROK_1108 |
|
ERR_NGROK_1109 |
|
ERR_NGROK_1110 | Error while parsing the |
ERR_NGROK_1111 | Timeout while waiting for SSH session |
ERR_NGROK_1112 | Timeout while waiting for port forward request. Use 'ssh -R ...' option to specify your port forwarding. |
ERR_NGROK_1113 | Cannot use bind port |
ERR_NGROK_1114 | Cannot use bind address '-R |
ERR_NGROK_1115 | Cannot request a custom TCP port '-R |
ERR_NGROK_1116 | Cannot request a custom bind port '-R |
ERR_NGROK_1117 | Cannot request a random port with a custom bind address |
ERR_NGROK_1118 | Cannot use binding address '-R |
ERR_NGROK_1119 | Cannot use binding address '-R |
ERR_NGROK_1120 | Cannot use '-hostname= |
ERR_NGROK_1121 | SSH sessions do not support update. |
ERR_NGROK_1122 | SSH sessions do not support restart. |
ERR_NGROK_1123 | Tunnel '-proxy-proto= |
ERR_NGROK_1200 | Authorized account's primary email |
ERR_NGROK_1202 | You can't enable Google OAuth without first connecting a Google Apps login. |
ERR_NGROK_1203 | You can't enable Google OAuth because your connected Google login does not have a Google Apps domain. |
ERR_NGROK_1204 | You can't delete your payment method while you have an active subscription. |
ERR_NGROK_1205 | You failed to solve the CAPTCHA, please try again. |
ERR_NGROK_1207 | Cannot switch to an account you are not a member of. |
ERR_NGROK_1208 | You failed to solve the CAPTCHA, please try again. |
ERR_NGROK_1210 | Invalid subscription interval |
ERR_NGROK_1211 | Warning: Your IP does not match the IP Policy for this Account. When IP Restrictions are enforced you will not be able to access the dashboard. Please authenticate from an IP in the correct range or update your IP Restrictions. |
ERR_NGROK_1212 | Your IP does not match the IP Policy for this Account. Please authenticate from an IP in the correct range or update your IP Restrictions from the ngrok dashboard. https://dashboard.ngrok.com/ip-restrictions |
ERR_NGROK_1213 | A new version of the ngrok dashboard is required to continue. Please refresh the page to update. |
ERR_NGROK_1214 | Your account is rate limited to |
ERR_NGROK_1215 | The user |
ERR_NGROK_1216 | The user |
ERR_NGROK_1217 | The user |
ERR_NGROK_1218 | The user |
ERR_NGROK_1219 | The user |
ERR_NGROK_1220 | The user |
ERR_NGROK_1221 | Refusing to perform an account delete operation because you are using the dashboard with a different active account than the one you requested deletion for. |
ERR_NGROK_1222 | You are not a member of any account. |
ERR_NGROK_1223 | You are logged out, please log back in. |
ERR_NGROK_1224 | You are no longer a member of the current account. |
ERR_NGROK_1225 | You must accept the terms of service and privacy policy to sign up for ngrok. |
ERR_NGROK_1226 | You are disallowed from creating an ngrok account due to violation of the terms of service. |
ERR_NGROK_1227 | The number of login attempts with this email has been exceeded, please try again later. |
ERR_NGROK_1228 | You are no longer an active member of the current account. |
ERR_NGROK_1229 | The resource you are attempting to access requires MFA, please authenticate via a second factor. |
ERR_NGROK_1230 | We do not allow sign ups from your location. Your location was determined using your IP address. |
ERR_NGROK_1231 | The email address |
ERR_NGROK_1232 | We do not allow sign ups from anonymous proxies such as Tor. |
ERR_NGROK_1400 | The IP Policy update failed because no values were provided. Specify at least one value |
ERR_NGROK_1401 | The IP Policy Rule update failed because no values were provided. Specify at least one value |
ERR_NGROK_1402 | IP Policy not found |
ERR_NGROK_1404 | IP Policy Rule not found |
ERR_NGROK_1405 | Required parameter is missing. Please specify |
ERR_NGROK_1406 | Invalid CIDR: |
ERR_NGROK_1407 | IP Policy with name |
ERR_NGROK_1408 | IP Policy Rule with CIDR |
ERR_NGROK_1409 | IP Policy Rule CIDR |
ERR_NGROK_1410 | Your account is limited to a maximum of |
ERR_NGROK_1411 | Your account is limited to a maximum of |
ERR_NGROK_1412 | Only Pro, Enterprise, or Pay-as-you-go accounts can use per-tunnel IP policies. Your account is not authorized to use per-tunnel IP policies. Upgrade to a Pro, Enterprise, or Pay-as-you-go plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_1413 | IP Policy Rule is missing a network mask. Consider using |
ERR_NGROK_1414 | The provided ip_policy_id is invalid. Please check the value given with your request. |
ERR_NGROK_1415 | Your account is limited to |
ERR_NGROK_1417 | Your account is limited to |
ERR_NGROK_1419 | Cannot delete only rule ( |
ERR_NGROK_1420 | Cannot delete IP Policy ( |
ERR_NGROK_1421 | The IP Policy Rule description exceeds the maximum length of |
ERR_NGROK_1422 | An IP Policy Rule must have an 'action' of either 'allow' or 'deny'. |
ERR_NGROK_1423 | An action should now be specified on the IP Policy Rule, not IP Policy. Please contact ngrok support if you need additional time to migrate. |
ERR_NGROK_1500 | Maintenance in progress, operations for some resources are read-only |
ERR_NGROK_1501 | Maintenance in progress, some operations are unavailable |
ERR_NGROK_1600 | Endpoint configuration not found |
ERR_NGROK_1601 | Invalid endpoint configuration ID |
ERR_NGROK_1602 | Invalid endpoint configuration request |
ERR_NGROK_1607 | The IP Policy ID |
ERR_NGROK_1608 | Endpoint Configurations are deprecated. Please use Cloud Edges instead. |
ERR_NGROK_1609 | Your account is limited to a maximum of |
ERR_NGROK_1611 | Invalid endpoint configuration, circuit breaker error threshold percentage must be between 0.0 and 1.0 inclusive, was |
ERR_NGROK_1612 | The auth provider |
ERR_NGROK_1613 | The endpoint configuration exceeds the max number of ip policies. You specified |
ERR_NGROK_1614 | The endpoint configuration TLS CA certificate size exceeds the max. You specified |
ERR_NGROK_1615 | The endpoint configuration exceeds the max number of headers. You specified |
ERR_NGROK_1616 | Invalid endpoint configuration, circuit breaker tripped duration must be greater than 0, was |
ERR_NGROK_1617 | Invalid endpoint configuration, circuit breaker rolling window must be greater than 0, was |
ERR_NGROK_1618 | Invalid endpoint configuration, circuit breaker num buckets must be greater than 0 and less than |
ERR_NGROK_1619 | The endpoint configuration could not be deleted because it is still referenced by at least one reserved domain or reserved address. |
ERR_NGROK_1620 | The endpoint configuration must specify a type. |
ERR_NGROK_1621 | The module |
ERR_NGROK_1622 |
|
ERR_NGROK_1623 |
|
ERR_NGROK_1624 |
|
ERR_NGROK_1625 | You must specify at least one IP policy in the IP Policy module. |
ERR_NGROK_1626 | SNS webhook validation does not accept a secret. |
ERR_NGROK_1627 | Webhook validation for |
ERR_NGROK_1628 | There were validation errors while saving the endpoint configuration: |
ERR_NGROK_1629 | You must specify a supported provider name. Supported providers: [ |
ERR_NGROK_1630 | Webhook provider |
ERR_NGROK_1631 | Endpoint Configurations are deprecated. Please use Cloud Edges instead. |
ERR_NGROK_1632 | You may not configure the TLS termination parameter |
ERR_NGROK_1633 | Invalid endpoint configuration, unmanaged provider configurations must specify a client ID and a client secret. |
ERR_NGROK_1634 | Invalid endpoint configuration, custom OAuth scopes on a managed OAuth application are not allowed. Define a custom OAuth application to use custom scopes. |
ERR_NGROK_1635 | Invalid endpoint configuration, OAuth auth check interval must be at least |
ERR_NGROK_1636 | Invalid endpoint configuration, OAuth may only have one provider configuration but multiple are defined: [ |
ERR_NGROK_1637 | Invalid endpoint configuration, OAuth does not define any provider configurations but one is required. |
ERR_NGROK_1638 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1639 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1640 | Invalid endpoint configuration, OAuth GitHub Teams must be listed as either numerical ids or in the format 'org_slug/team_slug', |
ERR_NGROK_1641 | Endpoint Configurations are deprecated. Please use Cloud Edges instead. |
ERR_NGROK_1642 | Invalid endpoint configuration, OAuth cookie prefix |
ERR_NGROK_1643 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1644 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1645 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1646 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1647 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1648 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1649 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1650 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1651 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1652 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1653 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1654 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1655 | Invalid endpoint configuration, OAuth provider |
ERR_NGROK_1656 | The endpoint configuration exceeds the maximum number of OAuth scopes. You specified |
ERR_NGROK_1657 | The endpoint configuration exceeds the maximum number of OAuth Github teams. You specified |
ERR_NGROK_1658 | The endpoint configuration exceeds the maximum number of OAuth Github orgs. You specified |
ERR_NGROK_1659 | The endpoint configuration exceeds the maximum number of OAuth Google groups. You specified |
ERR_NGROK_1660 | The endpoint configuration exceeds the maximum number of OAuth emails. You specified |
ERR_NGROK_1661 | The endpoint configuration exceeds the maximum number of OAuth domains. You specified |
ERR_NGROK_1662 | The endpoint configuration specifies the following modules which may not be enabled when TLS is not terminated: |
ERR_NGROK_1667 | Invalid endpoint configuration, email addresses must be lowercase but |
ERR_NGROK_1668 | Invalid endpoint configuration, email domains must be lowercase but |
ERR_NGROK_1669 | Duplicate 'add' header, |
ERR_NGROK_1670 | Your account is limited to |
ERR_NGROK_1672 | The CA ID |
ERR_NGROK_1673 | Description is limited to |
ERR_NGROK_1674 | Metadata is limited to |
ERR_NGROK_1675 | The Mutual TLS configurations exceeds the limit of |
ERR_NGROK_1679 | The endpoint configuration specifies conflicting authentication modules. Only one of SAML, OIDC, OAuth or Basic Auth may be enabled. |
ERR_NGROK_1680 | The SAML metadata exceeds the maximum length of |
ERR_NGROK_1681 | You must specify only the SAML IdP metadata or the SAML IdP metadata URL, but not both. |
ERR_NGROK_1682 | Failed to connect to IdP metadata URL |
ERR_NGROK_1683 | Failed to parse the SAML IdP metadata: |
ERR_NGROK_1684 | Received unexpected status code |
ERR_NGROK_1685 | Failed to parse the SAML IdP metadata fetched from URL |
ERR_NGROK_1686 | Encountered an error while reading the response body from the IdP metadata URL |
ERR_NGROK_1687 | The specified OIDC issuer has a maximum length of 255 bytes. The specified value is |
ERR_NGROK_1688 | The OIDC issuer property is required. |
ERR_NGROK_1689 | The OIDC Client ID property is required. |
ERR_NGROK_1690 | The OIDC Client Secret property is required. |
ERR_NGROK_1691 | One of the SAML IdP Metadata or IdP Metadata URL properties must be specified. |
ERR_NGROK_1692 | Invalid endpoint configuration, session inactivity timeout cannot be more than one year, was |
ERR_NGROK_1693 | " |
ERR_NGROK_1694 | Mutual TLS at edge requires TLS termination at edge. |
ERR_NGROK_1695 | No PEM data found in provided mutual TLS CA. |
ERR_NGROK_1696 | Certificate provided for mutual TLS is not a valid CA. |
ERR_NGROK_1697 | The header beginning with |
ERR_NGROK_1698 | The header value for |
ERR_NGROK_1699 | The sendgrid verification key is not a base64 encoded ecdsa public key. The following error was encountered while trying to parse it: " |
ERR_NGROK_1700 | Only Enterprise accounts can use session operations. Your account is not authorized to use session operations. Upgrade to an Enterprise or Pay-as-you-go plan at https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_1701 | Only Enterprise accounts can stop or restart the agent. Your account is not authorized to stop or restart the agent. Upgrade to an Enterprise or Pay-as-you-go plan at https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_1702 | Only Enterprise or Pay-as-you-go accounts can update the agent. Your account is not authorized to update the agent. Upgrade to an Enterprise or Pay-as-you-go plan at https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_1800 | You have reached the maximum of |
ERR_NGROK_1801 | Invalid IP Restriction. The policy |
ERR_NGROK_1802 | Only one IP Restriction is allowed per type. Consider either deleting the existing |
ERR_NGROK_1803 | The provided IP Restriction type " |
ERR_NGROK_1804 | An IP Restriction must specify at least one IP Policy. |
ERR_NGROK_1805 | Only Pro or Enterprise accounts can use dashboard IP restrictions.
Your account is not authorized to use dashboard IP restrictions. |
ERR_NGROK_1806 | Only Pro or Enterprise accounts can use API IP restrictions.
Your account is not authorized to use API IP restrictions. |
ERR_NGROK_1807 | Only Pro or Enterprise accounts can use agent IP restrictions.
Your account is not authorized to use agent IP restrictions. |
ERR_NGROK_1808 | Only Pro, Enterprise, or Pay-as-you-go accounts can use endpoints IP restrictions.
Your account is not authorized to use endpoints IP restrictions. |
ERR_NGROK_1900 | The provided certificate is in an unknown or unsupported format. The error encountered while parsing was: " |
ERR_NGROK_1901 | No PEM-encoded private key was found in the creation request. |
ERR_NGROK_1902 | The provided private key is encrypted. |
ERR_NGROK_1903 | The provided private key is in an unknown or unsupported format. |
ERR_NGROK_1904 | Your account can't upload custom TLS certificates. |
ERR_NGROK_1905 | Your account can't use managed TLS certificates. |
ERR_NGROK_1906 | The domain |
ERR_NGROK_1907 | The ip |
ERR_NGROK_1908 | Invalid authority |
ERR_NGROK_1909 | Invalid private key type |
ERR_NGROK_1910 | The provided PEM data contains a non-zero number of headers, which are not allowed. |
ERR_NGROK_1911 | The provided data is a valid PEM, but it has an unexpected type: |
ERR_NGROK_1912 | The upload contained |
ERR_NGROK_1913 | The uploaded certificate's x509 Basic Constraints did not mark it as a certificate authority (see RFC 5280, 4.2.1.9). |
ERR_NGROK_1914 | The description is limited to |
ERR_NGROK_1915 | Metadata is limited to |
ERR_NGROK_1916 | The description is limited to |
ERR_NGROK_1917 | Metadata is limited to |
ERR_NGROK_1918 | Your account is not allowed to upload certificate authorities. |
ERR_NGROK_1919 | No certificate PEM data was sent. |
ERR_NGROK_1920 | The certificate data could not be parsed as PEM. Certificate data: " |
ERR_NGROK_1921 | The uploaded certificate PEM data exceeds the maximum length limit of |
ERR_NGROK_1922 | No PEM-encoded certificate was found in the creation request. |
ERR_NGROK_1923 | The provided certificate and private key do not match each other. |
ERR_NGROK_1924 | The provided private key is actually a certificate. |
ERR_NGROK_1925 | The provided certificate is actually a private key. |
ERR_NGROK_1926 | The uploaded certificate bundle contained the following certificates in this order: [ |
ERR_NGROK_1927 | The domain |
ERR_NGROK_1929 | Invalid nameserver count. There should be |
ERR_NGROK_1930 | Nameservers are not set up correctly for |
ERR_NGROK_1934 | Got error |
ERR_NGROK_1935 |
|
ERR_NGROK_1936 | " |
ERR_NGROK_1937 | The description is limited to |
ERR_NGROK_1938 | Metadata is limited to |
ERR_NGROK_1939 | Invalid key size |
ERR_NGROK_1940 | Key size is supported only with a key type of "rsa", but the specified key type was " |
ERR_NGROK_1941 | Invalid elliptic curve " |
ERR_NGROK_1942 | Elliptic curve is supported only with a key type of "ecdsa", but the specified key type was " |
ERR_NGROK_1943 | The SSH CA Certificate duration must be greater than zero; got duration of |
ERR_NGROK_1945 | The description is limited to |
ERR_NGROK_1946 | Metadata is limited to |
ERR_NGROK_1947 | The description is limited to |
ERR_NGROK_1948 | Metadata is limited to |
ERR_NGROK_1949 | The SSH CA |
ERR_NGROK_1950 | Certificates are not supported for public keys of type |
ERR_NGROK_1951 | The SSH CA |
ERR_NGROK_1952 | The public key to sign in the certificate is required, but no public key was specified. |
ERR_NGROK_1953 | Your account is not allowed to use SSH certificates. |
ERR_NGROK_1954 | Your account is limited to |
ERR_NGROK_1956 | Your account is limited to |
ERR_NGROK_1958 | Your account is limited to |
ERR_NGROK_1960 | Your account is limited to |
ERR_NGROK_1962 | SSH User Certificate duration must be greater than zero; got duration of |
ERR_NGROK_1963 | SSH Host Certificate duration must be greater than zero; got duration of |
ERR_NGROK_1964 | Can't delete SSH CA |
ERR_NGROK_1965 | The certificate |
ERR_NGROK_1966 | The certificate |
ERR_NGROK_2032 | Webhook Validation middleware requires a secret for |
ERR_NGROK_2062 | Paths given in HTTPMux rules must be either empty or absolute. Perhaps you meant to specify '/ |
ERR_NGROK_2063 | The method |
ERR_NGROK_2065 | HTTPMux must have at least one rule. |
ERR_NGROK_2067 | Too many rules given to HTTPMux. You provided |
ERR_NGROK_2069 | The method ( |
ERR_NGROK_2070 | The path specified in an HTTPMux rule is too long. The path provided has |
ERR_NGROK_2071 | The path specified in an HTTPMux rule is unsupported or otherwise invalid. |
ERR_NGROK_2087 | The sendgrid verification key is not a base64 encoded ecdsa public key. The following error was encountered while trying to parse it: " |
ERR_NGROK_2089 | Found duplicate routing rule. Each rule must be unique. |
ERR_NGROK_2090 | The user agent filter regular expression |
ERR_NGROK_2200 | Invalid policy expression.
|
ERR_NGROK_2201 | Invalid policy action type |
ERR_NGROK_2202 | Action type |
ERR_NGROK_2203 | Failed to parse the configuration for policy action type |
ERR_NGROK_2204 | Configuration for policy action type |
ERR_NGROK_2205 | Policy action type |
ERR_NGROK_2206 | A policy must define at least one action. |
ERR_NGROK_2207 | Policy action type |
ERR_NGROK_2208 | Failed to parse configuration for |
ERR_NGROK_2209 | Failed to parse configuration for |
ERR_NGROK_2210 | Failed to parse configuration for |
ERR_NGROK_2211 | Failed to parse configuration for |
ERR_NGROK_2212 | Failed to parse configuration for |
ERR_NGROK_2213 | Failed to parse configuration for |
ERR_NGROK_2214 | Failed to parse configuration for compress: contained an invalid algorithm: |
ERR_NGROK_2215 | Failed to parse configuration for |
ERR_NGROK_2216 | Invalid IP Policy Reference(s): |
ERR_NGROK_2217 | Invalid CIDR(s): |
ERR_NGROK_2218 | Too many entries for |
ERR_NGROK_2219 |
|
ERR_NGROK_2221 | Invalid configuration for |
ERR_NGROK_2222 | Invalid configuration for |
ERR_NGROK_2223 | Invalid configuration for |
ERR_NGROK_2224 | Invalid configuration for action |
ERR_NGROK_2225 | Invalid configuration for |
ERR_NGROK_2226 | Invalid configuration for |
ERR_NGROK_2227 | Invalid configuration for |
ERR_NGROK_2228 | Invalid configuration for |
ERR_NGROK_2229 | Failed to validate Traffic Policy for unknown protocol |
ERR_NGROK_2230 | Invalid Traffic Policy phase |
ERR_NGROK_2231 | Invalid configuration for |
ERR_NGROK_2232 | Failed to resolve validated configuration for policy action type |
ERR_NGROK_2233 | Failed to compile resolved configuration for policy action type |
ERR_NGROK_2234 | Invalid configuration for |
ERR_NGROK_2235 | The traffic policy provided is not guaranteed to handle traffic. Ensure traffic always results in an action, e.g. custom response or forward action. |
ERR_NGROK_2236 | The traffic policy was not able to be parsed:
|
ERR_NGROK_2237 | Invalid configuration for |
ERR_NGROK_2238 | Failed to resolve interpolated CEL expression. The expression was: |
ERR_NGROK_2239 | Invalid policy: Only one auth action allowed per endpoint. |
ERR_NGROK_2240 | Invalid configuration for |
ERR_NGROK_2241 | Invalid configuration for |
ERR_NGROK_2242 | Invalid configuration for |
ERR_NGROK_2243 | Invalid configuration for |
ERR_NGROK_3002 | Error performing TLS handshake: |
ERR_NGROK_3003 | This client does not support TLS SNI, but the endpoint's TLS configuration requires SNI. See https://ngrok.com/docs/cloud-edge/edges/tls#compatible-clients |
ERR_NGROK_3004 | ngrok gateway error The server returned an invalid or incomplete HTTP response. |
ERR_NGROK_3005 | ngrok gateway timeout A connection to the server not be established. |
ERR_NGROK_3006 | ngrok gateway error The server refused our connection |
ERR_NGROK_3007 | ngrok gateway error |
ERR_NGROK_3008 | ngrok gateway error None of the configured backends responded in time |
ERR_NGROK_3009 | ngrok gateway error Received an HTTP network error (status code 0) from a backend |
ERR_NGROK_3010 | ngrok gateway error
Received an HTTP response with unknown status code |
ERR_NGROK_3100 | Your session has expired due to age.
Refresh this page or use the link below to log back in with |
ERR_NGROK_3101 | We lack permission to retrieve your data from |
ERR_NGROK_3102 |
|
ERR_NGROK_3103 |
|
ERR_NGROK_3104 | The email " |
ERR_NGROK_3105 | You lack the required permission to use this site. Contact the owner to obtain permission and then refresh this page. |
ERR_NGROK_3106 | The initial information required to authenticate with |
ERR_NGROK_3107 | The state parameter used to validate your request is missing. Please close this page and try again. |
ERR_NGROK_3108 | The state parameter used to validate your request cannot be read. Please close this page and try again. |
ERR_NGROK_3109 |
|
ERR_NGROK_3110 | The email permission from |
ERR_NGROK_3111 | All requested permissions with |
ERR_NGROK_3112 |
|
ERR_NGROK_3113 |
|
ERR_NGROK_3114 | In order to continue, you must authorize this application's access to |
ERR_NGROK_3115 | The redirect_uri configured for this application is not properly configured or whitelisted with |
ERR_NGROK_3116 |
|
ERR_NGROK_3117 | The initial link used to authorize with |
ERR_NGROK_3118 |
|
ERR_NGROK_3119 | Logging in with |
ERR_NGROK_3120 | The state parameter required to finish authorization with |
ERR_NGROK_3121 | The nonce cookie required to finish authorization with |
ERR_NGROK_3122 | The access code from |
ERR_NGROK_3123 | The access code from |
ERR_NGROK_3124 | The state parameter required to finish authorization with |
ERR_NGROK_3125 |
|
ERR_NGROK_3126 |
|
ERR_NGROK_3127 |
|
ERR_NGROK_3150 | An error occurred when retrieving your session. Please refresh the page to log in and try again. |
ERR_NGROK_3151 |
|
ERR_NGROK_3152 | An invalid request was sent to |
ERR_NGROK_3160 | An unexpected error occurred when communicating with |
ERR_NGROK_3161 |
|
ERR_NGROK_3162 |
|
ERR_NGROK_3163 | An error occurred when finishing authorization with |
ERR_NGROK_3164 | An error occurred when authorizing with |
ERR_NGROK_3165 |
|
ERR_NGROK_3166 |
|
ERR_NGROK_3167 |
|
ERR_NGROK_3200 | Tunnel |
ERR_NGROK_3202 | Circuit breaker tripped |
ERR_NGROK_3203 | Request blocked by IP Policy |
ERR_NGROK_3204 | Request failed webhook verification |
ERR_NGROK_3205 | Request blocked by Endpoints IP Restriction |
ERR_NGROK_3206 | Expected a websocket request with a "Connection: upgrade" header but did not receive one. |
ERR_NGROK_3208 | The ngrok account that was hosting this webpage has been banned for violation of ngrok's Terms of Service. If you're seeing this page instead of the one you were expecting, ngrok has most likely blocked a phishing attack targeting you. If you did enter any sensitive information before seeing this notice, please contact the real site by directly entering their URL in your browser. Learn more about how to protect yourself from phishing scams: https://consumer.ftc.gov/articles/how-recognize-and-avoid-phishing-scams |
ERR_NGROK_3209 | Tunnel not found |
ERR_NGROK_3210 | Error forwarding the connection to the ngrok agent |
ERR_NGROK_3211 | The server does not authorize requests from your user-agent |
ERR_NGROK_3212 | Tunnel |
ERR_NGROK_3300 | URL "state" parameter is invalid |
ERR_NGROK_3301 | URL "state" parameter is expired. |
ERR_NGROK_3302 | URL "state" parameter is invalid. |
ERR_NGROK_3303 | URL "state" parameter is invalid. |
ERR_NGROK_3304 | URL "state" parameter is invalid. |
ERR_NGROK_3305 | This request has expired. Please try again. |
ERR_NGROK_3306 | URL "state" parameter is invalid. |
ERR_NGROK_3307 | URL "state" parameter is invalid. |
ERR_NGROK_3308 | URL "state" parameter is invalid. |
ERR_NGROK_3309 | The route match type |
ERR_NGROK_3310 | URL "state" parameter is invalid. |
ERR_NGROK_3311 | URL "state" parameter is invalid. |
ERR_NGROK_3312 | URL "state" parameter is invalid. |
ERR_NGROK_3313 | Invalid Auth Cookie Domain: |
ERR_NGROK_3401 | Your request lacks valid credentials. |
ERR_NGROK_3403 | You are forbidden from making this request. |
ERR_NGROK_3406 | Token could not be found in request. |
ERR_NGROK_3408 | Configured HTTP Header |
ERR_NGROK_3411 | Failed to parse JSON body. |
ERR_NGROK_3412 | Failed to parse form. |
ERR_NGROK_3413 | Configured prefix |
ERR_NGROK_3414 | Failed to read content-type header. |
ERR_NGROK_3415 | Tokens in body not supported for HTTP method |
ERR_NGROK_3416 | Token could not be parsed, possibly malformed. |
ERR_NGROK_3422 | Failed to fetch JWKS. |
ERR_NGROK_3501 | ForwardInternal may only forward through |
ERR_NGROK_4001 | Plan |
ERR_NGROK_4003 | Account name must not be empty. |
ERR_NGROK_4004 | Account name exceeds max length, |
ERR_NGROK_4005 | Another account is already configured with the GSuite domain |
ERR_NGROK_4011 | Your password must be at least |
ERR_NGROK_4012 | Your account does not have access to |
ERR_NGROK_4013 | You may not create a new account because you are already a member of the free account " |
ERR_NGROK_4014 | The account |
ERR_NGROK_4015 | The account |
ERR_NGROK_4016 | You may not create a new account because another account you were the administrator of was suspended. Contact support@ngrok.com if you believe this is an error. |
ERR_NGROK_4017 | You may not create a new account because another account you were the administrator of was banned for violation of the terms of service. Contact support@ngrok.com if you believe this is an error. |
ERR_NGROK_4018 | Usage of ngrok requires a verified account and authtoken. Sign up for an account: https://dashboard.ngrok.com/signup Install your authtoken: https://dashboard.ngrok.com/get-started/your-authtoken |
ERR_NGROK_4019 | This account cannot be deleted because it has an active billing subscription. Please contact support@ngrok.com for help deleting this account. |
ERR_NGROK_4020 | Your password must be less then |
ERR_NGROK_4021 | This account cannot be deleted because it has an unpaid invoice. Please contact support@ngrok.com for help deleting this account. |
ERR_NGROK_4022 | You do not have permission to change the observability capture settings for this account. Please contact an admin for this account to change these settings. |
ERR_NGROK_4023 | Your account does not have access to |
ERR_NGROK_4100 | The email or password you entered is not valid. |
ERR_NGROK_4101 | A user with the email address |
ERR_NGROK_4103 |
|
ERR_NGROK_4104 | User name must not be empty. |
ERR_NGROK_4105 | User name exceeds max length, |
ERR_NGROK_4106 | Your user |
ERR_NGROK_4107 | Your user |
ERR_NGROK_4108 | Sign ups are disallowed for the email provider " |
ERR_NGROK_4109 | Bot name must not be empty. |
ERR_NGROK_4110 | Bot name exceeds max length, |
ERR_NGROK_4111 | You must be an admin to create, update, or delete Bots. |
ERR_NGROK_4112 | Bot names must be unique within an account. |
ERR_NGROK_4114 | The email domain " |
ERR_NGROK_4115 | The email domain " |
ERR_NGROK_4116 | The domain of the email entered is registered under a domain control and must signup via SSO |
ERR_NGROK_4117 | The email address |
ERR_NGROK_4118 | Sign ups are disallowed for the email provided " |
ERR_NGROK_4200 | You may not delete all or your logins, you must have at least one. |
ERR_NGROK_4201 | This |
ERR_NGROK_4300 | No user with the email address |
ERR_NGROK_4301 | You have not set a password for this account. Please login using Google or GitHub instead. |
ERR_NGROK_4302 | Unable to redeem password: |
ERR_NGROK_4400 | An email address is required to invite a new user |
ERR_NGROK_4401 | The invited email address is too long: |
ERR_NGROK_4402 | The invited user would exceed your current team size limit of |
ERR_NGROK_4403 | You cannot invite any more users. Please email contact@ngrok.com if you believe this is an error. |
ERR_NGROK_4404 | Unabled to redeem invitation: |
ERR_NGROK_4405 |
|
ERR_NGROK_4407 | You are not currently permitted to enroll in the beta. |
ERR_NGROK_4408 | Feature request suggestions must be between 1 and |
ERR_NGROK_4409 | Your account is not allowed to set invitation permissions. |
ERR_NGROK_4410 | You do not have permissions to invite an administrator to the account. Only administrators may invite other administrators. |
ERR_NGROK_4411 | You do not have permissions to invite users to the account. |
ERR_NGROK_4412 | You may not invite users to the account with higher permissions than your own. |
ERR_NGROK_4413 | Developer Read Write must set on a user if thier permissions include Invite. |
ERR_NGROK_4414 | You are not allowed to create invitations, this account uses SCIM 2.0 to manage members. |
ERR_NGROK_4415 | You are not allowed to redeem this invitation, this account uses SCIM 2.0 to manage members. |
ERR_NGROK_4416 | Your email does not match the email intended for this invitation, |
ERR_NGROK_4451 | A user with the email address |
ERR_NGROK_4452 | The email address being verified, |
ERR_NGROK_4500 | The URL |
ERR_NGROK_4501 | The TCP port |
ERR_NGROK_4502 | The TCP port |
ERR_NGROK_4503 | The IP |
ERR_NGROK_4504 | The host |
ERR_NGROK_4701 | You must only specify a single SSO configuration but you specified both SAML and OpenID Connect. |
ERR_NGROK_4702 | You cannot delete your last IdP provider when SSO enforced is enabled |
ERR_NGROK_5000 | Your account is limited to |
ERR_NGROK_5001 | Your account is rate limited to |
ERR_NGROK_5100 | An event destination must specify a destination target. Valid targets include: |
ERR_NGROK_5102 | You have reached the maximum of |
ERR_NGROK_5103 | No event destinations with ID: |
ERR_NGROK_5104 | Event Destination role ARN " |
ERR_NGROK_5105 | Event Destination role is missing an external ID. |
ERR_NGROK_5106 | Event Destination target is missing the auth field. |
ERR_NGROK_5107 | Event Destination auth is missing a role or credentials to send events to the destination target. |
ERR_NGROK_5108 | Update to target type not allowed. Create a new destination if you would like to send to a new target. |
ERR_NGROK_5112 | Event Destination " |
ERR_NGROK_5115 | An event destination may not specify more than one destination target. |
ERR_NGROK_5116 | An event destination may not specify more than one type of authentication. |
ERR_NGROK_5117 | The property |
ERR_NGROK_5118 | The partition ( |
ERR_NGROK_5119 | The service ( |
ERR_NGROK_5120 | The provided |
ERR_NGROK_5122 | <ERR> |
ERR_NGROK_5123 | Event Subscription |
ERR_NGROK_5124 | Your account can't use the event subscriptions feature. |
ERR_NGROK_5125 | Source |
ERR_NGROK_5126 | You have reached the maximum of |
ERR_NGROK_5127 | The event type for each source must be unique within a subscription. |
ERR_NGROK_5128 | Your account can't create event destinations. |
ERR_NGROK_5129 | The ARN ( |
ERR_NGROK_5130 | The ARN ( |
ERR_NGROK_5131 | You have reached the maximum of |
ERR_NGROK_5132 | The Datadog API key provided is not authorized to send events into Datadog: |
ERR_NGROK_5133 | Event Destination target is missing API Key. |
ERR_NGROK_5134 | The Datadog site provided ( |
ERR_NGROK_5135 | Your account can't use the event source filter feature. |
ERR_NGROK_5136 | The provided azure logs ingestion data collection rule ID is missing or invalid. |
ERR_NGROK_5137 | The provided azure logs ingestion data collection stream name is missing or invalid. |
ERR_NGROK_5138 | The provided azure logs ingestion URI is missing or invalid. |
ERR_NGROK_5139 | The provided azure configuration is invalid: $ |
ERR_NGROK_5140 | One or more provided fields are invalid: $ |
ERR_NGROK_5200 | URL "state" parameter is invalid. |
ERR_NGROK_5201 | URL "state" parameter is invalid. |
ERR_NGROK_5202 | Encountered an error while communicating with the OIDC provider:
" |
ERR_NGROK_5203 | The OIDC provider failed to return a OIDC ID Token. |
ERR_NGROK_5204 | Failed to verify the OIDC ID Token:
" |
ERR_NGROK_5205 | Failed to extract claims from the OIDC ID Token:
" |
ERR_NGROK_5206 | The endpoint configuration " |
ERR_NGROK_5207 | OIDC is not enabled on the endpoint configuration " |
ERR_NGROK_5208 | Encountered an error while attempting to fetch OIDC provider metadata:
" |
ERR_NGROK_5209 | The authentication flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5210 | The authentication flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5211 | The OIDC provider returned the error code " |
ERR_NGROK_5212 | OIDC is not enabled on the domain " |
ERR_NGROK_5300 | SAML RelayState parameter is invalid. |
ERR_NGROK_5301 | The SAML IdP sent an invalid SAML assertion:
" |
ERR_NGROK_5302 | The SAML module for the endpoint configuration " |
ERR_NGROK_5303 | The endpoint configuration " |
ERR_NGROK_5304 | Could not find the domain " |
ERR_NGROK_5305 | The SAML IdP sent an invalid SAML assertion:
" |
ERR_NGROK_5306 | SAML RelayState parameter is invalid. |
ERR_NGROK_5307 | The domain " |
ERR_NGROK_5308 | The SAML IdP sent an invalid SAML logout response:
" |
ERR_NGROK_5309 | URL "state" parameter is invalid. |
ERR_NGROK_5310 | URL "state" parameter is invalid. |
ERR_NGROK_5311 | The SAML IdP sent an invalid SAML assertion with |
ERR_NGROK_5312 | You are not a member of the configured authorized groups on the ngrok edge. |
ERR_NGROK_5313 | The authentication flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5314 | The logout flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5315 | The authentication flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5316 | The logout flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5317 | The SAML module for the edge route " |
ERR_NGROK_5318 | The edge " |
ERR_NGROK_5319 | Failed to complete IdP-initiated SAML login. The RelayState specified an invalid domain " |
ERR_NGROK_5320 | The edge route " |
ERR_NGROK_5321 | The RelayState must be configured with the redirect URL for IdP-initiated logins. |
ERR_NGROK_5322 | The domain " |
ERR_NGROK_5323 | The SAML module is not enabled for the configuration " |
ERR_NGROK_5324 | The ID " |
ERR_NGROK_5325 | Failed to complete IdP-initiated SAML login. Edge does not have any attached domains. Please ensure that at least one domain is configured as a hostport for " |
ERR_NGROK_5326 | Failed to complete IdP-initiated SAML login. The RelayState must be configured with the redirect URL for IdP-initiated logins when using a route selector match type of " |
ERR_NGROK_5400 | Event Sources for the " |
ERR_NGROK_5401 | Event Sources for the " |
ERR_NGROK_5402 | Event Sources for the " |
ERR_NGROK_5403 | Event Sources must be configured with fields that match its event type. " |
ERR_NGROK_5404 | Event Source filter is invalid: " |
ERR_NGROK_5405 | Invalid Event Field: " |
ERR_NGROK_5406 | Field is not yet supported in event filters: " |
ERR_NGROK_5500 | URL "state" parameter is invalid. |
ERR_NGROK_5501 | The authentication flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5502 | Authorization with |
ERR_NGROK_5503 | URL "state" parameter is invalid. |
ERR_NGROK_5504 | The authentication flow was not completed in time. Please try authenticating again. |
ERR_NGROK_5507 | <ERROR_NAME> <DETAILS> |
ERR_NGROK_5508 | Authorization with |
ERR_NGROK_5510 |
|
ERR_NGROK_5511 | Email " |
ERR_NGROK_5512 | Email is malformed. Email " |
ERR_NGROK_5513 | Email domain failed to normalize to a FQDN " |
ERR_NGROK_5517 |
|
ERR_NGROK_5518 |
|
ERR_NGROK_5520 |
|
ERR_NGROK_5521 |
|
ERR_NGROK_5522 |
|
ERR_NGROK_5523 |
|
ERR_NGROK_5524 |
|
ERR_NGROK_5525 |
|
ERR_NGROK_5526 |
|
ERR_NGROK_5527 |
|
ERR_NGROK_5528 | The access code from |
ERR_NGROK_5529 |
|
ERR_NGROK_5530 | OAuth is not enabled on the domain " |
ERR_NGROK_5531 |
|
ERR_NGROK_5532 |
|
ERR_NGROK_5533 |
|
ERR_NGROK_5534 | Encountered an error while attempting to fetch OIDC provider metadata:
" |
ERR_NGROK_5535 | The OAuth provider " |
ERR_NGROK_5536 | Encountered an error while fetching user data: |
ERR_NGROK_6000 | This tunnel was unable to update; this may be temporary, please try again shortly. |
ERR_NGROK_6001 | This tunnel is no longer available as its account was not found. |
ERR_NGROK_6002 | This tunnel is no longer available as its account does not own resources required to run. |
ERR_NGROK_6003 | Endpoint configurations cannot be used with agent-specified basic auth. Either remove the endpoint configuration from this endpoint or restart the agent without basic auth. |
ERR_NGROK_6006 | The Event Destination |
ERR_NGROK_6008 | This endpoint is unavailable as its account is suspended due to lack of payment. |
ERR_NGROK_6009 | The ngrok account that was hosting this webpage has been suspended for violation of ngrok's Terms of Service. If you're seeing this page instead of the one you were expecting, ngrok has most likely blocked a phishing attack targeting you. If you did enter any sensitive information before seeing this notice, please contact the real site by directly entering their URL in your browser. Learn more about how to protect yourself from phishing scams: https://consumer.ftc.gov/articles/how-recognize-and-avoid-phishing-scams |
ERR_NGROK_6010 | Endpoint configuration is incompatible with tunnel; module |
ERR_NGROK_6011 | You may not specify |
ERR_NGROK_6013 | Failed to compile filter for Event Subscription |
ERR_NGROK_6014 | Failed to run filter for Event Subscription |
ERR_NGROK_6018 | The Endpoint |
ERR_NGROK_6019 | The Endpoint |
ERR_NGROK_6020 | The Endpoint |
ERR_NGROK_6021 | HTML content may only be served after you upgrade to a paid account. |
ERR_NGROK_6022 | Before you can serve HTML content, you must sign up for an ngrok account and install your authtoken. |
ERR_NGROK_6023 | HTML content may only be served in this region after you upgrade to a paid account. |
ERR_NGROK_6024 | You are about to visit |
ERR_NGROK_6025 | The tunnel |
ERR_NGROK_6026 | The Endpoint |
ERR_NGROK_6027 | The Endpoint |
ERR_NGROK_6028 | The Endpoint |
ERR_NGROK_6500 | Your account is not authorized to use the backends feature. |
ERR_NGROK_6501 | Cannot save backend reference |
ERR_NGROK_6502 | The backend could not be deleted because it is still referenced by at least one backend. |
ERR_NGROK_6503 | Description is limited to |
ERR_NGROK_6504 | Metadata is limited to |
ERR_NGROK_6505 | Static backend requires address in the host:port form. |
ERR_NGROK_6506 | Static backend address |
ERR_NGROK_6507 | Static backend address |
ERR_NGROK_6508 | Tunnel group labels count is limited to |
ERR_NGROK_6509 | Tunnel group label key length is limited to between |
ERR_NGROK_6510 | Tunnel group label value length is limited to between |
ERR_NGROK_6511 | Weighted backends count is limited to |
ERR_NGROK_6512 | Weighted backend |
ERR_NGROK_6513 | Failover backends may only contain up to |
ERR_NGROK_6514 | Backend not found. |
ERR_NGROK_6515 | Tunnel Group Backend |
ERR_NGROK_6516 | HTTP Response Backend |
ERR_NGROK_6517 | HTTP Response Backend |
ERR_NGROK_6522 | The header beginning with |
ERR_NGROK_6523 | The header value for |
ERR_NGROK_6524 | A Weighted Backend may not reference the backend |
ERR_NGROK_6525 | A Failover Backend may not reference the backend |
ERR_NGROK_6526 | The id |
ERR_NGROK_6527 | The id |
ERR_NGROK_6528 | Traffic made it to the ngrok edge, but there are no tunnels online serving an app. |
ERR_NGROK_6529 | Your account is not authorized to use the weighted backends feature. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_6530 | The |
ERR_NGROK_6531 | The tunnel group label key/value |
ERR_NGROK_6600 | The account |
ERR_NGROK_6601 | Failed to add |
ERR_NGROK_6602 | You may not remove the last administrator of the account. Grant administrator privileges to another member first. |
ERR_NGROK_6603 | Your account is not allowed to set membership permissions. |
ERR_NGROK_6604 | You may not remove an administrator from the account. Only administrators may remove other administrators. |
ERR_NGROK_6605 | You may not grant administrator privileges to an account member. Only administrators may grant administrative privileges. |
ERR_NGROK_6606 | You may not change an administrator's permissions. Only other administrators may make that change. |
ERR_NGROK_6607 | You may not change the account administrator. Only the current accont administrator may make this change. |
ERR_NGROK_6608 | Could not transfer administrative control to membership |
ERR_NGROK_6609 | Swapping administrators is not supported on accounts with RBAC enabled. |
ERR_NGROK_6612 | You are not allowed to remove members. |
ERR_NGROK_6613 | You are not allowed to create members. |
ERR_NGROK_6614 | You are not allowed to set the permissions of members. |
ERR_NGROK_6615 | You may not create users with higher permissions than your own. |
ERR_NGROK_6616 | You may not set user permissions higher than your own. |
ERR_NGROK_6617 | Users must have a defined billing permission. |
ERR_NGROK_6618 | You are not allowed to create members, this account uses SCIM 2.0 to manage members. |
ERR_NGROK_6619 | You are not allowed to remove members, this account uses SCIM 2.0 to manage members. |
ERR_NGROK_6620 | You are not allowed to activate/deactivate members, this account uses SCIM 2.0 to manage members. |
ERR_NGROK_6621 | You are not allowed to activate/deactivate admins. Only other administrators may make that change. |
ERR_NGROK_6622 | You may not deactivate the last administrator of the account. Grant administrator privileges to another member first. |
ERR_NGROK_6700 | The description is limited to |
ERR_NGROK_6701 | Metadata is limited to |
ERR_NGROK_6702 | No DNS records were returned when querying for an NS record for the domain |
ERR_NGROK_6703 | The NS records for the domain |
ERR_NGROK_6704 | The specified domain " |
ERR_NGROK_6705 | The agent ingress domain " |
ERR_NGROK_6706 | The agent ingress domain " |
ERR_NGROK_6707 | Your account can't reserve custom agent ingresses. Contact us for access to the Agent Ingresses feature. |
ERR_NGROK_6708 | Multiple certificate sources provided. |
ERR_NGROK_6709 | Some of the dedicated IPs " |
ERR_NGROK_6710 | Dedicated IP " |
ERR_NGROK_6711 | Dedicated IP " |
ERR_NGROK_7000 | Edge not found |
ERR_NGROK_7001 | Invalid edge ID |
ERR_NGROK_7002 | Invalid edge request |
ERR_NGROK_7007 | The IP Policy ID |
ERR_NGROK_7008 | Only Pro and Enterprise plans are allowed to use edges. Your account is not authorized to use edges. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7009 | Your account is limited to a maximum of |
ERR_NGROK_7011 | Invalid edge, circuit breaker error threshold percentage must be between 0.0 and 1.0 inclusive, was |
ERR_NGROK_7012 | The auth provider |
ERR_NGROK_7013 | The edge module exceeds the max number of IP Policies. You specified |
ERR_NGROK_7014 | The edge module TLS CA certificate size exceeds the max. You specified |
ERR_NGROK_7015 | The edge module exceeds the max number of headers. You specified |
ERR_NGROK_7016 | Invalid edge module, circuit breaker tripped duration must be greater than 0, was |
ERR_NGROK_7017 | Invalid edge module, circuit breaker rolling window must be greater than 0, was |
ERR_NGROK_7018 | Invalid edge module, circuit breaker num buckets must be greater than 0 and less than |
ERR_NGROK_7019 | The edge could not be deleted because it is still referenced by at least one reserved domain or reserved address. |
ERR_NGROK_7020 | The edge must specify a type. |
ERR_NGROK_7021 | The module |
ERR_NGROK_7022 |
|
ERR_NGROK_7023 |
|
ERR_NGROK_7024 |
|
ERR_NGROK_7025 | You must specify at least one IP Policy in the IP Restriction module. |
ERR_NGROK_7026 | SNS webhook verification does not accept a secret. |
ERR_NGROK_7027 | Webhook verification for |
ERR_NGROK_7028 | There were validation errors while saving the edge: |
ERR_NGROK_7029 | You must specify a supported provider name. Supported providers: [ |
ERR_NGROK_7030 | Webhook provider |
ERR_NGROK_7031 | Only Pro and Enterprise accounts can use edges webhook verification.
Your account is not authorized to use webhook verification. |
ERR_NGROK_7032 | You may not configure the TLS termination parameter |
ERR_NGROK_7033 | Invalid edge module, unmanaged provider configurations must specify a client ID and a client secret. |
ERR_NGROK_7034 | Invalid edge module, custom OAuth scopes on a managed OAuth application are not allowed. Define a custom OAuth application to use custom scopes. |
ERR_NGROK_7035 | Invalid edge module, OAuth auth check interval must be at least |
ERR_NGROK_7036 | Invalid edge module, OAuth may only have one provider configuration but multiple are defined: [ |
ERR_NGROK_7037 | Invalid edge module, OAuth does not define any provider configurations but one is required. |
ERR_NGROK_7038 | Invalid edge module, OAuth provider |
ERR_NGROK_7039 | Invalid edge module, OAuth provider |
ERR_NGROK_7040 | Invalid edge module, OAuth GitHub Teams must be listed as either numerical ids or in the format 'org_slug/team_slug', |
ERR_NGROK_7041 | Only Pro and Enterprise accounts can use edges OAuth.
Your account is not authorized to use OAuth. |
ERR_NGROK_7042 | Invalid edge module, OAuth cookie prefix |
ERR_NGROK_7043 | Invalid edge module, OAuth provider |
ERR_NGROK_7044 | Invalid edge module, OAuth provider |
ERR_NGROK_7045 | Invalid edge module, OAuth provider |
ERR_NGROK_7046 | Invalid edge module, OAuth provider |
ERR_NGROK_7047 | Invalid edge module, OAuth provider |
ERR_NGROK_7048 | Invalid edge module, OAuth provider |
ERR_NGROK_7049 | Invalid edge module, OAuth provider |
ERR_NGROK_7050 | Invalid edge module, OAuth provider |
ERR_NGROK_7051 | Invalid edge module, OAuth provider |
ERR_NGROK_7052 | Invalid edge module, OAuth provider |
ERR_NGROK_7053 | Invalid edge module, OAuth provider |
ERR_NGROK_7054 | Invalid edge module, OAuth provider |
ERR_NGROK_7055 | Invalid edge module, OAuth provider |
ERR_NGROK_7056 | The edge module exceeds the maximum number of OAuth scopes. You specified |
ERR_NGROK_7057 | The edge module exceeds the maximum number of OAuth GitHub teams. You specified |
ERR_NGROK_7058 | The edge module exceeds the maximum number of OAuth GitHub orgs. You specified |
ERR_NGROK_7059 | The edge module exceeds the maximum number of OAuth Google groups. You specified |
ERR_NGROK_7060 | The edge module exceeds the maximum number of OAuth emails. You specified |
ERR_NGROK_7061 | The edge module exceeds the maximum number of OAuth domains. You specified |
ERR_NGROK_7062 | The edge specifies the following modules which may not be enabled when TLS is not terminated: |
ERR_NGROK_7067 | Invalid edge module, email addresses must be lowercase but |
ERR_NGROK_7068 | Invalid edge module, email domains must be lowercase but |
ERR_NGROK_7069 | Duplicate 'add' header, |
ERR_NGROK_7070 | Your account is limited to |
ERR_NGROK_7071 | Your account is rate limited for adding |
ERR_NGROK_7072 | The CA ID |
ERR_NGROK_7073 | Description is limited to |
ERR_NGROK_7074 | Metadata is limited to |
ERR_NGROK_7075 | The Mutual TLS configurations exceeds the limit of |
ERR_NGROK_7079 | The edge specifies conflicting authentication modules. Only one of SAML, OIDC, or OAuth may be enabled. |
ERR_NGROK_7080 | The SAML metadata exceeds the maximum length of |
ERR_NGROK_7081 | You must specify only the SAML IdP metadata or the SAML IdP metadata URL, but not both. |
ERR_NGROK_7082 | Failed to connect to IdP metadata URL |
ERR_NGROK_7083 | Failed to parse the SAML IdP metadata: |
ERR_NGROK_7084 | Received unexpected status code |
ERR_NGROK_7085 | Failed to parse the SAML IdP metadata fetched from URL |
ERR_NGROK_7086 | Encountered an error while reading the response body from the IdP metadata URL |
ERR_NGROK_7087 | The specified OIDC issuer has a maximum length of |
ERR_NGROK_7088 | The OIDC issuer property is required. |
ERR_NGROK_7089 | The OIDC Client ID property is required. |
ERR_NGROK_7090 | The OIDC Client Secret property is required. |
ERR_NGROK_7091 | One of the SAML IdP Metadata or IdP Metadata URL properties must be specified. |
ERR_NGROK_7092 | Invalid edge module, session inactivity timeout cannot be more than one year, was |
ERR_NGROK_7093 | Your account is not authorized to use basic auth. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7094 | Your account is not authorized to use compression. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7095 | Your account is not authorized to use circuit breaker. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7096 | Your account is not authorized to use request headers. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7097 | Your account is not authorized to use response headers. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7098 | Your account is not authorized to use OIDC. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7099 | Your account is not authorized to use SAML. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7100 | Your account is not authorized to use TLS termination. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7101 | Your account is not authorized to use IP Restrictions. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7102 | Your account is not authorized to use TCP address backends. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7103 | Your account is not authorized to use mutual TLS. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7104 | Edge has invalid hostports, must be specified in the format 'hostname:portnumber': |
ERR_NGROK_7105 | The header beginning with |
ERR_NGROK_7106 | The header value for |
ERR_NGROK_7107 | The sendgrid verification key is not a base64 encoded ecdsa public key. The following error was encountered while trying to parse it: " |
ERR_NGROK_7108 | Your account is not authorized to use the websocket to TCP converter. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7109 | You may not configure the TLS termination parameter 'terminate_at' for an HTTPS edge. |
ERR_NGROK_7110 | The request edge ID |
ERR_NGROK_7111 | The edge hostport |
ERR_NGROK_7112 | The hostport |
ERR_NGROK_7113 | The address |
ERR_NGROK_7114 | The address |
ERR_NGROK_7115 | The address |
ERR_NGROK_7116 | The domain |
ERR_NGROK_7117 | The domain |
ERR_NGROK_7118 | The domain |
ERR_NGROK_7119 | The domain |
ERR_NGROK_7120 | TCP edges can only be associated with TCP addresses: |
ERR_NGROK_7121 | HTTPS edges can only be associated with reserved domains: |
ERR_NGROK_7122 | Hostport |
ERR_NGROK_7123 | Edge routes require a match expression. |
ERR_NGROK_7124 | The edge route |
ERR_NGROK_7125 | There is a duplicate route |
ERR_NGROK_7126 | Route match expression |
ERR_NGROK_7127 | OAuth may not currently be configured for any route except '/', could not configure for route |
ERR_NGROK_7128 | Your account is limited to a maximum of |
ERR_NGROK_7129 | Your account is limited to a maximum of |
ERR_NGROK_7130 | Invalid match type, valid values are "exact_path" and "path_prefix". |
ERR_NGROK_7131 | The route selector expression |
ERR_NGROK_7132 | The hostport |
ERR_NGROK_7133 | TLS edges can only be associated with reserved domains: |
ERR_NGROK_7134 | OAuth, OIDC and SAML may only be configured for routes with path selectors (i.e. 'exact_path', 'path_prefix'). |
ERR_NGROK_7135 | The route selector expression exceeds the maximum length of |
ERR_NGROK_7136 | The OAuth Cookie Prefix exceeds the maximum length of |
ERR_NGROK_7137 | The OAuth Client ID exceeds the maximum length of |
ERR_NGROK_7138 | The OAuth Client Secret exceeds the maximum length of |
ERR_NGROK_7139 | The OAuth Email Address exceeds the maximum length of |
ERR_NGROK_7140 | The OAuth Email Domain exceeds the maximum length of |
ERR_NGROK_7141 | The OAuth Scope exceeds the maximum length of |
ERR_NGROK_7142 | The edge module exceeds the maximum number of GitHub teams. You specified |
ERR_NGROK_7143 | The edge module exceeds the maximum number of GitHub orgs. You specified |
ERR_NGROK_7144 | The OAuth GitHub team exceeds the maximum length of |
ERR_NGROK_7145 | The OAuth GitHub org exceeds the maximum length of |
ERR_NGROK_7146 | The edge module exceeds the maximum number of Google groups. You specified |
ERR_NGROK_7147 | The OAuth Google group exceeds the maximum length of |
ERR_NGROK_7148 | The OIDC Client ID exceeds the maximum length of |
ERR_NGROK_7149 | The OIDC Client Secret exceeds the maximum length of |
ERR_NGROK_7150 | The edge module exceeds the maximum number of OIDC scopes. You specified |
ERR_NGROK_7151 | The OIDC Scope exceeds the maximum length of |
ERR_NGROK_7152 | The OIDC Authn URL exceeds the maximum length of |
ERR_NGROK_7153 | The OIDC cookie prefix exceeds the maximum length of |
ERR_NGROK_7154 | The Webhook Verification secret exceeds the maximum length of |
ERR_NGROK_7155 | Enabling OAuth, OIDC, or SAML on more than one route is not supported. |
ERR_NGROK_7158 | Invalid edge module, OAuth auth check interval must be no greater than |
ERR_NGROK_7159 | Invalid edge module, OIDC auth check interval must be at least |
ERR_NGROK_7160 | Invalid edge module, OIDC auth check interval must be no greater than |
ERR_NGROK_7161 | Invalid edge module, OAuth max session duration must be no greater than |
ERR_NGROK_7162 | Invalid edge module, OIDC max session duration must be no greater than |
ERR_NGROK_7163 | Your account is not authorized to use the TLS edges. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7164 | The |
ERR_NGROK_7165 | An unsupported OAuth Provider was configured. |
ERR_NGROK_7166 | The " |
ERR_NGROK_7167 | Your account is not authorized to use user agent filter. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7168 | Your account is not authorized to use JWT Validation. Upgrade to a Pay-as-you-go or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_7169 | The |
ERR_NGROK_7170 | The |
ERR_NGROK_7171 | The JWT Validation configuration is invalid: |
ERR_NGROK_7172 | The JWT Validation configuration must have at least one issuer in the allow list. |
ERR_NGROK_7173 | The JWT Validation issuer is invalid: |
ERR_NGROK_7174 | The JWT Validation configuration must have at least one audience in the allow list. |
ERR_NGROK_7175 | The JWT Validation audience is invalid: |
ERR_NGROK_7176 | The JWT Validation configuration must have at least one allowed algorithm. |
ERR_NGROK_7177 | The |
ERR_NGROK_7178 | The JWT Validation configuration must have at least one token configuration. |
ERR_NGROK_7179 | The JWT Validation http token is invalid: |
ERR_NGROK_7180 | The JWT Validation http token name |
ERR_NGROK_7181 | The JWT Validation http token prefix |
ERR_NGROK_7182 | The JWT Validation signing key must have a way to be identified such as the 'kid' token claim. |
ERR_NGROK_7183 | The JWT Validation signing key must have a valid identification mechanism such as the 'kid' token claim. |
ERR_NGROK_7184 | The JWT Validation signing key must have at least one source. |
ERR_NGROK_7185 | The JWT Validation signing key source has an invalid additional jku: |
ERR_NGROK_7186 | The JWT Validation signing key source has an invalid additional jku: |
ERR_NGROK_7187 | The JWT Validation issuer |
ERR_NGROK_7188 | The JWT Validation audience |
ERR_NGROK_7189 | The JWT Validation http token identified by the method: |
ERR_NGROK_7190 | The JWT Validation signing key algorithm |
ERR_NGROK_7191 | The JWT Validation signing key identification token claim |
ERR_NGROK_7192 | The JWT Validation signing key source additional jku |
ERR_NGROK_7193 | The JWT Validation signing key sources have too many possible sources. You can supply at most 100. |
ERR_NGROK_7194 | Your account is not authorized to use policies. |
ERR_NGROK_7195 | This edge module has exceeded its policy rule limit of |
ERR_NGROK_8000 | Failed to resolve host |
ERR_NGROK_8001 | Failed to establish internet connectivity: |
ERR_NGROK_8002 | Failed to establish TCP connection to |
ERR_NGROK_8003 | Failed to establish TLS connection to |
ERR_NGROK_8004 | Failed to establish tunnel protocol connection to |
ERR_NGROK_8005 | Failed to resolve proxy IP with error: |
ERR_NGROK_8006 | Failed to connect to proxy |
ERR_NGROK_8007 | No tunnel servers were reachable via TCP. |
ERR_NGROK_8008 | No tunnel servers could establish a TLS connection. |
ERR_NGROK_8009 | No tunnel servers could establish a tunnel connection. |
ERR_NGROK_8010 |
|
ERR_NGROK_8011 | IPV6 errors encountered - it may be disabled. |
ERR_NGROK_8012 | Traffic was successfully tunneled to the ngrok agent, but the agent failed to establish a connection to the upstream web service at |
ERR_NGROK_8013 | You must add a credit or debit card before you can use TCP endpoints on a free account. We require a valid card as a way to combat abuse and keep the internet a safe place. This card will NOT be charged. Add a card to your account here: https://dashboard.ngrok.com/settings#id-verification |
ERR_NGROK_9000 | An account is required to use basic authentication. Please register for an ngrok account at: https://dashboard.ngrok.com/signup and install your authtoken. |
ERR_NGROK_9001 | Your account is not authorized to use compression. |
ERR_NGROK_9002 | Your account is not authorized to use circuit breaker. |
ERR_NGROK_9003 | Your account is not authorized to use request headers. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9004 | Your account is not authorized to use response headers. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9005 | Your account is not authorized to use OIDC. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9006 | Your account is not authorized to use SAML. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9007 | Your account is not authorized to use TLS Termination. Upgrade to a paid plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9008 | Your account is not authorized to run the agent as a service. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9009 | Running the agent with an http/s proxy is an enterprise feature. If this is unexpected, verify that there is no proxy_url value in your ngrok configuration file and that the http_proxy environment variable is not set. If you need this capability, upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9010 | Your account is not authorized to run the agent with socks5 proxy. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9011 | Your account is not authorized to run the agent on a custom network interface. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9012 | Your account is not authorized to run the agent with custom CAs. Upgrade to a Pro, Enterprise, or Pay-as-you-go plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9013 | Your account is not authorized to run the agent with mutual TLS. Please contact us at: sales@ngrok.com |
ERR_NGROK_9014 | Your account is not authorized to run the agent with proxy proto. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9015 | Your account is not authorized to use OAuth. |
ERR_NGROK_9016 | Your account is not authorized to use webhook verification. |
ERR_NGROK_9017 | Your account is not authorized to use ip restrictions. Upgrade to a Pro, Enterprise, or Pay-as-you-go plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9018 | An account is required to use host header rewrite. Please register for an ngrok account at: https://dashboard.ngrok.com/signup and install your authtoken. |
ERR_NGROK_9019 | Your account is not authorized to use mutual TLS. Please contact us at: sales@ngrok.com |
ERR_NGROK_9020 | Your account is not authorized to use the websocket to TCP converter. Upgrade to a Personal, Pro, Enterprise, or Pay-as-you-go plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9021 | You may specify at most one of subdomain, hostname, or domain for a tunnel. |
ERR_NGROK_9022 | Your account is not authorized to use user agent filtering. Please upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
ERR_NGROK_9023 | Your account is not authorized to use the policy module. |
ERR_NGROK_9024 | The account |
ERR_NGROK_9025 | You cannot specify both "Policy" and "TrafficPolicy". Use "TrafficPolicy" as "Policy" is deprecated. |
ERR_NGROK_9026 | The TrafficPolicy you provided is invalid: |
ERR_NGROK_9027 | Your account is not authorized to use internal bindings. |
ERR_NGROK_9028 | You must specify a domain name for a internally bound endpoint. |
ERR_NGROK_9029 | Failed to start endpoint with |
ERR_NGROK_9030 | Failed to start endpoint with URL |
ERR_NGROK_9031 | Failed to start endpoint with URL |
ERR_NGROK_9032 | Provided domain |
ERR_NGROK_9033 | Provided domain |
ERR_NGROK_9034 | Malformed URL: |
ERR_NGROK_9035 | Invalid port for reserve domains with scheme |
ERR_NGROK_9036 | Invalid scheme |
ERR_NGROK_9037 | Invalid URL |
ERR_NGROK_9038 | Invalid URL, trailing '/' is not allowed. Did you mean |
ERR_NGROK_9039 | You must specify a domain name for a kubernetes operator bound endpoint. |
ERR_NGROK_9040 | We do not allow agents to connect to ngrok from your IP address. If you believe this to be in error, please contact support: support@ngrok.com |
ERR_NGROK_10000 | Internal Server Error. Please check our status page https://status.ngrok.com/ or contact support: support@ngrok.com |
ERR_NGROK_10001 | Something went wrong with our code. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10002 | Could not read server rendered application data. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10003 | Something went wrong when communicating with Stripe. Please try again later. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10004 | Could not find the credit card form. Do you have a script blocker installed? |
ERR_NGROK_10005 | Could not find the Stripe token. Do you have a script blocker installed? |
ERR_NGROK_10006 | Failed to load the required reCAPTCHA script! Are you blocking it? It is required to continue. |
ERR_NGROK_10007 | All rules must be prefixed with "bind:" |
ERR_NGROK_10008 | If the "HTTPS" module is enabled and "Terminate TLS" is unchecked, then your configuration may not include any other modules except the IP Policy module. |
ERR_NGROK_10009 | The request header name must be at least one character. |
ERR_NGROK_10010 | The request header value must be at least one character. |
ERR_NGROK_10011 | You have already added the request header name " |
ERR_NGROK_10012 | The response header name must be at least one character. |
ERR_NGROK_10013 | The response header value must be at least one character. |
ERR_NGROK_10014 | You have already added the response header name " |
ERR_NGROK_10019 | You haven't added any Event Destinations |
ERR_NGROK_10020 | You haven't added any Event Sources |
ERR_NGROK_10021 | Received partition " |
ERR_NGROK_10022 | Received service " |
ERR_NGROK_10023 | There were no changes to submit. |
ERR_NGROK_10024 | Cannot update non-existent IP Policy. |
ERR_NGROK_10025 | A TLS Certificate must be selected. |
ERR_NGROK_10026 | Failed to upload Certificate Authority. Invalid file format " |
ERR_NGROK_10027 | Failed to upload SAML IdP Metadata. Invalid file format " |
ERR_NGROK_10028 | Failed to upload TLS Certificate. Invalid file format " |
ERR_NGROK_10029 | Failed to upload TLS Certificate Private Key. Invalid file format " |
ERR_NGROK_10030 | Failed to upload Certificate Authority. Please limit your file uploads to less than 16 KB. |
ERR_NGROK_10031 | Failed to upload SAML IdP Metadata. Please limit your file uploads to less than 16 KB. |
ERR_NGROK_10032 | Failed to upload TLS Certificate. Please limit your file uploads to less than 16 KB. |
ERR_NGROK_10033 | Failed to upload TLS Certificate Private Key. Please limit your file uploads to less than 16 KB. |
ERR_NGROK_10034 | Could not copy the AuthToken to your clipboard. Please ensure that you have granted the browser permission "clipboard-write". |
ERR_NGROK_10062 | ARN must begin with "arn:" |
ERR_NGROK_10063 | ARN is invalid |
ERR_NGROK_10064 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10065 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10066 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10067 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10068 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10069 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10072 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10073 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10074 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10075 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10076 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10077 | This account does not support JIT provisioning for SSO users. |
ERR_NGROK_10078 | This account requires users to be authenticated with a valid SSO provider. |
ERR_NGROK_10079 | The team member queried is of an unknown type. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_10080 | The invitation |
ERR_NGROK_10081 | You must specify only the correct ID for the requested team member entry. |
ERR_NGROK_10082 | You must specify a user, bot, or membership ID when attempting to update a credentials owner. |
ERR_NGROK_10083 | You already have a valid MFA configuration of this type enabled. |
ERR_NGROK_10084 | You cannot delete the SSO Identity Provider you used to logged when SSO Enforcement is enabled on your account. |
ERR_NGROK_10085 | The endpoint of the request you are trying to replay was not found. |
ERR_NGROK_10086 | You have exceeded the rate limit of |
ERR_NGROK_10087 | Request header " |
ERR_NGROK_10088 | Request body size too large. |
ERR_NGROK_10089 | Failed to replay the request. |
ERR_NGROK_10090 | The request you are trying to view was not found. |
ERR_NGROK_10091 | The usage page has timed out. Please refresh the page and try again. |
ERR_NGROK_11000 | Internal Server Error. Please refresh the page and try again. If the problem persists, please check our status page https://status.ngrok.com/ or contact the frontend team. |
ERR_NGROK_11001 | Something went wrong with our code. Please refresh the page and try again. If the problem persists, please contact the frontend team. |
ERR_NGROK_11002 | Could not read server rendered application data. Please refresh the page and try again. If the problem persists, please contact the frontend team. |
ERR_NGROK_11003 | Something went wrong with our code. Please refresh the page and try again. If the problem persists, please contact the frontend team. |
ERR_NGROK_11004 | ARN must begin with "arn:" |
ERR_NGROK_11005 | ARN is invalid |
ERR_NGROK_11006 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact the frontend team. |
ERR_NGROK_12000 | A new version of ngrok corp is required to continue. Please refresh the page to update. |
ERR_NGROK_13001 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13002 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13003 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13004 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13005 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13006 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13007 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13008 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_13009 | Encountered a type "never" value. Please refresh the page and try again. If the problem persists, please contact support: support@ngrok.com |
ERR_NGROK_14000 | The |
ERR_NGROK_14001 | Got an invalid TLS key/cert pair for TLS termination: |
ERR_NGROK_14002 | The PEM data provided for mutual TLS could not be parsed as a certificate: |
ERR_NGROK_15000 | You are not allowed to bind subdomains on |
ERR_NGROK_15001 | The Webhook Verification secret exceeds the maximum length of |
ERR_NGROK_15002 | Your account is on the |
ERR_NGROK_15003 | Upstream protocol is invalid: |
ERR_NGROK_15004 | This agent has exceeded its policy rule limit of |
ERR_NGROK_15005 | The binding |
ERR_NGROK_15006 | The binding |
ERR_NGROK_15007 | The Webhook Verification secret was not specified. |
ERR_NGROK_15008 | Invalid basic auth credential. Username must be at most |
ERR_NGROK_15009 | Invalid basic auth credentials list. Your plan is limited to |
ERR_NGROK_15010 | The binding |
ERR_NGROK_16000 | The email of the user you are trying to add, |
ERR_NGROK_17000 | The MFA device type " |
ERR_NGROK_17001 | The information supplied for MFA verification was invalid. |
ERR_NGROK_17002 | You do not have any recovery codes configured. |
ERR_NGROK_17003 | The information supplied for recovery code verification was invalid. |
ERR_NGROK_17004 | A matching MFA device was not found. |
ERR_NGROK_17005 | MFA Device verification is not supported. |
ERR_NGROK_18001 | The provided cloud endpoint configuration is invalid: url is invalid. |
ERR_NGROK_18002 | The provided cloud endpoint traffic policy configuration is invalid: |
ERR_NGROK_18003 | The provided cloud endpoint configuration is invalid: port is invalid or missing and cannot be inferred from scheme |
ERR_NGROK_18004 | The cloud endpoint update failed because no values were provided. Specify at least one value. |
ERR_NGROK_18005 | The cloud endpoint update failed because you are not allowed to change the protocol/URL scheme in-place. |
ERR_NGROK_18006 | This account does not have any domains or addresses reserved that match the provided URL. |
ERR_NGROK_18008 | This account does not have access to Cloud Endpoints. |
ERR_NGROK_18009 | This account already has a cloud endpoint on this URL. |
ERR_NGROK_18010 | You have exceeded the maximum number of cloud endpoints allowed for this account. Please log into https://dashboard.ngrok.com/usage to review your historic usage and https://dashboard.ngrok.com/billing/subscription/select to view your subscription options. |
ERR_NGROK_18012 | The description field cannot be longer than 255 characters. |
ERR_NGROK_18013 | The metadata field cannot be longer than 4096 characters. |
ERR_NGROK_18014 | The provided cloud endpoint has invalid value for field |
ERR_NGROK_18015 | The provided cloud endpoint is missing the required field |
ERR_NGROK_19000 | Internal Server Error. |
ERR_NGROK_19001 | Certificate Signing Requests Failed! Reason: |
ERR_NGROK_19002 | Failed to validate Kubernetes Operator! Reason: |
ERR_NGROK_20000 | An internal error occurred. |
ERR_NGROK_20001 | Operation failed due to a configuration error: |
ERR_NGROK_20002 | Failed to create the Upstream Service for BoundEndpoint. |
ERR_NGROK_20003 | Failed to create the Target Service for BoundEndpoint. |
ERR_NGROK_20004 | Failed to establish a connection between the Upstream and Target Services. |
ERR_NGROK_20005 | BoundEndpoint is Denied due to no matching pattern in AllowedURLs |
ERR_NGROK_20006 | Failed to create CSR. |