Search results

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...

On Ubuntu, it's /var/log/mail.log @rammstein Do you see any items in the list, or is it empty when you go to "Tracking Email Delivery"?

Hi, Could you share the specific warning messages from the migration? That will tell us exactly which modules it's looking for. However, keep in mind that RHEL-based distros tend to enable many Apache modules by default that aren't strictly necessary. Debian takes a more minimal approach for...

Hi, PM2 on Plesk? I don't think that's going to work. But regarding your issue, can you post a screenshot of the Node.js settings? Did you assign app.js to "Application Startup File"?

No problem, I'm glad it works now!

Could be different things. - How did you create the ssh-key? With the same type as the other servers? - Did you check the file- and directory permissions of the .ssh directory and the files inside .ssh/*? Those are very strict.

That looks like a bug in the Log Browser. Can you please report it as a bug? https://talk.plesk.com/forums/reports.746/

Can you check the info.log and debug.log for errors in /usr/local/psa/var/modules/panel-migrator/sessions/<date>/*

I am sure that Plesk is already working on a fix. In the meantime, take a look at my instructions to insert custom CSS. Or use the command line to monitor the logs: tail -f /var/www/vhosts/system/domain.com/logs/proxy_access_ssl_log tail -f...

You should be able to use my instruction for custom CSS to add the overflow: visible style: https://talk.plesk.com/resources/updated-20230617-change-the-width-of-scheduled-tasks-fields-in-plesk.44/

That spike looks like the start of the Plesk Daily Maintenance script: https://support.plesk.com/hc/en-us/articles/12377063217431-What-is-the-Plesk-Daily-Maintenance-script https://support.plesk.com/hc/en-us/articles/12377592733207-How-to-check-the-Plesk-Daily-Maintenance-Task-execution-time...

It looks like the feature that was described in a previous release: https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18072

They are working on it, There was an issue with the publication of the changelog. It will be published soon.