Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not initiate rate limits. Received fatal alert: handshake_failure #28

Open
craigbye opened this issue Mar 19, 2019 · 1 comment
Open

Comments

@craigbye
Copy link

Looks like the tool broke on March 14, 2019. Not sure if it's related to this annoucement:

New Request Domain Introduction for Rate Limiting
We would like to kindly inform you that a new request domain is introduced in our rate limiting structure for the API requests made to retrieve the current and next on-call user(s). These requests were considered in the Configuration domain before, but will now have their own request domain for rate limiting. You can see the list of available request domains from this page.

Please do not hesitate to contact us if you have any questions.

@gg5201818
Copy link

@craigbye
If you have seen this error after firing the command
17:59:42.764 [main] ERROR com.opsgenie.tools.backup.util.BackupUtils - Could not initiate rate limits. Unauthorized
It's possible that the --apiKey doesn't have the right permission (Suggest using the one from API Key Management), or the incorrect Host URL this request submitting to.

If your Opsgenie is hosted on the EU site, please incorporate the --opsgenieHost argument with the value "https://api.eu.opsgenie.com" into your command, like below.
java -jar OpsGenieExportUtil-0.23.4.jar --apiKey xxxxxx --opsgenieHost https://api.eu.opsgenie.com

By default, the --opsgenieHost URL is pointing to the US API Gateway, https://api.opsgenie.com, so no need to specify it if your Opsgenie is hosted on the US site.

Please try again and verify the result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants