When something goes wrong with ngrok, we report a unique error code. Each error code points to a specific location in our codebase and our engineers can use that to triage or give you specific instructions about what happened and the steps you can take to fix it. These codes were also designed so that you could quickly search your favorite search engine to find more information. Adding this code to your issue, comment, or support message will help everyone else trying to fix this issue.
Some error codes occur more frequently than others. Here is a list of the common error codes.
| Code | Message |
|---|---|
| ERR_NGROK_100 | Invalid metadata length |
| ERR_NGROK_108 | You've hit your account limit for simultaneous ngrok agent sessions. Try stopping an existing agent or upgrading your account. |
| ERR_NGROK_1226 | You are disallowed from creating an ngrok account due to violation of the terms of service. |
| ERR_NGROK_4100 | The email or password you entered is not valid. |
| ERR_NGROK_1205 | You failed to solve the catpcha, please try again. |
| ERR_NGROK_3004 | ngrok gateway error. The server returned an invalid or incomplete HTTP response. Try starting ngrok with the full upstream service URL (e.g. ngrok http https://localhost:8081) |
| ERR_NGROK_3200 | Tunnel not found. This could be because your agent is not online or your tunnel has been flagged by our automated moderation system. |
| ERR_NGROK_4101 | A user with the email address already exists. |
| ERR_NGROK_4011 | Your password must be at least 10 characters. |
| ERR_NGROK_4013 | You may not create a new account because you are already a member of a free account. Upgrade or delete that account first before creating a new account. |
| ERR_NGROK_4108 | Sign ups are disallowed for the email provider. Please sign up with a different email provider. |
Use this table to find more information about the error code you received.
| Code | Message |
|---|---|
| ERR_NGROK_100 |
Invalid metadata length: <VAL> bytes. Max:
<MAX>
|
| ERR_NGROK_102 |
The last payment for the <ACCOUNT> account failed.
The account has been suspended. Update the payment information here:
https://dashboard.ngrok.com/billing/payment-method
|
| ERR_NGROK_103 |
The account <ACCOUNT> has been suspended. This is
usually the result of violating the ngrok Terms of Service. Email
contact@ngrok.com if you think your suspension is an error.
|
| ERR_NGROK_105 |
The authtoken you specified does not look like a proper ngrok tunnel
authtoken. Your authtoken: <TOKEN> Instructions to
install your authtoken are on your ngrok dashboard:
https://dashboard.ngrok.com/get-started/your-authtoken
|
| ERR_NGROK_106 |
The authtoken you specified is an ngrok v1 authtoken, but you're using
ngrok v2. Your authtoken: <TOKEN> Instructions to
install your authtoken are on your ngrok dashboard:
https://dashboard.ngrok.com/get-started/your-authtoken
|
| ERR_NGROK_107 |
The authtoken you specified is properly formed, but it is invalid. Your
authtoken: <TOKEN> This usually happens when: - You
reset your authtoken - Your authtoken was for a team account that you
were removed from - You are using ngrok link and this credential was
explicitly revoked Go to your ngrok dashboard and double check that your
authtoken is correct:
https://dashboard.ngrok.com/get-started/your-authtoken
|
| ERR_NGROK_108 |
Your account is limited to <MAX> simultaneous ngrok
agent session<PLURAL>. <MSG>
|
| 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>
|
| 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
<MIN>, you specified <VAL>
|
| ERR_NGROK_112 |
The heartbeat tolerance you specified is not valid. It must be at least
<MIN>, you specified <VAL>
|
| ERR_NGROK_115 |
Your IP <IP> does not match the IP Policies specified
by the Agent IP Restriction for this account. Please authenticate from
an IP in the correct range or update your Agent IP Restrictions from the
ngrok dashboard. https://dashboard.ngrok.com/security/ip-restrictions
|
| ERR_NGROK_116 |
Your IP <IP> does not match the IP ACL policy
specified for your credentials. Please authenticate from an IP in the
correct range or make sure you are using the correct credentials
|
| ERR_NGROK_118 |
Only Enterprise accounts can use the enterprise tunnel ingress feature.
Your account <ACCOUNTNAME> is not permitted to use
the ngrok enterprise tunnel ingress. Upgrade to an Enterprise plan at:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_119 |
The agent specified an invalid semantic version string:
<VERSION>
|
| ERR_NGROK_120 |
Your ngrok agent version "<VERSION>" is no longer
supported. Only the most recent version of the ngrok agent is supported
without an account. Update to a newer version with `ngrok update` or by
downloading from https://ngrok.com/download. Sign up for an account to
avoid forced version upgrades: https://ngrok.com/signup.
|
| ERR_NGROK_121 |
Your ngrok agent version "<VERSION>" is too old. The
minimum supported agent version for your account is
"<MINVERSION>". Please update to a newer version with
`ngrok update` or by downloading from https://ngrok.com/download.
|
| ERR_NGROK_122 |
Your account is not permitted to use the agent ingress
"<DOMAIN>".
|
| ERR_NGROK_123 |
The account "<NAME>" may not start an ngrok agent
session until the admin's email address is verified. Verify your email
at https://dashboard.ngrok.com/user/settings
|
| 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 |
| 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: <VAL>. API keys and
instructions are available on your dashboard:
https://dashboard.ngrok.com/api
|
| ERR_NGROK_202 |
The API authentication you specified does not look like a valid
credential. Your credential: <TOKEN>. API keys and
instructions are available on your dashboard:
https://dashboard.ngrok.com/api
|
| ERR_NGROK_203 |
The API authentication you specified is properly formed, but it is
invalid. Your authentication: <TOKEN>. API keys and
instructions are available on your dashboard:
https://dashboard.ngrok.com/api
|
| ERR_NGROK_204 |
Only the Pro and Enterprise accounts can use the ngrok API. This is a
valid API token, but the account <ACCOUNT> is not
authorized to use the ngrok API. Upgrade to a Pro or Enterprise plan at:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_205 |
The account <ACCOUNT> has been suspended. This is
usually the result of violating the ngrok Terms of Service. Email
contact@ngrok.com if you think your suspension is an error.
|
| ERR_NGROK_206 |
The authentication you specified is actually a tunnel credential. Your
credential: <TOKEN>. Please check your records for an
API key. API keys and instructions are available on your dashboard:
https://dashboard.ngrok.com/api
|
| ERR_NGROK_207 |
The authentication you specified is actually a tunnel credential, not an
API key token. Your key: <TOKEN>. Please check your
records for an API key with the form FIRSTPART_SECONDPART. API keys and
instructions are available on your dashboard:
https://dashboard.ngrok.com/api
|
| ERR_NGROK_208 |
The authentication you specified is actually an API key ID, not an API
key token. Your credential: <TOKEN>. Please check
your records for an API key with the form FIRSTPART_SECONDPART. API keys
and instructions are available on your dashboard:
https://dashboard.ngrok.com/api
|
| ERR_NGROK_210 |
The content type you specified <CTYPE> is not
supported by the API. Please check your API client implementation and
see the list of supported content types:
https://ngrok.com/docs/ngrok-link#service-api-content-type
|
| ERR_NGROK_211 |
The <METHOD> request you made does not expect a body,
but you provided one. Please check your API client implementation and
review the API documentation:
https://ngrok.com/docs/ngrok-link#service-api.
|
| 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/ngrok-link#service-api. |
| ERR_NGROK_213 |
The <CTYPE> request body could not be parsed. Please
check your API client implementation and review the API documentation:
https://ngrok.com/docs/ngrok-link#service-api.
|
| ERR_NGROK_214 |
The request parameter <NAME> is unknown and not
expected. The supported fields are: <SUPPORTED>.
Please check your API client implementation and review the API
documentation: https://ngrok.com/docs/ngrok-link#service-api.
|
| ERR_NGROK_215 |
The value provided for the request parameter
<NAME> is invalid. Please check your request and
review the API documentation:
https://ngrok.com/docs/ngrok-link#service-api
|
| 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/ngrok-link#service-api-content-type |
| ERR_NGROK_217 |
The provided API version <VERSION> is invalid or
unsupported. Supported versions: <SUPPORTED>. Please
check your API client implementation.
|
| 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:
<SUPPORTED>.
|
| ERR_NGROK_219 |
<TLSVERSION> is not a supported TLS version.
Supported versions: <SUPPORTED>.
|
| 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/security/ip-restrictions |
| ERR_NGROK_221 |
This is a valid API token, but the account
<ACCOUNT> is not authorized to submit or view abuse
reports. Email contact@ngrok.com if you believe this is an error.
|
| ERR_NGROK_223 |
<ID> is not a valid resource reference identifier.
|
| ERR_NGROK_224 |
The value <VAL> is not valid for the terminate_at
property of the TLS Termination endpoint configuration module. Must be
either 'edge' or 'upstream'.
|
| ERR_NGROK_225 |
Your account is limited to <MAX> simultaneous API
requests.
|
| ERR_NGROK_226 |
Your account is rate limited to <MAX> API requests
per <INTERVAL>.
|
| ERR_NGROK_227 |
The ID <VAL> is invalid. Expected an ID with a prefix
of <PREFIX>.
|
| ERR_NGROK_228 |
The ID <VAL> is not a valid Certificate Authority ID.
|
| ERR_NGROK_229 |
The ID <VAL> is not a valid IP Policy ID.
|
| ERR_NGROK_230 |
The query part of the requested URI is invalid:
<ERR>. Please check your API client implementation
and review the API documentation:
https://ngrok.com/docs/ngrok-link#service-api.
|
| ERR_NGROK_231 |
The query part of the requested URI includes unknown parameters:
<UNKNOWN>. The supported parameters are:
<SUPPORTED>. Please check your API client
implementation and review the API documentation:
https://ngrok.com/docs/ngrok-link#service-api.
|
| ERR_NGROK_232 |
The request must specify only a single value for the
<NAME> parameter but got <COUNT>:
<VALUES>. Please check your API client implementation
and review the API documentation:
https://ngrok.com/docs/ngrok-link#service-api.
|
| ERR_NGROK_233 |
The page size limit must be between 1 and <MAX> but
<VAL> was provided.
|
| ERR_NGROK_235 |
The Format <VAL> is missing or is not a valid Event
Destination Format. Supported formats are:
<SUPPORTED>.
|
| ERR_NGROK_236 |
The destination target is invalid. Expected fields include one of the
following: <TARGETS>
|
| ERR_NGROK_238 |
The provided event type: <TYP> is not valid. Valid
event types are <ID>
|
| ERR_NGROK_239 |
The provided field: <TYP> is not valid.
|
| ERR_NGROK_240 | The provided event destination auth is invalid. |
| ERR_NGROK_241 |
The value "<TS>" is not a valid RFC3339 timestamp.
Error while parsing: "<ERR>".
|
| ERR_NGROK_242 |
The ID <VAL> is not a valid Backend ID.
|
| ERR_NGROK_243 |
The ID <VAL> is invalid. Expected an ID with prefix
one of <PREFIXES>.
|
| ERR_NGROK_244 |
The page size limit must be a number between 1 and
<MAX> but <VAL> was provided.
|
| ERR_NGROK_247 |
The account <ACCOUNT> has been suspended for
non-payment. Update your payment method to pay your oustanding bill and
resume service: https://dashboard.ngrok.com/billing/payment-method
|
| ERR_NGROK_300 |
The authtoken credential <ID> has been revoked and is
no longer valid.
|
| 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>
|
| ERR_NGROK_302 | TCP 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 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 Pro and Business paid 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 after you sign up. 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 |
Only paid plans may bind custom subdomains. Failed to bind the custom
subdomain <SUBDOMAIN> 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_306 |
Custom hostnames are only available for Pro and Business paid plans.
Failed to bind the custom hostname <HOSTNAME> 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_307 |
You must reserve an address for your account before it can be bound.
Failed to bind the address <ADDR> for the account
<ACCOUNT> in region <REGION>.
(Hint: Did you reserve the address in this region?) Reserve an address
on your dashboard: https://dashboard.ngrok.com/cloud-edge/tcp-addresses
|
| ERR_NGROK_308 |
The credential ACL policy does not permit binding this address.
Credential ID: <ID> Address:
<ADDR>
|
| ERR_NGROK_309 |
This address is reserved for another account. Failed to bind the address
<ADDR> for the account <ACCOUNT>.
Reserve an address on your dashboard:
https://dashboard.ngrok.com/cloud-edge/tcp-addresses/new If you have
reserved this address, make sure that you are using an authtoken
credential for the appropriate account.
|
| ERR_NGROK_310 |
Only Pro and Enterprise plans may bind reserved addresses. Failed to
bind the address <ADDR> for the account
<ACCOUNT>. This account is on the
<PLAN> plan. This usually only happens if you
downgraded your ngrok.com account and it no longer has permission to use
reserved addresses. Upgrade to Pro or Enterprise:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_311 |
This address is allocated for a different region. Failed to bind the
address <ADDR> in region
<WANT> because it is reserved in the
<HAVE> region. Try connecting to a different region:
https://ngrok.com/docs/platform#pops
|
| ERR_NGROK_312 |
Failed to bind a TLS tunnel for the account
<ACCOUNT>. Only Enterprise plans may bind TLS
tunnels. This account is on the <PLAN> plan. Upgrade
to an Enterprise plan at:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_313 |
Only paid plans may bind custom subdomains. Failed to bind the custom
subdomain <SUBDOMAIN> for the account
<ACCOUNT>. This account is on the
<PLAN> plan. Upgrade to a paid plan at:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_314 |
Only Pro and Enterprise plans may bind custom hostnames. Failed to bind
the custom hostname <HOSTNAME> for the account
<ACCOUNT>. This account is on the
<PLAN> plan. Upgrade to a paid plan at:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_315 |
Only Enterprise plans may bind wildcard names. Failed to bind the
wildcard name <DOMAIN> for the account
<ACCOUNT>. This account is on the
<PLAN> plan. Upgrade to an Enterprise plan at:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_316 |
The credential ACL policy does not permit binding this name. Credential
ID: <ID> Name: <DOMAIN>
|
| ERR_NGROK_317 |
You cannot bind the domain <DOMAIN> in region
<WANT> because it is only available in the
<HAVE> region. Try connecting to a different region:
https://ngrok.com/docs/platform#pops
|
| ERR_NGROK_318 |
You must reserve a wildcard domain for your account before it can be
bound. Failed to bind the wildcard domain
<DOMAIN> for the account
<ACCOUNT> in region <REGION>.
Reserve a domain on your dashboard:
https://dashboard.ngrok.com/cloud-edge/domains/new
|
| ERR_NGROK_319 |
You must reserve a custom hostname for your account before it can be
bound. Failed to bind the domain <DOMAIN> for the
account <ACCOUNT> in region
<REGION>. (Hint: Did you reserve the domain in this
region?) Reserve this name on your dashboard:
https://dashboard.ngrok.com/cloud-edge/domains/new
|
| ERR_NGROK_320 |
This domain is reserved for another account. Failed to bind the domain
<DOMAIN> for the account
<ACCOUNT>. If you have reserved this name, make sure
that you are using an authtoken credential for the appropriate account.
Reserve a name on your dashboard:
https://dashboard.ngrok.com/cloud-edge/domains/new
|
| ERR_NGROK_321 |
Wildcard names must be reserved exactly. Failed to bind the wildcard
domain <DOMAIN> for the account
<ACCOUNT>. This name matches
<MATCH> which is reserved for your account, but
wildcard domains must be reserved with an exact match. Reserve this name
on your dashboard: https://dashboard.ngrok.com/cloud-edge/domains/new
|
| ERR_NGROK_322 |
This name is reserved in a different region. Failed to bind the domain
<DOMAIN> in the region
<WANT> because it is reserved in the
<HAVE> region. Try connecting to a different region:
https://ngrok.com/docs/platform#pops
|
| ERR_NGROK_323 |
You may not run more than <MAX> tunnels over a single
ngrok session without an account. You may increase this limit by signing
up and upgrading. The tunnels already running on this session are:
<URLS>
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_324 |
Your account may not run more than <MAX> tunnels over
a single ngrok agent session. The tunnels already running on this
session are:
<URLS>
|
| ERR_NGROK_326 |
Invalid character <CHAR> in domain name. Valid
domains may contain only a-z, A-Z, 0-9, . * and - characters. Failed to
bind the domain <DOMAIN>.
|
| ERR_NGROK_327 |
Domain has an invalid character sequence. Valid domains may not contain
repeated periods '..'. Failed to bind the domain
<DOMAIN>.
|
| ERR_NGROK_328 |
Domain part <PART> has an invalid first character.
Valid domain parts must begin with a-z, A-Z, 0-9 or *. Failed to bind
the domain <DOMAIN>.
|
| ERR_NGROK_329 |
Domain part <PART> has an invalid last character.
Valid domains must end with a-z A-Z or 0-9. Failed to bind the domain
<DOMAIN>.
|
| 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 <DOMAIN>.
|
| ERR_NGROK_331 |
You may not bind a domain with the TLD <SUFFIX>. This
TLD is not reachable over the public internet. Failed to bind the domain
<DOMAIN>.
|
| ERR_NGROK_332 |
<PROTO> is not a supported tunnel protocol
|
| ERR_NGROK_333 |
No tunnel found with the ID <ID>
|
| ERR_NGROK_334 |
The tunnel <URL> is already bound to another tunnel
session
|
| 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 <ACCOUNT> account failed.
The account has been suspended. Update the payment information here:
https://dashboard.ngrok.com/billing/payment-method
|
| ERR_NGROK_338 |
The account <ACCOUNT> has been suspended. This is
usually the result of violating the ngrok Terms of Service. Email
contact@ngrok.com if you think your suspension is an error.
|
| 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 <ID> not found
|
| ERR_NGROK_342 | Only Enterprise plans may use per-tunnel IP policies. Your account is not authorized to use per-tunnel IP policies. Upgrade to Enterprise: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_343 |
Endpoint configuration <ID> does not allow the agent
to set basic authentication. Update the endpoint configuration to
specify 'agent' as the auth provider or remove the basic authentication
settings from the agent's tunnel creation definition.
|
| ERR_NGROK_344 |
Endpoint configuration <ID> does not allow clients to
set an IP policy.
|
| ERR_NGROK_345 |
Endpoint configuration <ID>s HTTPS module terminates
TLS which is incompatible with a 'tls' tunnel. You may either: - Modify
the endpoint configuration to include the HTTPS module with
'terminate_tls' disabled. - OR start an 'http' tunnel with
-bind-tls=true or -bind-tls=both instead
|
| ERR_NGROK_346 |
Endpoint configuration <ID>s HTTPS module does not
terminate TLS which is incompatible with a 'https' tunnel. You may
either: - Modify the endpoint configuration to enable the
'terminate_tls' option - OR start a 'tls' tunnel instead
|
| ERR_NGROK_347 |
Domain has invalid punycode: <IDNA_ERROR>. Failed to
bind the domain <DOMAIN>.
|
| ERR_NGROK_348 |
Your account is limited to <MAX> sessions.
|
| ERR_NGROK_349 |
Your account is rate limited for adding
<MAX> sessions per <INTERVAL>.
|
| ERR_NGROK_350 |
Your account is limited to <MAX> tunnels in a
session.
|
| ERR_NGROK_351 |
Your account is rate limited for adding <MAX> tunnels
per <INTERVAL>.
|
| ERR_NGROK_352 |
Anonymous sessions are limited to <MAX> tunnels.
|
| ERR_NGROK_353 |
Anonymous sessions are rate limited for adding
<MAX> tunnels per <INTERVAL>.
|
| ERR_NGROK_354 |
Failed to bind <DOMAIN>. Nested subdomains of the
ngrok base endpoint domain <ENDPOINT_DOMAIN> must be
reserved first. Alternatively, try
<SUGGESTION> instead.
|
| ERR_NGROK_355 |
Invalid '_' in domain name. Valid domains may not contain underscores.
Failed to bind the domain <DOMAIN>.
|
| ERR_NGROK_356 |
The credential ACL policy does not permit binding random TCP addresses.
Credential ID: <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
<MINLENGTH> and
<MAXLENGTH> characters, got
<GOTLENGTH>.
|
| ERR_NGROK_361 |
Invalid circuit breaker configuration, error threshold percentage must
be between 0.0 and 1.0 inclusive, was <VAL>.
|
| ERR_NGROK_362 |
Invalid IP restriction configuration, invalid CIDR:
<CIDR>
|
| ERR_NGROK_363 |
You must specify a supported provider name. Supported providers:
[<SUPPORTED>]
|
| ERR_NGROK_364 |
Webhook provider <PROVIDER> is not supported.
Supported providers: [<SUPPORTED>]
|
| ERR_NGROK_365 |
OAuth provider <PROVIDER> is not supported. Supported
providers: [<SUPPORTED>]
|
| ERR_NGROK_366 |
You may not authorize more than <MAX> emails. Got
<GOT>.
|
| ERR_NGROK_367 |
You may not authorize more than <MAX> email domains.
Got <GOT>.
|
| ERR_NGROK_368 |
You may not request more than <MAX> oauth scopes. Got
<GOT>.
|
| ERR_NGROK_370 |
Added request header should be in key:value format, got
<VAL>
|
| ERR_NGROK_371 |
Added response header should be in key:value format, got
<VAL>
|
| ERR_NGROK_372 |
<KEY> is not a valid HTTP header name because it
contains at least one invalid character.
|
| ERR_NGROK_373 |
<KEY> is not a valid HTTP header name because it
contains at least one invalid character.
|
| ERR_NGROK_374 |
<VAL> is not a valid HTTP header value:
<REASON>.
|
| ERR_NGROK_375 |
Duplicate 'add' header, <HEADER> was provided twice
with different casings: <CASE_ONE> and
<CASE_TWO>.
|
| ERR_NGROK_376 |
Exceeded the maximum number of added headers. You specified
<VAL>, the maximum is <MAX>.
|
| ERR_NGROK_377 |
The header beginning with <PREFIX>...' exceeds the
maximum header name length of 128 bytes.
|
| ERR_NGROK_378 |
The header value for <HEADERKEY> beginning with
<PREFIX>...' exceeds the maximum header value length
of 1024 bytes.
|
| 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:
"<ERROR>"
|
| ERR_NGROK_380 |
The resource <ID> was referenced, but not found.
Please retry, and contact support if this error persists.
|
| ERR_NGROK_381 |
The host <HOST> and port
<PORT> you requested is already reserved by an edge.
|
| ERR_NGROK_382 |
The account "<NAME>" may not start a tunnel until the
admin's email address is verified. Verify your email at
https://dashboard.ngrok.com/user/settings
|
| 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 <MAX> OIDC scopes. Got
<GOT>.
|
| 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
<MAX>. Got scope <SCOPE> with
length <GOT>.
|
| ERR_NGROK_392 |
You may not request an individual OIDC scope with length greater than
<MAX>. Got scope <SCOPE> with
length <GOT>.
|
| 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_400 |
The region you specified, <REGION> is invalid. Please
use one of the following acceptable values: <VALID>
|
| ERR_NGROK_401 | Only Pro or Enterprise accounts can reserve domains. Your account can't reserve domains. Upgrade to a Pro or Enterprise 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 <DOMAIN>.
|
| ERR_NGROK_403 |
The first subdomain of a wildcard domain must be a single '*' character.
Failed to reserve <DOMAIN>.
|
| ERR_NGROK_404 |
You may not reserve names on ngrok.com. Please use an ngrok.io suffix.
Failed to reserve <DOMAIN>.
|
| ERR_NGROK_405 |
You may not reserve a domain with the suffix
<SUFFIX> in the <WANT> region
because names with this suffix must be reserved for the
<HAVE> region. Failed to reserve
<DOMAIN>.
|
| ERR_NGROK_406 |
Invalid character <CHAR> in domain name. Valid
domains may contain only a-z, A-Z, 0-9, . * and - characters. Failed to
reserve <DOMAIN>.
|
| ERR_NGROK_407 |
Domain part <PART> has an invalid first character.
Valid domain parts must begin with a-z, A-Z, 0-9 or *. Failed to reserve
<DOMAIN>.
|
| ERR_NGROK_408 |
Domain part <PART> has an invalid last character.
Valid domains must end with a-z A-Z or 0-9. Failed to reserve
<DOMAIN>.
|
| ERR_NGROK_409 |
Domain has an invalid character sequence. Valid domains may not contain
repeated periods '..'. Failed to reserve <DOMAIN>.
|
| 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 <DOMAIN>.
|
| ERR_NGROK_411 |
You may not reserve a name on the TLD <SUFFIX>. This
TLD is not reachable over the public internet. Failed to reserve
<DOMAIN>.
|
| ERR_NGROK_412 |
Only Pro or Enterprise accounts can reserve tunnels on whitelabel
domains. Your account cannot reserve tunnels on whitelabel domains
(<DOMAIN> is not a subdomain of
<BASE>). Upgrade to a Pro or Enterprise plan at:
https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_413 |
This domain is already reserved for your account. Failed to reserve
<DOMAIN>.
|
| ERR_NGROK_414 |
This domain is already reserved for another account. Failed to reserve
<DOMAIN>.
|
| ERR_NGROK_415 |
Your account is limited to <MAX> reserved domains.
Email sales@ngrok.com to purchase additional domains.
|
| ERR_NGROK_416 |
You may not register a wildcard for all
<SUFFIX> domains. Failed to reserve
<DOMAIN>.
|
| ERR_NGROK_417 |
This wildcard domain would conflict with a domain reserved for another
account. Failed to reserve <DOMAIN>.
|
| ERR_NGROK_418 |
Your account is limited to <MAX> wildcard domains.
Email contact@ngrok.com to purchase additional wildcard domains.
|
| ERR_NGROK_419 | Only Pro or Enterprise accounts can reserve wildcard domains. Your account can't reserve wildcard domains. Upgrade to a Pro or Enterprise plan at https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_420 |
A description is limited to <MAX> characters; you
have entered <VAL> characters.
|
| ERR_NGROK_421 |
Metadata is limited to <MAX> characters; you have
entered <VAL> characters.
|
| 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
<MAX> characters; you are using
<VAL> characters. The name you've requested is:
<DOMAIN>
|
| ERR_NGROK_424 |
Domain <DOMAIN> does not require a CNAME record
|
| ERR_NGROK_425 |
Domain <DOMAIN> CNAME record not found
|
| ERR_NGROK_426 |
Domain <DOMAIN> CNAME record not found, A record
<IPS> found
|
| ERR_NGROK_427 |
Domain <DOMAIN> CNAME record resolved to
<HAVE>, should have been <WANT>
|
| ERR_NGROK_428 |
You may not assign endpoint configuration
<ID> because it is type <TYPE>.
You must assign a configuration with type
<EXPECTEDTYPE>.
|
| ERR_NGROK_429 |
Domain has invalid punycode: <IDNA_ERROR>. Failed to
reserve <DOMAIN>.
|
| ERR_NGROK_430 |
Another account is running an active tunnel on the domain
<DOMAIN>. You may not reserve domains that are
actively in use.
|
| ERR_NGROK_431 |
Your account is limited to <MAX> reserved domains.
|
| ERR_NGROK_432 |
Your account is rate limited for adding
<MAX> reserved domains per
<INTERVAL>.
|
| ERR_NGROK_433 |
Your account is limited to <MAX> reserved wildcard
domains.
|
| 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 <DOMAIN>.
|
| 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 <DOMAIN> does not require an ACME Challenge
CNAME record
|
| ERR_NGROK_442 |
Domain <RECORD> ACME Challenge CNAME record not found
|
| ERR_NGROK_443 |
ACME Challenge <RECORD> CNAME record not found, A
record <IPS> found
|
| ERR_NGROK_444 |
ACME Challenge <RECORD> CNAME record resolved to
<HAVE>, should have been <WANT>
|
| ERR_NGROK_445 |
There was an error looking up the DNS <RTYPE> record
for domain <DOMAIN> (status:
<STATUS>): <MSG>
|
| ERR_NGROK_500 |
The region you specified, <REGION> is invalid. Please
use one of the following acceptable values: <VALID>
|
| ERR_NGROK_501 | Only Pro or Enterprise accounts can reserve addresses. Your account can't reserve addresses. Upgrade to a Pro or Enterprise plan at https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_502 |
Your account is limited to <MAX> reserved addresses.
Email contact@ngrok.com to purchase additional addresses.
|
| ERR_NGROK_503 |
No available reserved addresses in region <REGION>
|
| ERR_NGROK_504 |
A description is limited to <MAX> characters; you
have entered <VAL> characters.
|
| ERR_NGROK_505 |
Metadata is limited to <MAX> characters; you have
entered <VAL> characters.
|
| 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
<ID> because it is type <TYPE>.
You must assign a configuration with type 'tcp'.
|
| ERR_NGROK_508 |
Your account is limited to <MAX> reserved addresses.
|
| ERR_NGROK_509 |
Your account is rate limited for adding
<MAX> reserved addresses per
<INTERVAL>.
|
| ERR_NGROK_511 |
The domain <DOMAIN> has a dangling CNAME record. The
CNAME must be deleted before this domain can be reserved.
|
| ERR_NGROK_512 |
The domain <DOMAIN> has a dangling A, AAAA, ALIAS or
other record pointing to ngrok. The record must be deleted before this
domain can be reserved.
|
| ERR_NGROK_600 |
Invalid ACL rule. An ACL rule must be '*' or start with 'bind:'. You
specified: <RULE>.
|
| ERR_NGROK_601 |
Cannot delete user credential <ID>.
|
| ERR_NGROK_602 |
Your account is limited to <MAX> tunnel credentials.
Email contact@ngrok.com to increase the limit.
|
| ERR_NGROK_603 |
Your account is limited to <MAX> API keys. Email
contact@ngrok.com to increase the limit.
|
| ERR_NGROK_604 |
A description is limited to <MAX> characters; you
have entered <VAL> characters.
|
| ERR_NGROK_605 |
Metadata is limited to <MAX> characters; you have
entered <VAL> characters.
|
| ERR_NGROK_606 | The credentials update failed because no values were provided. Specify at least one value. |
| ERR_NGROK_607 | Only Pro and Enterprise accounts can use the SSH tunnel feature. SSH tunnel feature is not enabled. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_608 |
Your account is limited to <MAX> SSH keys. Email
contact@ngrok.com to increase the limit.
|
| ERR_NGROK_609 |
The public key <PUBKEY> already exists on your
account.
|
| ERR_NGROK_610 |
The public key <PUBKEY> is already used in a
different account. Remove it from the other ngrok account or generate a
new SSH key pair (hint: use ssh-keygen).
|
| ERR_NGROK_611 | Public key is missing or empty. |
| ERR_NGROK_612 |
Invalid public key <PUBKEY>: <ERR>
|
| ERR_NGROK_613 |
Your account is limited to <MAX> API keys.
|
| ERR_NGROK_614 |
Your account is rate limited for adding <MAX> API
keys per <INTERVAL>.
|
| ERR_NGROK_615 |
Your account is limited to <MAX> tunnel credentials.
|
| ERR_NGROK_617 |
Your account is limited to <MAX> SSH keys.
|
| ERR_NGROK_619 |
Your account is not authorized to use this ACL rule type. You specified:
<RULE>.
|
| ERR_NGROK_620 | Only Enterprise plans can use tunnel ACL rules. Your account is not authorized to use tunnel ACL rules. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_621 | Only Enterprise plans can use API ACL rules. Your account is not authorized to use API ACL rules. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_622 | Only Enterprise plans can use SSH ACL rules. Your account is not authorized to use SSH ACL rules. Upgrade to an Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_702 |
Too many connections! The tunnel session
<SESSION> has violated the rate-limit policy of
<THRESHOLD> connections per minute by initiating
<COUNT> connections in the last
<SECONDS> seconds. Please decrease your inbound
connection volume or upgrade to a paid plan for additional capacity.
|
| ERR_NGROK_703 |
Too many connections! The account hosting this endpoint has violated the
rate-limit policy of <THRESHOLD> connections per
minute by initiating <COUNT> connections in the last
<SECONDS> seconds. Please decrease your inbound
connection volume or upgrade your account plan for additional capacity.
|
| 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 |
Your account is limited to <MAX> connections.
|
| ERR_NGROK_715 |
Your account is rate limited for adding
<MAX> connections per <INTERVAL>.
|
| ERR_NGROK_716 |
Anonymous sessions are limited to <MAX> connections.
|
| ERR_NGROK_717 |
Anonymous sessions are rate limited for adding
<MAX> connections per <INTERVAL>.
|
| ERR_NGROK_718 |
Your account is rate limited to <MAX> bytes incoming
traffic per <INTERVAL>.
|
| ERR_NGROK_719 |
Anonymous sessions are rate limited to <MAX> bytes
incoming traffic per <INTERVAL>.
|
| ERR_NGROK_720 |
Your account is rate limited to <MAX> bytes outgoing
traffic per <INTERVAL>.
|
| ERR_NGROK_721 |
Anonymous sessions are rate limited to <MAX> bytes
outgoing traffic per <INTERVAL>.
|
| ERR_NGROK_722 | internal server error |
| ERR_NGROK_724 |
No backend is available to serve requests for endpoint
<URL>.
|
| ERR_NGROK_800 |
Unknown stream type: <TYPE>. This usually indiciates
a bug in the client's protocol implementation.
|
| 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>
|
| 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:
<REASON>.
|
| ERR_NGROK_805 |
This ngrok agent does not support remote stopping:
<REASON>.
|
| ERR_NGROK_806 |
This ngrok agent does not support remote updating:
<REASON>.
|
| ERR_NGROK_807 |
The remote ngrok agent failed to stop because of an error:
<ERR>
|
| ERR_NGROK_808 |
The remote ngrok agent failed to restart because of an error:
<ERR>
|
| ERR_NGROK_809 |
The remote ngrok agent failed to update because of an error:
<ERR>
|
| 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:
"<REQUESTED>", Supported:
<SUPPORTED>"
|
| ERR_NGROK_812 |
Your request exceeded the maximum size of <SIZE>.
|
| ERR_NGROK_1000 |
Your billing address is too long: <VAL> bytes. Max:
<MAX>
|
| ERR_NGROK_1001 |
Your tax ID is too long: <VAL> bytes. Max:
<MAX>
|
| ERR_NGROK_1002 |
Your account is limited to <MAX> billing email
addresses. Email contact@ngrok.com to increase the limit
|
| ERR_NGROK_1003 |
The billing email <ID> (<EMAIL>)
may not be deleted
|
| ERR_NGROK_1004 |
The billing email is too long: <VAL> bytes. Max:
<MAX>
|
| ERR_NGROK_1005 |
The billing email address <EMAIL> is invalid:
<ERR>
|
| ERR_NGROK_1006 |
There was a problem with your credit card: <MSG>
|
| ERR_NGROK_1007 |
Your subscription was updated, by we failed to charge your card:
<MSG>.
|
| ERR_NGROK_1008 |
Your account is limited to <MAX> billing email
addresses.
|
| ERR_NGROK_1010 |
The email address "<EMAIL>" is invalid.
|
| 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 <USERS> users.
|
| ERR_NGROK_1013 |
Yearly plans can only be downgraded or canceled in their final month.
Try again after <TIMESTAMP>.
|
| ERR_NGROK_1014 | You may only purchase one license product at a time. |
| ERR_NGROK_1015 | You are on 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_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/tunnels/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
<VAL>, max <MAX>). Rerun ssh with
'-v' to check what keys get 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/tunnels/ssh-keys |
| ERR_NGROK_1103 |
Only Pro or Enterprise accounts can use the SSH tunneling feature. The
account <ACCOUNT> doesn't have the SSH tunneling
feature enabled. Upgrade to a Pro or Enterprise plan at:
https://dashboard.ngrok.com/billing/subscription to enable SSH tunnels.
|
| 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 <USER> API version. Use
<VERSION> as user when connecting with SSH to get the
latest version.
|
| 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 |
<CMD> is not a valid tunnel type. The SSH command
must be one of 'http', 'tls', or 'tcp'.
|
| ERR_NGROK_1109 |
<FLAG> flag is not supported when using SSH tunneling
|
| ERR_NGROK_1110 |
Error while parsing the <CMD> command:
<OUT>
|
| 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 <PORT> when using
<CMD> command. Use 'ssh -R 0:host:hostport ...' to
let the server choose the remote port based on the command.
|
| ERR_NGROK_1114 |
Cannot use bind address '-R
<HOST>:<PORT>:' with
'-remote-addr=<ADDR> parameter. You may either
specify -R <HOST>:<PORT>:' or
-remote-addr=<ADDR> but not both.
|
| ERR_NGROK_1115 |
Cannot request a custom TCP port '-R <PORT>:' with
'-remote-addr=<ADDR> parameter. Remove -remote-addr
and specify 'ssh -R address:port:host:port' to bind on your reserved
address. Example: ssh -R 0:localhost:22 ... Example: ssh -R
1.tcp.eu.ngrok.io:21412:localhost:22 ...
|
| ERR_NGROK_1116 |
Cannot request a custom bind port '-R <PORT>:'. You
may either specify a reserved TCP address with '-R address:port:' or you
may let the server choose a random remote port for you with '-R 0:'.
Example: ssh -R 0:localhost:22 ... Example: ssh -R
1.tcp.eu.ngrok.io:21412:localhost:22 ...
|
| ERR_NGROK_1117 |
Cannot request a random port with a custom bind address
<ADDR> in '-R <ADDR>:0:'. You may
either specify a reserved TCP address with '-R address:port:' or you may
let the server choose a random remote port for you with '-R 0:'.
Example: ssh -R 0:localhost:22 ... Example: ssh -R
1.tcp.eu.ngrok.io:21412:localhost:22 ...
|
| ERR_NGROK_1118 |
Cannot use binding address '-R <ADDR>:' with
'-hostname=<HOSTNAME> parameter. You may either
specify '-R <ADDR>:' or '-hostname=<HOSTNAME>
but not both.
|
| ERR_NGROK_1119 |
Cannot use binding address '-R <ADDR>:' with
'-subdomain=<SUBDOMAIN> parameter. You may either
specify binding address '-R <ADDR>:' or
'-subdomain=<SUBDOMAIN> but not both.
|
| ERR_NGROK_1120 |
Cannot use '-hostname=<HOSTNAME> with
'-subdomain=<SUBDOMAIN> parameter. You may either
specify '-hostname=<HOSTNAME> or '-subdomain=<SUBDOMAIN>
but not both.
|
| ERR_NGROK_1121 | SSH sessions do not support update. |
| ERR_NGROK_1122 | SSH sessions do not support restart. |
| ERR_NGROK_1123 |
Tunnel '-proxy-proto=<PROXYPROTO> specifies invalid
protocol version. Use one of version '1' or '2' to enable proxy proto.
|
| ERR_NGROK_1200 |
Authorized account's primary email <EMAIL> is not
verified.
|
| 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 catpcha, 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 catpcha, please try again. |
| ERR_NGROK_1210 |
Invalid subscription interval <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/security/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 <MAX> requests per
<INTERVAL>.
|
| ERR_NGROK_1215 |
The user <EMAIL> does not have permissions to invite
other team members.
|
| ERR_NGROK_1216 |
The user <EMAIL> does not have permissions to manage
team members.
|
| ERR_NGROK_1217 |
The user <EMAIL> does not have permissions to view
billing information.
|
| ERR_NGROK_1218 |
The user <EMAIL> does not have permissions to change
billing information.
|
| ERR_NGROK_1219 |
The user <EMAIL> does not have permissions to change
developer resources.
|
| ERR_NGROK_1220 |
The user <EMAIL> does not have administrative
privileges which are required to perform this operation.
|
| 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_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 <PARAM>
|
| ERR_NGROK_1406 | Invalid CIDR: <CIDR> |
| ERR_NGROK_1407 |
IP Policy with name <NAME> already exists
|
| ERR_NGROK_1408 |
IP Policy Rule with CIDR <CIDR> already exists
|
| ERR_NGROK_1409 |
IP Policy Rule CIDR <CIDR> must be specified using
the lowest IP address in the range. Did you mean
<SUGGESTION>?
|
| ERR_NGROK_1410 |
Your account is limited to a maximum of <MAX> IP
Policies
|
| ERR_NGROK_1411 |
Your account is limited to a maximum of <MAX> IP
Policy rules for each IP Policy
|
| ERR_NGROK_1412 | Only Pro or Enterprise accounts can use per-tunnel IP policies. Your account is not authorized to use per-tunnel IP policies. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1413 |
IP Policy Rule is missing a network mask. Consider using
<IP>/<BITS> if you want to target
a single host IP.
|
| 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 <MAX> IP Policies.
|
| ERR_NGROK_1417 |
Your account is limited to <MAX> rules per IP Policy.
|
| ERR_NGROK_1419 |
Cannot delete only rule (<RULEID>) in use by
dashboard IP Restriction (<RESTRICTIONID>). Please
detach this IP Policy from IP Restriction before deleting this rule.
|
| ERR_NGROK_1420 |
Cannot delete IP Policy (<POLICYID>) because it is
referenced by one or more IP Restrictions:
(<RESTRICTIONIDS>). Please detach this IP Policy from
all IP Restrictions before deleting it.
|
| ERR_NGROK_1421 |
The IP Policy Rule description exceeds the maximum length of
<MAX>, got <SIZE>.
|
| 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 <ID> specified for the IP Policy
module does not exist.
|
| ERR_NGROK_1608 | Only Pro or Enterprise accounts can use endpoint configuration. Your account is not authorized to use endpoint configurations. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1609 |
Your account is limited to a maximum of
<MAX> endpoint configurations.
|
| ERR_NGROK_1611 |
Invalid endpoint configuration, circuit breaker error threshold
percentage must be between 0.0 and 1.0 inclusive, was
<VAL>.
|
| ERR_NGROK_1612 |
The auth provider <VAL> does not exist. Specify an
auth provider ID or the special value 'agent'.
|
| ERR_NGROK_1613 |
The endpoint configuration exceeds the max number of ip policies. You
specified <VAL>, the maximum is
<MAX>.
|
| ERR_NGROK_1614 |
The endpoint configuration TLS CA certificate size exceeds the max. You
specified <VAL>, the maximum is
<MAX>.
|
| ERR_NGROK_1615 |
The endpoint configuration exceeds the max number of headers. You
specified <VAL>, the maximum is
<MAX>.
|
| ERR_NGROK_1616 |
Invalid endpoint configuration, circuit breaker tripped duration must be
greater than 0, was <VAL>.
|
| ERR_NGROK_1617 |
Invalid endpoint configuration, circuit breaker rolling window must be
greater than 0, was <VAL>.
|
| ERR_NGROK_1618 |
Invalid endpoint configuration, circuit breaker num buckets must be
greater than 0 and less than <MAX>, was
<VAL>.
|
| 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 <NAME> is not supported on an endpoint
configuration of type <TYPE>.
|
| ERR_NGROK_1622 |
<NAME> is not a valid endpoint configuration type.
Must be one of 'http', 'https', 'tcp'.
|
| ERR_NGROK_1623 |
<KEY> is not a valid HTTP header name because it
contains at least one invalid character.
|
| ERR_NGROK_1624 |
<VAL> is not a valid HTTP header value:
<REASON>.
|
| 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 <T> requires a secret.
|
| ERR_NGROK_1628 |
There were validation errors while saving the endpoint
configuration:<ERRS>
|
| ERR_NGROK_1629 |
You must specify a supported provider name. Supported providers:
[<T>]
|
| ERR_NGROK_1630 |
Webhook provider <T> is not supported. Supported
providers: [<TYPE>]
|
| ERR_NGROK_1631 | Only Pro or Enterprise accounts can use webhook validation. Your account is not authorized to use webhook validation. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1632 |
You may not configure the TLS termination parameter
<PARAMETER> when the HTTPS module disables TLS
termination.
|
| 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 <MIN>, was <ACTUAL>.
|
| ERR_NGROK_1636 |
Invalid endpoint configuration, OAuth may only have one provider
configuration but multiple are defined:
[<PROVIDER_NAMES>].
|
| 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
<PROVIDER> requires at least the
<SCOPE> scope to authenticate by
<AUTH_FEATURE>.'
|
| ERR_NGROK_1639 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> contains an invalid email domain:
<NAME>.
|
| ERR_NGROK_1640 |
Invalid endpoint configuration, OAuth GitHub Teams must be listed as
either numerical ids or in the format 'org_slug/team_slug',
<TEAM> does not match either format.
|
| ERR_NGROK_1641 | Ony Pro or Enterprise accounts can use OAuth. Your account is not authorized to use OAuth. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1642 |
Invalid endpoint configuration, OAuth cookie prefix
<PREFIX> must consist of only alphanumeric characters
with periods.
|
| ERR_NGROK_1643 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> contains an invalid email address,
<NAME>.
|
| ERR_NGROK_1644 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> contains an email domain with invalid
punycode: <NAME>.
|
| ERR_NGROK_1645 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> contains an email address with invalid
punycode: <NAME>.
|
| ERR_NGROK_1646 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> email addresses must be unique, but a
duplicate is present: <DUPLICATE>.
|
| ERR_NGROK_1647 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> email domains must be unique, but a
duplicate is present: <DUPLICATE>.
|
| ERR_NGROK_1648 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> teams must be unique, but a duplicate is
present: <DUPLICATE>.
|
| ERR_NGROK_1649 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> organizations must be unique, but a
duplicate is present: <DUPLICATE>.
|
| ERR_NGROK_1650 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> groups must be unique, but a duplicate is
present: <DUPLICATE>.
|
| ERR_NGROK_1651 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> email addresses must not contain empty
values
|
| ERR_NGROK_1652 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> email domains must not contain empty
values
|
| ERR_NGROK_1653 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> teams must not contain empty values
|
| ERR_NGROK_1654 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> organizations must not contain empty
values
|
| ERR_NGROK_1655 |
Invalid endpoint configuration, OAuth provider
<PROVIDER> groups must not contain empty values
|
| ERR_NGROK_1656 |
The endpoint configuration exceeds the maximum number of OAuth scopes.
You specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_1657 |
The endpoint configuration exceeds the maximum number of OAuth Github
teams. You specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_1658 |
The endpoint configuration exceeds the maximum number of OAuth Github
orgs. You specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_1659 |
The endpoint configuration exceeds the maximum number of OAuth Google
groups. You specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_1660 |
The endpoint configuration exceeds the maximum number of OAuth emails.
You specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_1661 |
The endpoint configuration exceeds the maximum number of OAuth domains.
You specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_1662 |
The endpoint configuration specifies the following modules which may not
be enabled when TLS is not terminated:
<MODULE_NAMES>.
|
| ERR_NGROK_1667 |
Invalid endpoint configuration, email addresses must be lowercase but
<EMAIL> is not.
|
| ERR_NGROK_1668 |
Invalid endpoint configuration, email domains must be lowercase but
<DOMAIN> is not.
|
| ERR_NGROK_1669 |
Duplicate 'add' header, <HEADER> was provided twice
with different casings: <CASE_ONE> and
<CASE_TWO>.
|
| ERR_NGROK_1670 |
Your account is limited to <MAX> endpoint
configurations.
|
| ERR_NGROK_1672 |
The CA ID <ID> specified for the Mutual TLS module
does not exist.
|
| ERR_NGROK_1673 |
Description is limited to <MAX> characters; you have
entered <VAL> characters.
|
| ERR_NGROK_1674 |
Metadata is limited to <MAX> characters; you have
entered <VAL> characters.
|
| ERR_NGROK_1675 |
The Mutual TLS configurations exceeds the limit of
<LIMIT> attached certificate authorities.
|
| 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 16834 bytes, got
<NBYTES>.
|
| 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 <MDURL>:
<ERR>.
|
| ERR_NGROK_1683 |
Failed to parse the SAML IdP metadata: <ERR>.
|
| ERR_NGROK_1684 |
Received unexpected status code <STATUSCODE> while
fetching metadata URL <MDURL>
|
| ERR_NGROK_1685 |
Failed to parse the SAML IdP metadata fetched from URL
<MDURL>: <ERR>.
|
| ERR_NGROK_1686 |
Encountered an error while reading the response body from the IdP
metadata URL <MDURL>: <ERR>.
|
| ERR_NGROK_1687 |
The specified OIDC issuer has a maximum length of 255 bytes. The
specified value is <N> bytes.
|
| 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 <ACTUAL>.
|
| ERR_NGROK_1693 |
"<FORMAT>" is not a supported SAML nameid format.
|
| 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 <PREFIX>...' exceeds the
maximum header name length of 128 bytes.
|
| ERR_NGROK_1698 |
The header value for <HEADERKEY> beginning with
<PREFIX>...' exceeds the maximum header value length
of 1024 bytes.
|
| 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:
"<ERROR>"
|
| ERR_NGROK_1700 | Only Enterprise accounts can use session operations. Your account is not authorized to use session operations. Upgrade to an Enterprise 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 plan at https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1702 | Only Enterprise accounts can update the agent. Your account is not authorized to update the agent. Upgrade to an Enterprise plan at https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1800 |
You have reached the maximum of <MAX> IP Policies on
a restriction.
|
| ERR_NGROK_1801 |
Invalid IP Restriction. The policy <POLICY_ID> does
not exist on your account.
|
| ERR_NGROK_1802 |
Only one IP Restriction is allowed per type. Consider either deleting
the existing <TYPE> restriction first, or updating it
instead.
|
| ERR_NGROK_1803 |
The provided IP Restriction type "<TYPE>" is invalid.
Valid types: <SUPPORTED>.
|
| 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. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1806 | Only Pro or Enterprise accounts can use API IP restrictions. Your account is not authorized to use API IP restrictions. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1807 | Only Pro or Enterprise accounts can use agent IP restrictions. Your account is not authorized to use agent IP restrictions. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1808 | Only Pro or Enterprise accounts can use endpoints IP restrictions. Your account is not authorized to use endpoints IP restrictions. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_1900 |
The provided certificate is in an unknown or unsupported format. The
error encountered while parsing was: "<ERROR>"
|
| 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 <DOMAIN> is not a valid domain name.
|
| ERR_NGROK_1907 |
The ip <IP> is not a valid IP address.
|
| ERR_NGROK_1908 |
Invalid authority <AUTHORITY>. Valid authorities:
<SUPPORTED>.
|
| ERR_NGROK_1909 |
Invalid private key type <TYPE>. Valid types:
<SUPPORTED>.
|
| 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:
<TYPE>. It must be "CERTIFICATE".
|
| ERR_NGROK_1912 |
The upload contained <COUNT> certificates:
<CNS>. Only a single certificate may be uploaded at a
time.
|
| 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 <MAX> characters, but
the provided value had <VAL> characters.
|
| ERR_NGROK_1915 |
Metadata is limited to <MAX> characters, but the
provided value had <VAL> characters.
|
| ERR_NGROK_1916 |
The description is limited to <MAX> characters, but
the provided value had <VAL> characters.
|
| ERR_NGROK_1917 |
Metadata is limited to <MAX> characters, but the
provided value had <VAL> characters.
|
| 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:
"<PREFIX>".
|
| ERR_NGROK_1921 |
The uploaded certificate PEM data exceeds the maximum length limit of
<MAX_SIZE> bytes.
|
| 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: [<ORDER>], however
<INVALID> has not been signed by
<INTERMEDIATE>.
|
| ERR_NGROK_1927 |
The domain <DOMAIN> is not available for certificate
management.
|
| ERR_NGROK_1929 |
Invalid nameserver count. There should be <WANT> but
only found <GOT> for <ZONE>
|
| ERR_NGROK_1930 |
Nameservers are not set up correctly for <DOMAIN>,
expected <WANT> but got <GOT>
|
| ERR_NGROK_1934 |
Got error <ERROR> where parsing public key
<PUBLICKEY>
|
| ERR_NGROK_1935 |
<CERTTYPE> is not a valid SSH certificate type. Valid
certificate types: <SUPPORTED>.
|
| ERR_NGROK_1936 |
"<KEYTYPE>" is not a valid SSH key type. Valid key
types: <SUPPORTED>.
|
| ERR_NGROK_1937 |
The description is limited to <MAX> characters, but
the provided value had <VAL> characters.
|
| ERR_NGROK_1938 |
Metadata is limited to <MAX> characters, but the
provided value had <VAL> characters.
|
| ERR_NGROK_1939 |
Invalid key size <KEYSIZE>. Valid key sizes:
<SUPPORTED>.
|
| ERR_NGROK_1940 |
Key size is supported only with a key type of "rsa", but the specified
key type was "<KEYTYPE>".
|
| ERR_NGROK_1941 |
Invalid elliptic curve "<CURVE>". Valid elliptic
curves: <SUPPORTED>.
|
| ERR_NGROK_1942 |
Elliptic curve is supported only with a key type of "ecdsa", but the
specified key type was "<KEYTYPE>".
|
| ERR_NGROK_1943 |
The SSH CA Certificate duration must be greater than zero; got duration
of <DURATION>.
|
| ERR_NGROK_1945 |
The description is limited to <MAX> characters, but
the provided value had <VAL> characters.
|
| ERR_NGROK_1946 |
Metadata is limited to <MAX> characters, but the
provided value had <VAL> characters.
|
| ERR_NGROK_1947 |
The description is limited to <MAX> characters, but
the provided value had <VAL> characters.
|
| ERR_NGROK_1948 |
Metadata is limited to <MAX> characters, but the
provided value had <VAL> characters.
|
| ERR_NGROK_1949 |
The SSH CA <CA> does not exist.
|
| ERR_NGROK_1950 |
Certificates are not supported for public keys of type
<KEYTYPE>.
|
| ERR_NGROK_1951 |
The SSH CA <CA> does not exist.
|
| 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 <MAX> Certificate
Authorities.
|
| ERR_NGROK_1956 |
Your account is limited to <MAX> SSH Certificate
Authorities.
|
| ERR_NGROK_1958 |
Your account is limited to <MAX> SSH Host
Certificates.
|
| ERR_NGROK_1960 |
Your account is limited to <MAX> SSH User
Certificates.
|
| ERR_NGROK_1962 |
SSH User Certificate duration must be greater than zero; got duration of
<DURATION>.
|
| ERR_NGROK_1963 |
SSH Host Certificate duration must be greater than zero; got duration of
<DURATION>.
|
| ERR_NGROK_1964 |
Can't delete SSH CA <ID> because an SSH certificate
signed by it exists. Delete all host and user SSH certificates signed by
this CA before deleting it.
|
| ERR_NGROK_1965 |
The certificate <ID> does not exist.
|
| ERR_NGROK_2062 |
Paths given in HTTPMux rules must be either empty or absolute. Perhaps
you meant to specify '/<PATH>?
|
| ERR_NGROK_2063 |
The method <METHOD> was specified multiple times for
the path <PATH>. Each method must be unique among all
rules with the same path.
|
| ERR_NGROK_2065 | HTTPMux must have at least one rule. |
| ERR_NGROK_2067 |
Too many rules given to HTTPMux. You provided
<VAL> rules, but the limit is
<MAX>.
|
| ERR_NGROK_2069 |
The method (<METHOD>) specified in an HTTPMux rule is
invalid or otherwise not currently supported.
|
| ERR_NGROK_2070 |
The path specified in an HTTPMux rule is too long. The path provided has
<VAL> bytes, but the limit is
<MAX>.
|
| ERR_NGROK_2071 | The path specified in an HTTPMux rule is unsupported or otherwise invalid. |
| ERR_NGROK_2089 | Found duplicate routing rule. Each rule must be unique. |
| ERR_NGROK_3002 |
Error performing TLS handshake: <ERR>
|
| 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#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
<CODE> from a backend
|
| ERR_NGROK_3100 |
Your session has expired due to age. Refresh this page or use the link
below to log back in with <PROVIDER>.
|
| ERR_NGROK_3101 |
We lack permission to retrieve your data from
<PROVIDER> and cannot continue. Make sure to allow
all requested permissions for this application.
|
| ERR_NGROK_3102 |
<PROVIDER> requires that you correct an issue with
your account prior to using this website. Please log in to
<PROVIDER>, correct the issue, and then refresh this
page.
|
| ERR_NGROK_3103 |
<PROVIDER> requires that you correct an issue with
your account prior to using this website:
<ERROR_TITLE>: <ERROR_MESSAGE>
After correcting the issue with <PROVIDER>, refresh
this page.
|
| ERR_NGROK_3104 |
The email "<EMAIL>" associated with your
<PROVIDER> account is not valid. Please correct your
email with <PROVIDER> and then refresh this page.
|
| 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
<PROVIDER> is invalid.
|
| 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 |
<PROVIDER> did not provide an email for your account.
Check that you have a primary email and that it's confirmed before
trying again.
|
| ERR_NGROK_3110 |
The email permission from <PROVIDER> was not granted
but is required. Please ensure that the email permission is granted.
|
| ERR_NGROK_3111 |
All requested permissions with <PROVIDER> must be
granted in order to use this site, but the following were not:
<PERMISSIONS>.
|
| ERR_NGROK_3112 |
<PROVIDER> has returned an error when attempting to
authorize you to use this site:
<ERROR>
|
| ERR_NGROK_3113 |
<PROVIDER> denied access to this application when
retrieving your information. This is likely caused by expiration or
revocation of your authorization.
|
| ERR_NGROK_3114 |
In order to continue, you must authorize this application's access to
<PROVIDER>.
|
| ERR_NGROK_3115 |
The redirect_uri configured for this application is not properly
configured or whitelisted with <PROVIDER>. Please
contact the owner of this application in order to fix this error.
|
| ERR_NGROK_3116 |
<PROVIDER> denied access to your data when attempting
to authorize you. Please contact the owner of this application to ensure
it is properly installed for your organization.
|
| ERR_NGROK_3117 |
The initial link used to authorize with
<PROVIDER> had unsupported parameters.
|
| ERR_NGROK_3118 |
<PROVIDER> denied access to your data. Please contact
the owner of this application to ensure it is properly installed for
your organization.
|
| ERR_NGROK_3119 |
Logging in with <PROVIDER> took more than 15 minutes
and was rejected for security. Please try again.
|
| ERR_NGROK_3120 |
The state parameter required to finish authorization with
<PROVIDER> is missing. Please start over to try
again.
|
| ERR_NGROK_3121 |
The nonce cookie required to finish authorization with
<PROVIDER> is missing. Please start over to try
again.
|
| ERR_NGROK_3122 |
The access code from <PROVIDER> has expired and
cannot be used. Please try again and finish authorization more quickly.
|
| ERR_NGROK_3123 |
The access code from <PROVIDER> has already been
used. Please remove any bookmarks to this page and start reauthorization
again.
|
| ERR_NGROK_3124 |
The state parameter required to finish authorization with
<PROVIDER> does not match this host. Please try
again.
|
| ERR_NGROK_3125 |
<PROVIDER> denied access to your data. The owner of
this application should verify the OAuth application client ID and
secret are valid.
|
| ERR_NGROK_3126 |
<PROVIDER> rejected authorization due to a invalid or
unknown scope requested by this application. The owner of this
application must correct the application configuration before you can
continue.
|
| ERR_NGROK_3127 |
<PROVIDER> rejected authorization due to invalid or
expired credentials. If this error persists after reauthorizing, contact
the owner of the application to ensure you have permission.
|
| ERR_NGROK_3150 | An error occurred when retrieving your session. Please refresh the page to log in and try again. |
| ERR_NGROK_3151 |
<PROVIDER> rejected use of your session's OAuth
token: "<ERROR>". Your session is invalid and cannot
continue.
|
| ERR_NGROK_3152 |
An invalid request was sent to <PROVIDER> but its
response is required in order to continue. This is a bug and it has been
reported; please try again in a couple of hours to see if it has been
resolved.
|
| ERR_NGROK_3160 |
An unexpected error occurred when communicating with
<PROVIDER>.
|
| ERR_NGROK_3161 |
<PROVIDER> has throttled this application and cannot
be reached right now. Please try again in a few minutes.
|
| ERR_NGROK_3162 |
<PROVIDER> has throttled this application and cannot
be reached right now. Please try again in about an hour.
|
| ERR_NGROK_3163 |
An error occurred when finishing authorization with
<PROVIDER>. This is likely caused by authorization
taking too long. Please try again.
|
| ERR_NGROK_3164 |
An error occurred when authorizing with <PROVIDER>:
<ERROR>
|
| ERR_NGROK_3165 |
<PROVIDER> is too busy to handle requests and
authorization cannot be completed at this time.
|
| ERR_NGROK_3166 |
<PROVIDER> enountered an error and authorization
cannot be completed at this time.
|
| ERR_NGROK_3167 |
<PROVIDER> is too busy to handle requests and
required data cannot be retrieved right now. Wait a few minutes before
trying again.
|
| ERR_NGROK_3200 |
Tunnel <HOSTNAME> not found
|
| 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_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 `<TYP>` is incompatible with
OAuth, OIDC, or SAML. Compatible selector match types are "EXACT_PATH"
or "PATH_PREFIX".
|
| ERR_NGROK_4001 |
Plan <PLAN_ID> does not exist.
|
| ERR_NGROK_4003 | Account name must not be empty. |
| ERR_NGROK_4004 |
Account name exceeds max length, <LENGTH> bytes, max:
<MAX>.
|
| ERR_NGROK_4005 |
Another account is already configured with the GSuite domain
<DOMAIN>.
|
| ERR_NGROK_4011 | Your password must be at least 10 characters. |
| ERR_NGROK_4012 |
Your account does not have access to <FEATURE>.
Upgrade to get access: https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_4013 |
You may not create a new account because you are already a member of the
free account "<ACCOUNT_NAME>". Upgrade or delete that
account first before creating a new account.
|
| ERR_NGROK_4014 |
The account <NAME> was suspended. It may not be
deleted. Contact support@ngrok.com if you believe this is an error.
|
| ERR_NGROK_4015 |
The account <NAME> was banned for violation of the
terms of service. It may not be deleted. Contact support@ngrok.com if
you believe this is an error.
|
| ERR_NGROK_4016 | You may not create a new account because another account you were the administator 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 | You must signup for ngrok and add your authtoken to perform this operation. Sign up for an account: https://dashboard.ngrok.com/signup Install your authoken: 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_4100 | The email or password you entered is not valid. |
| ERR_NGROK_4101 |
A user with the email address <EMAIL> already exists.
|
| ERR_NGROK_4103 |
<EMAIL> is not a valid email address.
|
| ERR_NGROK_4104 | User name must not be empty. |
| ERR_NGROK_4105 |
User name exceeds max length, <LENGTH> bytes, max:
<MAX>.
|
| ERR_NGROK_4108 |
Sign ups are disallowed for the email provider
"<DOMAIN>". Please sign up with a different email
provider.
|
| ERR_NGROK_4200 | You may not delete all or your logins, you must have at least one. |
| ERR_NGROK_4201 |
This <LOGIN> login is already connected to another
ngrok user.
|
| ERR_NGROK_4300 |
No user with the email address <EMAIL> exists.
|
| ERR_NGROK_4301 | This account does not support a password reset. |
| ERR_NGROK_4302 |
Unable to redeem password: <REASON>
|
| ERR_NGROK_4400 | An email address is required to invite a new user |
| ERR_NGROK_4401 |
The invited email address is too long:
<LENGTH> bytes. Max <MAX> bytes.
|
| ERR_NGROK_4402 |
The invited user would exceed your team size limit of
<TEAM_SIZE>. Delete unused invitations or users to
make room, or upgrade to a Pro or Enterprise plan:
https://dashboard.ngrok.com/billing/subscription
|
| 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: <REASON>
|
| ERR_NGROK_4405 |
<EMAIL> is not a valid email address.
|
| ERR_NGROK_4407 | You are not currently permitted to enroll in the beta. |
| ERR_NGROK_4408 |
Feature request suggestions must be between 1 and
<MAXLEN> characters, got <LENGTH>.
|
| 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_4451 |
A user with the email address <EMAIL> already exists.
|
| ERR_NGROK_4452 |
The email address being verified, <EMAIL>, belongs to
another user.
|
| ERR_NGROK_4500 |
The URL <URL> is not a valid tcp address or URL.
Please use either hostname:port or a full URL including protocol for
HTTP or TLS endpoints.
|
| ERR_NGROK_4501 |
The TCP port <PORT> in <HOST> is
not a valid numerical TCP port.
|
| ERR_NGROK_4502 |
The TCP port <PORT> for <HOST> is
not within the range of possible ngrok ports.
|
| ERR_NGROK_4503 |
The IP <IP> is not a known ngrok TCP IP.
|
| ERR_NGROK_4504 |
The host <HOST> is not a known ngrok TCP hostname.
|
| ERR_NGROK_5000 |
Your account is limited to <MAX>
<RESOURCE>.
|
| ERR_NGROK_5001 |
Your account is rate limited to <MAX>
<RESOURCE> per <INTERVAL>.
|
| ERR_NGROK_5100 |
An event destination must specify a destination target. Valid targets
include: <TYPE>.
|
| ERR_NGROK_5102 |
You have reached the maximum of <MAX> destinations
for your account.
|
| ERR_NGROK_5103 |
No event destinations with ID: <ID> associated with
this account.
|
| ERR_NGROK_5104 |
Event Destination role ARN "<ARN>" is not a valid ARN
for an aws IAM role. Error: <MSG>.
|
| 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 "<ID>" cannot be deleted because it
is still in use by at least one Event Stream
|
| 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 <NAME> is an immutable property and may
not be updated. Create a new destination instead.
|
| ERR_NGROK_5118 |
The partition (<VALUE>) of the provided
<FIELD> (<ARN>) is invalid.
|
| ERR_NGROK_5119 |
The service (<VALUE>) of the provided
<FIELD> (<ARN>) is invalid.
|
| ERR_NGROK_5120 |
The provided <FIELD> (<ARN>) is
invalid. Please make sure it matches the ARN you obtained from Amazon
exactly.
|
| ERR_NGROK_5122 | <ERR> |
| ERR_NGROK_5123 |
Event Subscription <ID> not found.
|
| ERR_NGROK_5124 | Your account can't use the event subscriptions feature. |
| ERR_NGROK_5125 |
Source <TYP> not found on Event Subscription
<ID>.
|
| ERR_NGROK_5126 |
You have reached the maximum of <MAX> destinations on
a subscription.
|
| 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 (<ARN>) is not valid for the
<SERVICE> service.
|
| ERR_NGROK_5130 |
The ARN (<ARN>) is not valid for the
<RESOURCE> resource type.
|
| ERR_NGROK_5131 |
You have reached the maximum of <MAX> event
subscriptions for your account.
|
| 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:
"<ERROR>".
|
| ERR_NGROK_5203 | The OIDC provider failed to return a OIDC ID Token. |
| ERR_NGROK_5204 |
Failed to verify the OIDC ID Token: "<ERROR>".
|
| ERR_NGROK_5205 |
Failed to extract claims from the OIDC ID Token:
"<ERROR>".
|
| ERR_NGROK_5206 |
The endpoint configuration "<ECID>" does not exist.
|
| ERR_NGROK_5207 |
OIDC is not enabled on the endpoint configuration
"<ECID>".
|
| ERR_NGROK_5208 |
Encountered an error while attempting to fetch OIDC provider metadata:
"<ERROR>".
|
| 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 "<ERROR>"
with the additional details: "<DETAILS>". Please try
authenticating again.
|
| ERR_NGROK_5212 |
OIDC is not enabled on the domain "<HOSTNAME>".
|
| ERR_NGROK_5300 | SAML RelayState parameter is invalid. |
| ERR_NGROK_5301 |
The SAML IdP sent an invalid SAML assertion:
"<ERROR>"
|
| ERR_NGROK_5302 |
The SAML module for the endpoint configuration
"<ECID>" disallows IdP-initiated logins.
|
| ERR_NGROK_5303 |
The endpoint configuration "<ECID>" is not attached
to any domains.
|
| ERR_NGROK_5304 |
Could not find the domain "<DOMAIN>" specified in the
IdP-initiated RelayState.
|
| ERR_NGROK_5305 |
The SAML IdP sent an invalid SAML assertion:
"<ERROR>"
|
| ERR_NGROK_5306 | SAML RelayState parameter is invalid. |
| ERR_NGROK_5307 |
The domain "<DOMAIN>" specified in the IdP-initiated
RelayState is not attached to the endpoint configuration
"<ECID>".
|
| ERR_NGROK_5308 |
The SAML IdP sent an invalid SAML logout response:
"<ERROR>"
|
| 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
<N> Authn statements.
|
| ERR_NGROK_5312 | Your are not a member of the configured authorized groups on the ngrok endpoint configuration. |
| 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 "<RTEID>"
disallows IdP-initiated logins.
|
| ERR_NGROK_5318 |
The edge "<EDGID>" is not attached to any domains.
|
| ERR_NGROK_5319 |
Failed to complete IdP-initiated SAML login. The RelayState specified an
invalid domain "<DOMAIN>" to redirect to. Ensure that
the domain "<DOMAIN>" is configured as a hostport for
"<EDGID>".
|
| ERR_NGROK_5320 |
The edge route "<RTEID>" does not exist.
|
| ERR_NGROK_5321 | The RelayState must be configured with the redirect URL for IdP-initiated logins. |
| ERR_NGROK_5322 |
The domain "<DOMAIN>" specified in the IdP-initiated
RelayState is not attached to the edge "<EDGID>".
|
| ERR_NGROK_5323 |
The SAML module is not enabled for the configuration
"<ID>".
|
| ERR_NGROK_5324 |
The ID "<ID>" that was specified is invalid. This
usually indicates a malformed URL.
|
| 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 "<EDGID>".
|
| 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 "<MATCHTYP>".
|
| ERR_NGROK_5400 |
Event Sources for the "<TYP>" event type must specify
fields to capture.
|
| ERR_NGROK_5401 |
Event Sources for the "<TYP>" event may not specify
fields.
|
| ERR_NGROK_5402 |
Event Sources for the "<TYP>" event may not specify a
filter.
|
| ERR_NGROK_5403 |
Event Sources must be configured with fields that match its event type.
"<FIELD>" is not a "<TYP>" field
|
| ERR_NGROK_5404 |
Event Source filter is invalid: "<ERR>"
|
| ERR_NGROK_5405 |
Invalid Event Field: "<FIELD>"
|
| ERR_NGROK_5406 |
Field is not yet supported in event filters:
"<FIELD>"
|
| 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 <PROVIDER> succeeded, but these
required scopes not were granted: <SCOPES>. Please
reauthorize and grant all requested scopes to the application.
|
| 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 <PROVIDER> succeeded, but these
required scopes not were granted: <SCOPES>. Please
reauthorize and grant all requested scopes to the application.
|
| ERR_NGROK_5510 |
<PROVIDER> did not provide an email for your account.
Check that you have a primary email and that it's confirmed before
trying again.
|
| ERR_NGROK_5511 |
Email "<EMAIL>" is not authorized for use by this
account.
|
| ERR_NGROK_5512 |
Email is malformed. Email "<EMAIL>" is missing an @
sign.
|
| ERR_NGROK_5513 |
Email domain failed to normalize to a FQDN
"<DOMAIN>": "<ERROR>"
|
| ERR_NGROK_5517 |
<PROVIDER> denied access to your data during the
final step of authorization: <DESCRIPTION>. Please
contact the owner of this application to ensure it is properly installed
for your organization.
|
| ERR_NGROK_5518 |
<PROVIDER> rejected authorization with access denied:
<DESCRIPTION>. You must authorize this application
before continuing.
|
| ERR_NGROK_5520 |
<PROVIDER> rejected authorization due to a invalid or
unknown scope requested by this application:
<DESCRIPTION>. The owner of this application must
correct the application configuration before you can continue.
|
| ERR_NGROK_5521 |
<PROVIDER> rejected authorization due to an internal
server error: <DESCRIPTION>.
|
| ERR_NGROK_5522 |
<PROVIDER> is too busy to handle requests and
authorization cannot be completed at this time:
<DESCRIPTION>.
|
| ERR_NGROK_5523 |
<PROVIDER> rejected authorization as the redirect URL
for this application is improperly configured:
<DESCRIPTION>. Please contact the owner of this
application in order to fix this error.
|
| ERR_NGROK_5524 |
<PROVIDER> rejected authorization:
<DESCRIPTION>. The owner of this application should
verify the OAuth application client ID and secret are valid before you
can continue.
|
| ERR_NGROK_5525 |
<PROVIDER> has throttled this application and cannot
be reached right now. Please try again in a few minutes.
|
| ERR_NGROK_5526 |
<PROVIDER> rejected access to your information. This
is likely caused by expiration or revocation of your authorization.
|
| ERR_NGROK_5527 |
<PROVIDER> rejected the final step of authorization
due to invalid credentials. The owner of this application should verify
the OAuth application client ID and secret are valid before you can
continue.
|
| ERR_NGROK_5528 |
The access code from <PROVIDER> has expired and
cannot be used. Please authorize again more quickly.
|
| ERR_NGROK_5529 |
<PROVIDER> denied access to your data during the
final step of authorization. Please contact the owner of this
application to ensure it is properly installed for your organization.
|
| ERR_NGROK_5530 |
OAuth is not enabled on the domain "<HOSTNAME>".
|
| ERR_NGROK_5531 |
<PROVIDER> denied access to your account as the
correct account could not be chosen automatically. Please try
authorizing again or contacting the owner of this application if the
issue persists.
|
| ERR_NGROK_5532 |
<PROVIDER> denied access to your account as
reauthentication is required. Please try logging in again or contact the
owner of this application if the issue persists.
|
| ERR_NGROK_5533 |
<PROVIDER> had an internal server error when
refreshing your information. Please try again or contact the owner of
this application if the issue persists.
|
| ERR_NGROK_5534 |
Encountered an error while attempting to fetch OIDC provider metadata:
"<ERROR>".
|
| ERR_NGROK_5535 |
The OAuth provider "<PROVIDER>" cannot be used
without a user-defined client ID and client secret.
|
| 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 <EDID> required by
<ECID> was not found. If these were recently created
or removed, this should be temporary and resolve itself.
|
| ERR_NGROK_6008 | This endpoint is unavailable as its account is suspended due to lack of payment. |
| ERR_NGROK_6009 | This endpoint is unavailable as its account is suspended. |
| ERR_NGROK_6010 |
Endpoint configuration is incompatible with tunnel; module
<MODULE> required by Endpoint Configuration
<ECID> is incompatible with
<PROTO> tunnels.
|
| ERR_NGROK_6011 |
You may not specify <MIDDLEWARE> options from the
ngrok agent because this domain has a configured endpoint configuration:
<ECID>. Remove the endpoint configuration from this
domain or remove the conflicting options when starting the ngrok agent.
|
| ERR_NGROK_6013 |
Failed to compile filter for Event Subscription
<ESID>.
|
| ERR_NGROK_6014 |
Failed to run filter for Event Subscription <ESID>.
|
| ERR_NGROK_6018 |
The Endpoint <HOSTPORT> has both an Endpoint
Configuration (<EPCID>) and a Tunnel with
incompatible configuration (<TUNNELID>) online.
|
| ERR_NGROK_6019 |
The Endpoint <HOSTPORT> has both an Edge
(<EDGID>) and Endpoint Configuration
(<EPCID>) configured.
|
| ERR_NGROK_6020 |
The Endpoint <HOSTPORT> has both an Edge
(<EDGID>) and Tunnel (<TUNID>)
online.
|
| 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_6500 | Your account is not authorized to use the backends feature. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_6501 |
Cannot save backend reference <ID> because it does
not exists.
|
| 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 <MAX> characters; you have
entered <VAL> characters.
|
| ERR_NGROK_6504 |
Metadata is limited to <MAX> characters; you have
entered <VAL> characters.
|
| ERR_NGROK_6505 | Static backend requires address in the host:port form. |
| ERR_NGROK_6506 |
Static backend address <ADDR> is invalid
(<REASON>). Use host:port as address.
|
| ERR_NGROK_6507 |
Static backend address <ADDR> is missing host. Use
host:port as address.
|
| ERR_NGROK_6508 |
Tunnel group labels count is limited to <MAX>; you
have <VAL> labels.
|
| ERR_NGROK_6509 |
Tunnel group label key length is limited to <MAX>;
key <NAME> has <VAL> characters.
|
| ERR_NGROK_6510 |
Tunnel group label value length is limited to <MAX>;
value <NAME> has <VAL> characters.
|
| ERR_NGROK_6511 |
Weighted backends count is limited to <MAX>; you have
<VAL> backends.
|
| ERR_NGROK_6512 |
Weighted backend <ID> weight
<VAL> is out of range; it must be between
<MIN> and <MAX>.
|
| ERR_NGROK_6513 |
Failover backends may only contain up to
<MAX> failover backends; you have
<VAL> failover backends.
|
| ERR_NGROK_6514 | Backend not found. |
| ERR_NGROK_6515 |
Tunnel Group Backend <ID> did not match any tunnels.
Please start tunnels matching its labels in order to serve traffic.
|
| ERR_NGROK_6516 |
HTTP Reseponse Backend <ID> had too large of a body.
The maximum is length <MAX> bytes, but the supplied
body was <VAL> bytes long.
|
| ERR_NGROK_6517 |
HTTP Response Backend <ID> had an invalid status
code. The status code <STATUS> is an invalid HTTP
Status Code.
|
| ERR_NGROK_6522 |
The header beginning with <PREFIX>...' exceeds the
maximum header name length of 128 bytes.
|
| ERR_NGROK_6523 |
The header value for <HEADERKEY> beginning with
<PREFIX>...' exceeds the maximum header value length
of 1024 bytes.
|
| ERR_NGROK_6524 |
A Weighted Backend may not reference the backend
<ID> because it is a
<BACKENDTYPE> backend.
|
| ERR_NGROK_6525 |
A Failover Backend may not reference the backend
<ID> because it is a
<BACKENDTYPE> backend.
|
| ERR_NGROK_6526 |
The id <ID> is not a valid backend ID.
|
| ERR_NGROK_6527 |
The id <ID> is invalid; expected an id of type
<BACKENDTYPE> backend.
|
| ERR_NGROK_6528 | Traffic made it to the ngrok edge, but there are no tunnels online serving an app. |
| ERR_NGROK_6600 |
The account <NAME> has reached its team size limit
and may not add additional users. Please ask the account owner to
upgrade your plan: https://dashboard.ngrok.com/billing/subscription
|
| ERR_NGROK_6601 |
Failed to add <USER_NAME> as a member of account
<ACCOUNT_NAME> because they are already a member.
|
| 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
<ID> because it could not be found on this account.
|
| 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_6700 |
The description is limited to <MAX> characters, but
the provided value had <VAL> characters.
|
| ERR_NGROK_6701 |
Metadata is limited to <MAX> characters, but the
provided value had <VAL> characters.
|
| ERR_NGROK_6702 |
No DNS records were returned when querying for an NS record for the
domain <DOMAIN>.
|
| ERR_NGROK_6703 |
The NS records for the domain
<DOMAIN> "<GOT>" do not match the
expected targets "<EXPECTED>".
|
| ERR_NGROK_6704 |
The specified domain "<DOMAIN>" is not a valid domain
name. Enter a valid DNS name.
|
| ERR_NGROK_6705 |
The agent ingress domain "<DOMAIN>" must be a third
party domain, you may not enter a domain controlled by ngrok.
|
| ERR_NGROK_6706 |
The agent ingress domain "<DOMAIN>" already exists,
choose another domain.
|
| 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 <ID> specified for the IP
Restriction module does not exist.
|
| 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 <MAX> edges.
|
| ERR_NGROK_7011 |
Invalid edge, circuit breaker error threshold percentage must be between
0.0 and 1.0 inclusive, was <VAL>.
|
| ERR_NGROK_7012 |
The auth provider <VAL> does not exist. Specify an
auth provider ID or the special value 'agent'.
|
| ERR_NGROK_7013 |
The edge module exceeds the max number of IP Policies. You specified
<VAL>, the maximum is <MAX>.
|
| ERR_NGROK_7014 |
The edge module TLS CA certificate size exceeds the max. You specified
<VAL>, the maximum is <MAX>.
|
| ERR_NGROK_7015 |
The edge module exceeds the max number of headers. You specified
<VAL>, the maximum is <MAX>.
|
| ERR_NGROK_7016 |
Invalid edge module, circuit breaker tripped duration must be greater
than 0, was <VAL>.
|
| ERR_NGROK_7017 |
Invalid edge module, circuit breaker rolling window must be greater than
0, was <VAL>.
|
| ERR_NGROK_7018 |
Invalid edge module, circuit breaker num buckets must be greater than 0
and less than <MAX>, was <VAL>.
|
| 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 <NAME> is not supported on an edge of type
<TYPE>.
|
| ERR_NGROK_7022 |
<NAME> is not a valid edge type. Must be one of
'http', 'https', 'tcp'.
|
| ERR_NGROK_7023 |
<KEY> is not a valid HTTP header name because it
contains at least one invalid character.
|
| ERR_NGROK_7024 |
<VAL> is not a valid HTTP header value:
<REASON>.
|
| 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 <T> requires a secret.
|
| ERR_NGROK_7028 |
There were validation errors while saving the edge:<ERRS>
|
| ERR_NGROK_7029 |
You must specify a supported provider name. Supported providers:
[<T>]
|
| ERR_NGROK_7030 |
Webhook provider <T> is not supported. Supported
providers: [<TYPE>]
|
| ERR_NGROK_7031 | Only Pro and Enterprise accounts can use edges webhook verification. Your account is not authorized to use webhook verification. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_7032 |
You may not configure the TLS termination parameter
<PARAMETER> when the HTTPS module disables TLS
termination.
|
| 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
<MIN>, was <ACTUAL>.
|
| ERR_NGROK_7036 |
Invalid edge module, OAuth may only have one provider configuration but
multiple are defined: [<PROVIDER_NAMES>].
|
| 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
<PROVIDER> requires at least the
<SCOPE> scope to authenticate by
<AUTH_FEATURE>.'
|
| ERR_NGROK_7039 |
Invalid edge module, OAuth provider
<PROVIDER> contains an invalid email domain:
<NAME>.
|
| ERR_NGROK_7040 |
Invalid edge module, OAuth GitHub Teams must be listed as either
numerical ids or in the format 'org_slug/team_slug',
<TEAM> does not match either format.
|
| ERR_NGROK_7041 | Only Pro and Enterprise accounts can use edges OAuth. Your account is not authorized to use OAuth. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_7042 |
Invalid edge module, OAuth cookie prefix
<PREFIX> must consist of only alphanumeric characters
with periods.
|
| ERR_NGROK_7043 |
Invalid edge module, OAuth provider
<PROVIDER> contains an invalid email address,
<NAME>.
|
| ERR_NGROK_7044 |
Invalid edge module, OAuth provider
<PROVIDER> contains an email domain with invalid
punycode: <NAME>.
|
| ERR_NGROK_7045 |
Invalid edge module, OAuth provider
<PROVIDER> contains an email address with invalid
punycode: <NAME>.
|
| ERR_NGROK_7046 |
Invalid edge module, OAuth provider <PROVIDER> email
addresses must be unique, but a duplicate is present:
<DUPLICATE>.
|
| ERR_NGROK_7047 |
Invalid edge module, OAuth provider <PROVIDER> email
domains must be unique, but a duplicate is present:
<DUPLICATE>.
|
| ERR_NGROK_7048 |
Invalid edge module, OAuth provider <PROVIDER> teams
must be unique, but a duplicate is present:
<DUPLICATE>.
|
| ERR_NGROK_7049 |
Invalid edge module, OAuth provider
<PROVIDER> organizations must be unique, but a
duplicate is present: <DUPLICATE>.
|
| ERR_NGROK_7050 |
Invalid edge module, OAuth provider <PROVIDER> groups
must be unique, but a duplicate is present:
<DUPLICATE>.
|
| ERR_NGROK_7051 |
Invalid edge module, OAuth provider <PROVIDER> email
addresses must not contain empty values
|
| ERR_NGROK_7052 |
Invalid edge module, OAuth provider <PROVIDER> email
domains must not contain empty values
|
| ERR_NGROK_7053 |
Invalid edge module, OAuth provider <PROVIDER> teams
must not contain empty values
|
| ERR_NGROK_7054 |
Invalid edge module, OAuth provider
<PROVIDER> organizations must not contain empty
values
|
| ERR_NGROK_7055 |
Invalid edge module, OAuth provider <PROVIDER> groups
must not contain empty values
|
| ERR_NGROK_7056 |
The edge module exceeds the maximum number of OAuth scopes. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7057 |
The edge module exceeds the maximum number of OAuth GitHub teams. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7058 |
The edge module exceeds the maximum number of OAuth GitHub orgs. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7059 |
The edge module exceeds the maximum number of OAuth Google groups. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7060 |
The edge module exceeds the maximum number of OAuth emails. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7061 |
The edge module exceeds the maximum number of OAuth domains. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7062 |
The edge specifies the following modules which may not be enabled when
TLS is not terminated: <MODULE_NAMES>.
|
| ERR_NGROK_7067 |
Invalid edge module, email addresses must be lowercase but
<EMAIL> is not.
|
| ERR_NGROK_7068 |
Invalid edge module, email domains must be lowercase but
<DOMAIN> is not.
|
| ERR_NGROK_7069 |
Duplicate 'add' header, <HEADER> was provided twice
with different casings: <CASE_ONE> and
<CASE_TWO>.
|
| ERR_NGROK_7070 |
Your account is limited to <MAX> edges.
|
| ERR_NGROK_7071 |
Your account is rate limited for adding <MAX> edges
per <INTERVAL>.
|
| ERR_NGROK_7072 |
The CA ID <ID> specified for the Mutual TLS module
does not exist.
|
| ERR_NGROK_7073 |
Description is limited to <MAX> characters; you have
entered <VAL> characters.
|
| ERR_NGROK_7074 |
Metadata is limited to <MAX> characters; you have
entered <VAL> characters.
|
| ERR_NGROK_7075 |
The Mutual TLS configurations exceeds the limit of
<LIMIT> attached certificate authorities.
|
| 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
<MAX> bytes, got <NBYTES>.
|
| 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 <MDURL>:
<ERR>.
|
| ERR_NGROK_7083 |
Failed to parse the SAML IdP metadata: <ERR>.
|
| ERR_NGROK_7084 |
Received unexpected status code <STATUSCODE> while
fetching metadata URL <MDURL>
|
| ERR_NGROK_7085 |
Failed to parse the SAML IdP metadata fetched from URL
<MDURL>: <ERR>.
|
| ERR_NGROK_7086 |
Encountered an error while reading the response body from the IdP
metadata URL <MDURL>: <ERR>.
|
| ERR_NGROK_7087 |
The specified OIDC issuer has a maximum length of
<MAX> bytes. The specified value is
<N> bytes.
|
| 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 <ACTUAL>.
|
| 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': <INVALID>
|
| ERR_NGROK_7105 |
The header beginning with <PREFIX>...' exceeds the
maximum header name length of 128 bytes.
|
| ERR_NGROK_7106 |
The header value for <HEADERKEY> beginning with
<PREFIX>...' exceeds the maximum header value length
of 1024 bytes.
|
| 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:
"<ERROR>"
|
| 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 <EID> does not match the route
edge ID <REID>.
|
| ERR_NGROK_7111 |
The edge hostport <HOST>:<PORT>
does not exist.
|
| ERR_NGROK_7112 |
The hostport <HOSTPORT> has port out of range:
<PORT> is not in range 1-65535.
|
| ERR_NGROK_7113 |
The address <HOSTPORT> is not reserved.
|
| ERR_NGROK_7114 |
The address <HOSTPORT> is not reserved by your
account.
|
| ERR_NGROK_7115 |
The address <HOSTPORT> has an endpoint configuration
which must be removed before it can be used by an edge.
|
| ERR_NGROK_7116 |
The domain <HOSTPORT> is unsupported because it does
not use port 443.
|
| ERR_NGROK_7117 |
The domain <HOSTPORT> is not reserved.
|
| ERR_NGROK_7118 |
The domain <HOSTPORT> is not reserved by your
account.
|
| ERR_NGROK_7119 |
The domain <HOSTPORT> has an endpoint configuration
which must be removed before it can be used by an edge.
|
| ERR_NGROK_7120 |
TCP edges can only be associated with TCP addresses:
<HOSTPORT> is a domain.
|
| ERR_NGROK_7121 |
HTTPS edges can only be associated with reserved domains:
<HOSTPORT> is a TCP address.
|
| ERR_NGROK_7122 |
Hostport <HOSTPORT> already exists for another edge.
|
| ERR_NGROK_7123 | Edge routes require a match expression. |
| ERR_NGROK_7124 |
The edge route <ID> could not be found.
|
| ERR_NGROK_7125 |
There is a duplicate route <ID> for HTTPS edge.
|
| ERR_NGROK_7126 |
Route match expression <MATCH> must be unique across
all routes for HTTPS edge.
|
| ERR_NGROK_7127 |
OAuth may not currently be configured for any route except '/', could
not configure for route <MATCH>.
|
| ERR_NGROK_7128 |
Your account is limited to a maximum of <MAX> routes
for a single edge.
|
| ERR_NGROK_7129 |
Your account is limited to a maximum of
<MAX> hostports for a single edge.
|
| ERR_NGROK_7130 | Invalid match type, valid values are "exact_path" and "path_prefix". |
| ERR_NGROK_7131 |
The route selector expression `<MATCH>` is invalid.
Valid route selector match expressions are of the form /path (e.g.
"/foo", or "/foo/bar").
|
| ERR_NGROK_7132 |
The hostport `<HOSTPORT>` is already in use by an
agent directly.
|
| ERR_NGROK_7133 |
TLS edges can only be associated with reserved domains:
<HOSTPORT> is a TCP address.
|
| 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
<MAX>, got <SIZE>.
|
| ERR_NGROK_7136 |
The OAuth Cookie Prefix exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7137 |
The OAuth Client ID exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7138 |
The OAuth Client Secret exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7139 |
The OAuth Email Address exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7140 |
The OAuth Email Domain exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7141 |
The OAuth Scope exceeds the maximum length of <MAX>,
got <SIZE>.
|
| ERR_NGROK_7142 |
The edge module exceeds the maximum number of GitHub teams. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7143 |
The edge module exceeds the maximum number of GitHub orgs. You specified
<COUNT>, the max is <MAX>.
|
| ERR_NGROK_7144 |
The OAuth GitHub team exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7145 |
The OAuth GitHub org exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7146 |
The edge module exceeds the maximum number of Google groups. You
specified <COUNT>, the max is
<MAX>.
|
| ERR_NGROK_7147 |
The OAuth Google group exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7148 |
The OIDC Client ID exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7149 |
The OIDC Client Secret exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7150 |
The edge module exceeds the maximum number of OIDC scopes. You specified
<COUNT>, the max is <MAX>.
|
| ERR_NGROK_7151 |
The OIDC Scope exceeds the maximum length of <MAX>,
got <SIZE>.
|
| ERR_NGROK_7152 |
The OIDC Authn URL exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7153 |
The OIDC cookie prefix exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7154 |
The Webhook Verification secret exceeds the maximum length of
<MAX>, got <SIZE>.
|
| ERR_NGROK_7155 | Enabling OAuth, OIDC, or SAML on more than one route is not supported. |
| ERR_NGROK_7156 |
Failed to attach hostport. The domain <HOSTPORT> is
allocated for region <NEW_REGION> but the previous
hostport is allocated in <OLD_REGION>.
|
| ERR_NGROK_7157 |
Failed to attach hostport. The address <HOSTPORT> is
allocated for region <NEW_REGION> but the previous
hostport is allocated in <OLD_REGION>
|
| ERR_NGROK_7158 |
Invalid edge module, OAuth auth check interval must be no greater than
<MAX>, was <ACTUAL>.
|
| ERR_NGROK_7159 |
Invalid edge module, OIDC auth check interval must be at least
<MIN>, was <ACTUAL>.
|
| ERR_NGROK_7160 |
Invalid edge module, OIDC auth check interval must be no greater than
<MAX>, was <ACTUAL>.
|
| ERR_NGROK_7161 |
Invalid edge module, OAuth max session duration must be no greater than
<MAX>, was <ACTUAL>.
|
| ERR_NGROK_7162 |
Invalid edge module, OIDC max session duration must be no greater than
<MAX>, was <ACTUAL>.
|
| 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_8000 |
Failed to resolve host <HOST>:
<ERR>
|
| ERR_NGROK_8001 |
Failed to establish internet connectivity: <ERR>
|
| ERR_NGROK_8002 |
Failed to establish TCP connection to <HOST> with
error: <ERR>
|
| ERR_NGROK_8003 |
Failed to establish TLS connection to <HOST> with
error: <ERR>. Possible Man-in-the Middle.
|
| ERR_NGROK_8004 |
Failed to establish tunnel protocol connection to
<HOST> with error: <ERR>
|
| ERR_NGROK_8005 |
Failed to resolve proxy IP with error: <ERR>
|
| ERR_NGROK_8006 |
Failed to connect to proxy <URL> with error:
<ERR>
|
| 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 |
<RESOLVER> was the only resolver to return
<IP> for the hostname <HOSTNAME>.
This, or the other resolvers, may be returning incorrect results.
|
| 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
<ADDR>.
|
| ERR_NGROK_9000 | Only Pro or Enterprise accounts can use basic auth. 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_9001 | Only Pro or Enterprise accounts can use compression. Your account is not authorized to use compression. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_9002 | Only Pro or Enterprise accounts can use circuit breaker. 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_9003 | Only Pro or Enterprise accounts can use request headers. 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 | Only Pro or Enterprise accounts can use response headers. 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 | Only Pro or Enterprise accounts can use OIDC. 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 | Only Pro or Enterprise accounts can us SAML. 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 | Only Pro or Enterprise accounts can use TLS Termination. 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_9008 | Your account is not authorized to run the agent as a service. Upgrade to a new Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_9009 | Your account is not authorized to run the agent with http/s proxy. 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 | Only Pro or Enterprise accounts can run the agent on a custom network interface. Your account is not authorized to run the agent on a custom network interface. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_9012 | Only Enterprise accounts can run the agent with custom CAs. Your account is not authorized to run the agent with custom CAs. Upgrade to an Enterprise 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 | Only Pro or Enterprise accounts can run the agent with proxy proto. Your account is not authorized to run the agent with proxy proto. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_9015 | Only Pro or Enterprise accounts can use OAuth. Your account is not authorized to use OAuth. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_9016 | Only Pro or Enterprise accounts can use webhook verification. Your account is not authorized to use webhook verification. Upgrade to a Pro or Enterprise plan at: https://dashboard.ngrok.com/billing/subscription |
| ERR_NGROK_9017 | Only Pro or Enterprise accounts can use ip restrictions. Your account is not authorized to use ip restrictions. Upgrade to a Pro or Enterprise 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 | Only Pro or Enterprise accounts can use the websocket to TCP converter. 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_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
"<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
"<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 "<PARTITION>" that does not
include the word "aws".
|
| ERR_NGROK_10022 |
Received service "<SERVICE>" but expected
"<TARGETSERVICENAME>".
|
| 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
"<FORMAT>" given. Upload a Certificate Authority in
PEM format.
|
| ERR_NGROK_10027 |
Failed to upload SAML IdP Metadata. Invalid file format
"<FORMAT>" given. Upload SAML IdP Metadata in XML
format.
|
| ERR_NGROK_10028 |
Failed to upload TLS Certificate. Invalid file format
"<FORMAT>" given. Upload a TLS Certificate in PEM
format.
|
| ERR_NGROK_10029 |
Failed to upload TLS Certificate Private Key. Invalid file format
"<FORMAT>" given. Upload a TLS Certificate Private
Key in PEM 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_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 |