Search results

Imunify360. Imunify360

Hi @siska8080 Add this block to your Additional nginx directives in Plesk: location /usage { return 404; }

Hi Carlos, I logged to the server and executed the following commands, if use the SSH terminal on Plesk you could do it too. Create a New Swap File (if needed): If you don't have an existing swap file, create one using fallocate: Bash sudo fallocate -l 4G /swapfile Use code with caution...

Hi Carlos, what Peter Debik says resonates with what I heard from Plesk Technical Support recommendations. I did have a similar experience, server running out of memory, and I added swap and it seems to help my situation.

@Carlos Nog have you tried Increase Virtual Memory size

Hi @helalsiftwell , I was able to clear the security assessment implementing this fix; https://support.plesk.com/hc/en-us/articles/12377482124439-How-to-configure-a-redirect-from-the-domain-name-IP-address-to-the-server-hostname-on-port-8443-in-Plesk-for-Linux- Hope it works for you.

I use the Scheduled Backup settings, automatically backing up to Dropbox daily up to 14 full backups stored. I like to check the option to receive an email if errors occur during the execution of the backup task. More information on Scheduling Backup Settings here Scheduling Backups

When I ran this MYSQL_PWD=cat /etc/psa/.psa.shadow mysqldump -u admin psa > psadate +%F_%H.%M.sql I got permission denied. Would this plesk db dump psa > /root/psa_dump.sql has the same effect? I back up the psa database with the instructions above and ran the update and have the same...

Hi Peter, Thank you so much for your help, I can confirm the domains resolves to the correct ip address. When I ran the command on the Plesk server 2 where http://websiteserver2.com:443 get the 400 Bad request error Plesk Server 1 where http://websiteserver1.com:443 goes to https://

I have the situation where http://websiteserver2.com:443 in plesk server 2 brings 400 Bad Request error. In another plesk server 1 http://websiteserver1.com:443 forwards the traffic to https://. I would like to replicate this behavior. How is it possible? Curl results are the same for both...

Do we need a new section for Plesk (Monitor) 360 to report issues, provide suggestions or recommendations? I recently encountered the situation where I need to provide a monthly reports to the client with daily information on website availability and responsiveness. I can get the performance...

Totally agree with you if just a workaround for the "Websites and Domains display purposes".

Wish you the best luck, you can vote for this feature here Enable chrooted sftp for more than one user per account

You can do it but is not supported (the customization). I had a Plesk server on Media Temple with multiple SFTP accounts however I didn't implement this.

A workaround could be to use the Move option, place a.example.com and b.example.com under the same subscription example.com

Plesk rule only 1 SFTP user per domain. https://support.plesk.com/hc/en-us/articles/12377932751255 In default configuration it is possible to have only one user that could access domain via SFTP.

I have a similar issue while using AWS Cloudfront on a WordPress site. I went to the Apache & nginx Settings for the domain. In Additional nginx directives: add_header Access-Control-Allow-Origin *;

I like it, it saves time when you don't have to click the WP Toolkit link under WordPress tab.

Since the release of Plesk Obsidian 18.0.46, the Plesk Panel is available and can be installed on Ubuntu 22 with ARM architecture. https://www.plesk.com/blog/product-technology/arm-architecture-keeps-trending-in-2022/

We have a client were we only host a subdomain for them, the root domain is hosted somewhere else and the DNS records are managed externally. The client wants to block access to port 8443, they do not want the page for <subdomain>/login_up.php showing up on security assessments. We already...