Paul

Version 4.7.2 is now available, please see the release announcement. Patching Blesta See Patching Blesta in the User Manual for instructions. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.7.2. For older releases see all Change Logs.

Drag and drop DIRECTLY above the text that says "Drag & Drop Groups Here" that has a white background. Not in the gray background below it.

YES! Your admin password is now using the new key, however ALL encryption in the database EXCEPT your admin password is now using the old key. You absolutely must restore your system key. After that you'll have to reset your admin password again, but you will be recovering all the other things that are encrypted. If you've sold any services that use encryption, created any clients or admins since you changed your system key those will be broken after you restore your system key. If you don't restore your system key, everything else prior to that will be lost that's encrypted. We will be unable to provide any support whatsoever. If much has changed since you changed your system key, then I would highly recommend restoring from backup prior to your changing the system key. This is a very big deal. Critical!

To force HTTPS (After you've fixed your install per my previous reply) uncomment the lines in the .htaccess file as indicated in the file for https.

If you did a fresh install and then overwrote your database, you will have broke your installation. Having to reset your password is a sign that you did this wrong. Please note the big red IMPORTANT box in the documentation Tyson linked at https://docs.blesta.com/display/user/Moving+Blesta There is a very important System key in the config file that MUST match the original database. If you did a new install and overwrote your database you will have permanently and irrecoverably broken all encryption in Blesta. The fact you had to change your admin password is proof of this. Put your original System key back ASAP, or you will have to restore from backup.

It should have been unfeatured, done. We'll likely have a new deal for 2019 soon.

You created a new package, and are now trying to modify existing services to change the module_row_id associated with them in the database? This isn't recommended, any custom service fields the module would normally create will not exist if the module is changing. If the service has been cancelled and the package module needs to change, I would mark the package as inactive and create a new package as Tyson mentioned. No reason I can see to change the package associated with a cancelled service. What are you trying to accomplish?

Your DA server did not respond. Make sure your firewall on your Blesta and DA server has the DA ports open, they are non-standard so they are closed by default on most firewalls. Make sure your settings are correct. Make sure you have CURL SSL. If all the above is fine, make sure your server can negotiate a high enough TLS protocol that your DA server will accept. See https://docs.blesta.com/pages/viewpage.action?pageId=10551368#Debugging/Tools-CheckPHPCURL,outboundTLSVersion for how to test.

Things will work without it, just falls back to slower encryption methods. It's not likely you will notice anything, the most obvious is key generation during initial installation. If you get through installation without a time out, you'll be fine.

It can't connect. If it's not the firewall, you could check CURL SSL, check your settings make sure the port is correct. Make sure there is a path to Plesk from the server you have Blesta on. (Can you ping it?) Does your CURL support modern TLS? If Plesk is only listening on TLS 1.2 and your server can't negotiate 1.2 then it won't be able to connect. There's an example script you can use to test what version of TLS you support, and confirm that CURL SSL is working. See https://docs.blesta.com/pages/viewpage.action?pageId=10551368#Debugging/Tools-CheckPHPCURL,outboundTLSVersion

It's defined in your module configuration, typically 8443 see https://docs.blesta.com/display/user/Plesk?preview=/2621908/6225988/plesk-server.png See also https://support.plesk.com/hc/en-us/articles/213932745-What-ports-need-to-be-opened-for-all-Plesk-Services-to-work-with-a-firewall for a full list of Plesk ports, 8443 is plesk-https, 8880 is plesk-http. Your server should be able to make egress connections on these ports. These are non-standard ports and would not be open by default on most firewalls.

Your Plesk server is not responding. Check your firewall, make sure the required ports are open on both ends.

The only change was to Lifetime licenses. It's likely we will have a black friday / cyber monday promotion but we don't have the details worked out yet.

Never heard of bitwarden, does it support TOTP? Looks like it's compatible with Google Authenticator, and YubiKey per https://help.bitwarden.com/article/setup-two-step-login/ but this may be just to get into bitwarden?

Thanks, CORE-3289