-
Notifications
You must be signed in to change notification settings - Fork 52
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
After Creating Server, Serve Not Showed in WHMCS #111
Comments
I am now running in to the same issue, It appears the update to WHCMS 8.2 broke the API again. |
i am trying to fix the issue, please let me know if you found any solution |
check my fork and release |
Thanks so much @meramsey Tested and this is working again with Version: 8.2.0 of WHMCS again! |
@meramsey Not sure what happened. My test went through and the Virtual Machine ID loaded in WHMCS but just sold a New VPS today and the user created it and WHCS never got it and it allowed the user to try again. |
Yeah i think ive seen that happen once due to it letting clients click create multiple times if they do that vs being patient and waiting for it to complete. Was an issue before too afaik. Can report a bug on my fork if you would like not sure how much time ill have to look into it just yet. When this happens i usually delete the duplicates and just enter the first uuid/subid and save in the product to link it back. In reality i feel like this module could/should probably be rewritten from scratch at for some sections as there are some really weird issues at times that shouldn't really be possible. |
Yeah I have to manually go in and update the VM ID when this happens but that was really the only issue I was having. We just updated to WHMCS 8.2.1. I'll try a couple tests runs and see if it continues to do it again. |
still not fixed I update a lot of things but still not reliable even after creating server-client don't see manage server |
Same, I had a new order come in and it worked but one other one didn't seems random. |
Advise looking into this maintained product which is what I switched too. 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. |
https://prnt.sc/17c09zh https://prnt.sc/17c0gfx
The text was updated successfully, but these errors were encountered: