Recent content by jopple

Updating the Mobile Center extension from Extensions > Mobile Center and restarting sw-cp-server fixed it for me. Also, make sure events are firing under Event Manager; if nothing’s there, push notifications won’t work either. The protocol version warning usually points to a sync issue between...

Thanks for the info, Sebahat. I’m seeing the same issue on one of my subscriptions, too. wp-config.php is suddenly blank, and no other obvious signs of compromise. I’ll try the workaround with wp-config-sample.php for now and see if it helps get things running again. Curious if anyone figured...

FTPS has its limitations, especially with the passive port range issue. It appears that Plesk isn't handling the data connection properly in your setup, which could be due to a firewall or NAT issue.

Even if you stop the sw-engine with the service sw-engine stop, there might still be active processes hanging around, especially if something is calling it via cron jobs or other background tasks tied to Plesk.

Since webmail uses the server IP, the usual IP-based limits won’t work. To apply similar controls, you’ll need to set per-user sending limits directly in MailEnable under SMTP throttling. That should help keep things consistent.

Hi Sebahat, thanks for sharing the update about the renewed "What's New in Plesk Obsidian" page. I took a look, and it seems well-organized and clear in outlining the main features. It’s helpful to have everything summarized in one place. Looking forward to seeing how the page evolves based on...

The error is due to either database user permissions or a limit on the number of databases your hosting plan allows. Check if your Plesk user has permission to create databases and whether you’ve hit any limits.

Plesk connects to the local database via a socket, so enabling SSL there isn't necessary and can cause issues like you're seeing. If your goal is just to secure the external MariaDB connection, you don't need to enable SSL globally in panel.ini.

Hey Fred, If your server is still using Plesk Onyx 17.8.11, try accessing it via https://your-server-ip:8443 instead of the old domain link. Sometimes older Plesk versions show browser security warnings; just proceed with caution. If you’ve forgotten your login, you may need to reset it through...