Recent content by J.Wick

I fixed it by creating a custom nginx.conf for the domain, and making the file immutable so Plesk can't overwrite it. Magento is working incredibly well now; page load times are wicked fast.

I'm in Magento 2.4 / Nginx hell too. You need to set it to the root to the /pub directory for Magento security. The problem with Nginx is the inability to modify the server root Location ~/ setting to allow Magento's router to rewrite URLs correctly. I'm currently looking for a method to...

To get back to the operational level, I had to modify the /etc/msmtprc I had to hard-set these values. (Which should be available in the Plesk Panel under settings!! ) from email allow_from_override on domain For my login script, I had to modify it to: For Plesk Notifications coming from...

Everything has been working great until the latest update. I've verified the email account settings using a desktop client and re-entered the details into Plesk. All Plesk emails should be coming from [email protected], but now they are being sent from [email protected], and when...

The Plesk Upgrade for MariaDB didn't function properly because of two tables with 0 Autodata integers. I had to use the manual method. After upgrading, PHPMyAdmin stopped working for all users due to a permission issue with the pma__tracking. After two hours of troubleshooting, I found a...

Thanks, but that defeats the purpose of using Cloudflare security to protect the server IP. Hope to see a future upgrade.

Server performance is acceptable. Doing some research, if Plesk were to use Server-Sent Events (SSE) instead of what it currently uses, it would solve this problem. Considering the hosts using Cloudflare, this might be something Plesk Devs want to implement.

When starting real-time log monitoring, it crashes after 100 seconds, which is Cloudflare's default, and throws a 524 Error. No matter your rule, it's unpreventable. Even when disabling caching with the orange cloud, going straight to the subdomain IP does not fix it, suggesting it's the origin...

It's great to hear of your liberation. I was about to do the same, but I received a Black Friday deal for a 40% discount if you purchased an annual license yesterday and went with it to buy some time for other, more critical projects.

If Plesk were sold to a company in Russia, the US would sanction and ban it from being used, just as they did to Kaspersky.

Agreed. We're most likely going to move to CloudPanel.

There are solid points on this thread regarding what happens to products and services owned by investment companies. Plesk Web Host Pro Edition Monthly (PLSK-PRO-M) 2014 $7.25 2015 $14.25 2017 $14.25 2018 $12.75 2020 $14.03 2023 $17.43 2024 $19.43 2025 $26.99 2026 $2,025.99 (est.) I'm...

This alert came out three days ago and there's no update for the following PHP vulnerability. TLP:CLEAR MS-ISAC CYBERSECURITY ADVISORY MS-ISAC ADVISORY NUMBER: 2024-067 DATE(S) ISSUED: 06/07/2024 SUBJECT: Multiple Vulnerabilities in PHP Could Allow for Remote Code Execution OVERVIEW...

Updated to Plesk 18.0.61 Update 3, which corrected the login MFA and Monitoring 8880 bug. However, MFA requests the code for every login, regardless of the "Remember Device" setting. I cleared cookies and cache and still had the same behavior.

I'm able to log in using the customized Plesk URL, which goes through port 443 and works with Cloudflare. If I were to open my server to use port 8443, I'd have to use a Let's Encrypt certificate and expose the server IP address to the world, breaking a part of our security. This change to use...