Troubleshooting

Here we try provide solutions to most common integration roadblocks. In case you are still experiencing issues, please contact us at [email protected].

• Routes configuration unspecified

  • Before you run any code snippet please configure your routes. Without proper routes your code wouldn't work.

  • Use Routes menu on the Dashboard.

• No upstream provided for reverse proxy or source IP %s is not on the allowlist

  • Our inbound/reverse proxy failed to find destination host due to absence of an inbound route. Please either create an inbound route in the existing route configuration.

  • If the inbound route already exists, please check if the source IP is on the allowlist.

• Requests to host from source IP are forbidden according to your routes configuration

  • By default, our outbound/forward proxy does not allow any (outbound) traffic between your server, the VGS vault (where sensitive data is stored), and your third party integrations. In order to enable an allowlist for a particular API endpoint, please create an outbound route for it.

  • If the outbound route already exists for this host, please check if the source IP is on the allowlist.

• Missing or invalid authentication data for outbound proxy

  • Requests to outbound/forward proxy contain invalid or missing authentication data.

  • Please check if you are providing correct access credentials and are authenticating your requests correctly.

• Invalid VAULT_ID provided

  • Requests are being send to an incorrext proxy URL.

  • Please make sure that you are using correct VAULT_ID and proxy URL looks like this: {VAULT_ID}.{ENVIRONMENT}.verygoodproxy.com.

• Prohibited upstream URI

  • Route's upstream host resolves to an invalid or reserved address.

  • Please change the upstream host of your route to a valid one.

• Invalid payload

  • Proxy can’t process the request's payload.

  • Please check if your route's filter is performing correct operations and verify the integrity of your payload data.

• Proxy message processing timeout reached

  • Please chech if the upstream host (your destination third party) is working correctly.

  • If the upstream host is working correctly or contact our support team via [email protected].

• Internal proxy error

  • It looks like proxy encountered an unexpected error. First of all, please chech if the upstream host (your destination third party) is working correctly.

  • If upstream host is working correcly, please go to your Dashboard and into the Logs section. Paste the request ID from the error message into the search bar and inspect the request for potential clues as to why this is happening.

  • If you are still unable to deduct the reason from this error, please send the details with request ID to our customer support team via [email protected].