You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to deploy algo with Vultr. It seems that Vultr has stopped allowing new accounts to use their v1 APIs and will deprecate them for old accounts on June 30th, 2023
I got the following error when trying to deploy.
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Reached API retries limit 5 for URL https://api.vultr.com/v1/firewall/group_list, method GET with data None. Returned 503, with body: HTTP Error 503: API v1 Gone b'Sorry, all newly created accounts are forbidden from using API v1, all other accounts are able to use this deprecated API until June 30, 2023 at which point Vultr API v1 will be sunset. Please use API v2.'", "vultr_api": {"api_account": "default", "api_endpoint": "https://api.vultr.com", "api_retries": 5, "api_retry_max_delay": 12, "api_timeout": 60}, "vultr_firewall_group": {}}
Is there a plan to help update this? Thanks
The text was updated successfully, but these errors were encountered:
I'm trying to deploy algo with Vultr. It seems that Vultr has stopped allowing new accounts to use their v1 APIs and will deprecate them for old accounts on June 30th, 2023
I got the following error when trying to deploy.
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Reached API retries limit 5 for URL https://api.vultr.com/v1/firewall/group_list, method GET with data None. Returned 503, with body: HTTP Error 503: API v1 Gone b'Sorry, all newly created accounts are forbidden from using API v1, all other accounts are able to use this deprecated API until June 30, 2023 at which point Vultr API v1 will be sunset. Please use API v2.'", "vultr_api": {"api_account": "default", "api_endpoint": "https://api.vultr.com", "api_retries": 5, "api_retry_max_delay": 12, "api_timeout": 60}, "vultr_firewall_group": {}}
Is there a plan to help update this? Thanks
The text was updated successfully, but these errors were encountered: