Search results

3) maybe have a script run on first boot that curls the plesk api to issue the license and then apply it. You'll want to have the script remove itself after it's ran.

I wouldn't say "crazy" - Active support has been dead for years. Think you need to be more into pushing customers to upgrade to PHP 7; push it as a performance enhancement instead of supporting a possible security issue. What's the reason for needing PHP 5 still?

Where are you seeing this little warning? Can you share the domain?

Looks like a bug; Unable to create a domain backup using REST API in Plesk for Windows

Your reseller can always open a support request on your behalf......

Sounds to me like two completely separate issues. Just my two cents.

Uh. What?

You likely have directory index off. Creating an .htaccess file with the following in the folder; Options +Indexes

Home > Tools&Settings > Apache Web Server What MPM mode?

I went thru this fun on AWS once. You need to map private -> public IPs. Running Plesk Behind a Router with NAT

^^ yup, cgroup not mounted. If you want to get a bit hack-ish you could try messing with the following but I would first try it in a dev environment; tianon/cgroupfs-mount

>> Using the local Plesk's FTP server as a remote storage is prohibited. Please specify a remote location. I see you mention it's hosted remotely, but do you possibly have a local DNS zone?

Seems like there should be some automation to keep the auth token fresh....

Do you actually have a reason that you need to be HIPAA compliant? It's not really just some magic tweak these settings kind of a thing. For example, Not even Gmail is HIPAA compliant out of the box.

Seems to be here in the SessionContexts table; Dropbox - Screenshot 2019-03-23 19.42.22.png Wonder what happens if you drop that entry? ¯\_(ツ)_/¯

Try hitting the path directly? :8443/modules/digitaloceandns/index.php/index/update-auth-parameters

You're not going to get true HIPAA compliance on a Plesk server unless you're ready to get dirty. HIPAA compliance requires encrypting the content of email messages which out of the box Plesk does not support.

^ yup, what Peter said. Plesk's API would help with this.

^ what Igor said. AWS EC2 doesn't have root user enabled by default, but you can enable it. To do so; - Connect to user via ssh - Gain root with sudo command - Set root password with passwd command OR apply public key to authorized_keys - Modify /etc/ssh/sshd_config and set PermitRootLogin...

Do you really mean to use port 3307?