Open colb opened 7 years ago
Hi, Sorry for the slow response.
First, it might help in your debugging to know that I do not experience this issue on my test installation, and thus it is not a universal problem. That being said, I'd love to ask a couple questions.
Does his happen for all ordered services? When a service is created through the admin interface is it successful?
The error you received is kind of a generic catch all. There should be a more detailed log under admin/tools/logs/module/. Would you mind posting one of those logs here? If you would rather communicate privately, please contact me through pm on the Blesta Forums under the user name Jono.
Sorry for the delay too, but I found the solution. First of all you have to check the records if the problem comes from something that has been repeated (Domains, DNS, Databases, Crons) if there is something repeated in the records it will tell you, in my case the problem was that I had a domain equal to the one I was going to activate and that is why the module bounced me in the registry that already existed.
The records are your clue
Hi, The module seems to work (and I want to thank you for that. VestaCP modules are rare), but when an order is created, it stays in "pending" but the automation create the account in vestacp. If I try to manually activate the order, I got "An internal error occurred, or the server did not respond to the request."