Leaderboard

Perhaps the SolusVM module should be updated not to show the option to change the password for KVM virtualizations.

try this links http://host-image.net/v.php?id=79160proxmox_package.png http://host-image.net/v.php?id=31682proxmox_adminside.png

Also, if you move your install, make sure you re-issue the license key in the client area. Also, update the paths in the settings under Settings > System > General after the move.

Any such code would likely work similar to a passphrase that is not stored within Blesta anywhere, but can be confirmed by Blesta when entered. Personally, I don't like the idea. It weakens 2FA. But, it's good if you have a lot of customers opening tickets because they lost their 2FA tokens.

That's interesting. It's not something I would personally use because I frown upon backdoors, but some may find it useful.

Do you have a link to their documentation (hopefully available in English)?

You may be interested in CORE-1449. It allows for client permissions to add or edit. If add is granted, they can order it during checkout. If edit is granted, they can change it in the client area after its active.

Not sure if this helps but I had what I think is a similar problem and Tyson put me right I was using /home/user/public_html/services/ which was wrong

I see no problem of modifiying the core files (if needed), in fact, if the users of a certain software aren't going to modify the core files to make it fit with their needs (since there is no software that can fit all businesses) in my opinion there would be no point of having the source code open, yes you will have to replace the files every time you upgrade your blesta, but how often Blesta team releases an update? not often.

Support depends where you buy the license from. If you buy direct you get the best Blesta support you can ever want. If you buy from a reseller (Distributor / Reseller webhost [eg: Site5,etc]) you get support from them, and that depends per business you use. You get support here as-well as the others above. As for stable, Blesta is the most stable billing system out there on the market. If you look at the bug fixes for Blesta and then a competitor and you will see the difference. Blesta 1 - 5 in a beta, maybe a few got outside beta maximum, WHM** - ClientExec you get about 100 and / or more per release. And most of them are for simple things they just didn't bother with. As for Security, Blesta again is the most secure billing system out there, and don't just take my word for it read these: - http://www.webhostingtalk.com/showpost.php?p=8898652&postcount=14 - http://www.webhostingtalk.com/showpost.php?p=8885045&postcount=183 Two well known security auditors.

We are partnered with e-onlinedata, see http://e-onlinedata.com/blesta/ They have good rates, and can set you up with Authorize.net included, which works well with Blesta. If you are not in the US, then they may not work for you yet.. but I hear they have plans to expand into Europe.

That's why. I have the same issue, but I've liked it to that, not a Blesta thing.

Standard order form shows step by step arrows.

Surely someone else needs/wants this

I have yet to have a problem with namecheap however enom is a great way to go as well. Personally I suggest picking the one that you like best. I also like the idea of a full audit log for admin actions. Even client actions for that matter.

You need to enable legacy password support in config/blesta.php http://docs.blesta.com/display/user/Configuration Blesta 2 uses MD5 passwords for user accounts. Blesta 3.0 uses bcrypted HMAC SHA 256 passwords. Enabling legacy support allows clients with imported MD5 passwords to login.. and once they do, they are converted to the new password format. We suggest enabling legacy password support, and then disabling it after a reasonable amount of time.