Recent content by Maarten

I would suggest contacting Plesk support for assistance with your issue. See information on how to get Plesk support here: https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk The subscription has a free trial period for 1 month, so that would be...

You need to use custom server-wide web server configuration files, as described in this guide: https://support.plesk.com/hc/en-us/articles/12377559696151-How-to-create-custom-Apache-and-nginx-configuration-files-for-all-domains-in-Plesk In short, the steps are: Create a custom Apache or Nginx...

Have you seen this thread? It sounds like the issue you're having: https://talk.plesk.com/threads/network-drops-every-12-hours-ionos.361876/post-938717

The DUMP_D path in /etc/psa/psa.conf has to point to the new location, and sw-cp-server needs to be restarted afterwards. I wrote a small script to handle this, because the Plesk Migrator can’t work with the new location due to the “wrong” ownership of the mounted storage. So, before migrating...

Hi @Sebahat.hadzhi, Based on this discussion, I’ve submitted a feature request to Plesk for a Time Machine–like disaster recovery feature (restore a full server to new hardware from an existing backup).

There is no single “best” Linux OS for Plesk. The best choice is still the one you are comfortable with and that is supported by Plesk, but be aware that each distribution has its own limitations. Plesk publishes distro-specific restrictions (PHP versions, MariaDB/MySQL support, extensions...

Hi, Your general approach makes sense, especially the idea of having subscription-level backups off-site so you can bring critical clients back online quickly while a full BMR is still running. A couple of practical tips from experience: Hetzner Storage Box Storage Boxes work well with...

The issue is fixed in Plesk Obsidian 18.0.74 Update 3: https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18074-mu3 Could you please install this and let us know if this solves your issue?

Interesting. How did you find these articles?

I’m curious, any particular reason you chose Courier over Dovecot?

I’ve shared a suggestion regarding this issue in the Plesk Suggestions and Feedback forum for Plesk to improve security notifications: https://talk.plesk.com/threads/provide-detailed-security-information-and-a-dedicated-security-mailing-list.392004/

You can safely ignore most of the warnings. The modules listed (like log_config, logio, lua, mime_magic, proxy_ajp, proxy_connect, proxy_express, proxy_fdpass, unixd, version, watchdog) aren’t important for normal Plesk hosting. They appear because they were enabled on your old RHEL server...

When Plesk sends a notification about a “critical security update”, the only information we receive is the short message shown on the changelog. There is no CVE, no affected component, and no severity score. Looking at the inf3 files in the autoinstall directory, it’s difficult to determine...

Problem When configuring a Node.js application in Plesk, users can set Document Root and Application Root to the same path. This creates a serious security vulnerability where server-side code (app.js, config files, database credentials, API keys) becomes directly accessible via HTTP. Example...

Normally, a Node.js app uses a public folder which you use as the document root. That prevents your code from being exposed in the browser. Currently, it looks like your Document Root is set to the same location as your Application Root (D:\PROJECT - LIVE\IMS\), which is why app.js and other...