crand

This amazing level of support is truly top notch.

Did you use the self cert that vestacp makes by default? I set my vestacp to use a lets encrypt cert manually after autoinstall. Just curious, that could cause that perhaps. I may try to wipe the VM and reinstall it with the auto self cert. (Only downside is its a mixed secured sign)

Also I've just tested another Vesta CP server and changed the details to the others. Still the same error. Leading me to believe the vesta integration might be broken :/

Yes 4.2.1 domain.com|v-add-user a:2:{s:6:"status";s:5:"false";s:8:"response";s:64:"Failed connect to domain.com:8083; Connection refused";} Does this answer anything other than the fact it can't connect? P.S. the domain is the correct CNAME for VestaCP pointed at the right ip, just removed it. Also I've pinged both IPs from each other and they can successfully ping. So I don't think it's a firewall issue. Also edit: could the fact I'm running cloudflare / nginx on both be affecting this? I've disabled cloudflare for both domains and it's still doing it.

Upon trying to use VestaCP module 1.10 on the latest Blesta release I get the error: "An internal error occurred, or the server did not respond to the request." I've also allowed all UDP/TCP on my Debian server's firewall running VestaCP. Also I've confirmed all module details are correct. Can anyone confirm this is up to date and works at all with Vesta? If so, do you have any idea what could be wrong?