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

ERROR can't manage VPS at website[BUG] #120

Open
M14092007 opened this issue Dec 24, 2021 · 3 comments
Open

ERROR can't manage VPS at website[BUG] #120

M14092007 opened this issue Dec 24, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@M14092007
Copy link

i am using WHMCS 8.3.2 and am getting the same error as some previous users. Don't know when there will be an update for this module? Or can anyone fix it?
php: 7.4
whmcs: 8.3.2
server os: ubuntu + cyberpanel
image

@M14092007 M14092007 added the bug Something isn't working label Dec 24, 2021
@limsoke
Copy link

limsoke commented Dec 27, 2021

in your screenshot not build VM, try build and gat managed
but, if you have build from vultr website u can added Virtual machine ID in your Client Product

@meramsey
Copy link

meramsey commented Jan 2, 2022

Advise looking into this maintained product which is what I switched too.
https://www.modulesgarden.com/products/whmcs/vultr-vps

This made it finally possible to transition the existing clients in place by adding a new customfield to all existing Vultr Products "instanceId|Instance ID" text admin only. I then went and populated all existing orders with their V2 API instance id which you can get from visiting the server in the my.vultr.com dashboard and noting the string from url or via the V1/V2 list servers/instances API "v2_id": field. I then was able to just switch the products Module from Vultr to Vultr VPS and all the existing server's connections remain working.

@Businezz99
Copy link

Advise looking into this maintained product which is what I switched too. https://www.modulesgarden.com/products/whmcs/vultr-vps

This made it finally possible to transition the existing clients in place by adding a new customfield to all existing Vultr Products "instanceId|Instance ID" text admin only. I then went and populated all existing orders with their V2 API instance id which you can get from visiting the server in the my.vultr.com dashboard and noting the string from url or via the V1/V2 list servers/instances API "v2_id": field. I then was able to just switch the products Module from Vultr to Vultr VPS and all the existing server's connections remain working.

They don't have applications available to install yet... It's kinda disappointing. I guess they can't use Vultr APIs for applications, only OS can be installed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants