• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Recent content by Bitpalast

  1. Bitpalast

    Issue httpd service failed to start after plesk 18.0.75 upgradre

    status=226/NAMESPACE is a systemd failure at the “namespace setup” step, i.e. systemd tried to apply one of its sandboxing/isolation features (mount/user/tmp/dev namespaces, etc.) for httpd.service and the kernel/container runtime didn’t allow it. In LXC containers (especially unprivileged ones...
  2. Bitpalast

    Resolved SMTP connection timeout

    So mail.mydomain1.com was hosted elsewhere, not on the same server where the website is? That of course explains why so many iterations where needed to solve the case. I was certainly assuming that mail.mydomain1.com is hosted on the same server where the website is hosted.
  3. Bitpalast

    Resolved SMTP connection timeout

    How does an MX record come into play in this scenario, specificially when you use "localhost" to address the SMTP server?
  4. Bitpalast

    Resolved SMTP connection timeout

    Is the SMTP server actually listening? Is the service active?
  5. Bitpalast

    Resolved SMTP connection timeout

    It's either the host name or a ban on localhost IP connecting to the SMTP server. First try "localhost" instead of the public domain name.
  6. Bitpalast

    Resolved SMTP connection timeout

    You can try "localhost" instead of the real hostname.
  7. Bitpalast

    Resolved SMTP connection timeout

    Port 587 requires STARTSSL/STARTTLS, won't work on SSL/TLS. Options: change port to 465 or 25 (without SSL/TLS, you don't need that anyway if the connection stays on your own server).
  8. Bitpalast

    Issue I cant send email to hotmail

    Yes it is. If you have tried the delisting service Sign in to your account be aware, that the first email you get from them always states, that there is no error non MS side. However, you need to respond to that email and bring your case forward again, e.g. send them their return mail, then a...
  9. Bitpalast

    Resolved Auto-scrolling to bottom of paginated pages

    Username: TITLE Auto-scrolling to bottom of paginated pages PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE 18.0.74 #2 PROBLEM DESCRIPTION Since the latest Plesk updates, paginated pages auto-scroll to the bottom when opened. This makes the pagination settings >10 useless...
  10. Bitpalast

    Issue Permission issues after file restoration

    I suggest to rather find /var/www/vhosts/domain.tld/httpdocs/ -type d -exec chmod 0750 {} \;
  11. Bitpalast

    Issue AWStats high CPU in localhost.localdomain

    Shortening log rotation intervals on that one big client installation is a good idea. Removing AWStats might be too much. It's an issue in that software, but sooner or later that will be solved. Instead, develop a short script that monitors the process list for long running AWStats processes and...
  12. Bitpalast

    502 bad gateway problem

    A reboot of that instance might solve it.
  13. Bitpalast

    Resolved Let's Encrypt certificate with SSL It -> using wrong certificates

    I think there is not true technical issue in Plesk with it. Rather check whether the domain is consistently routed to the desired IP or whether it might have several A- or AAAA-records that are pointing to another server, too.
  14. Bitpalast

    Resolved Tips for resolving failure to dump SQL for Plesk Backup ("Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = ..." )

    Admin privileges are not required for "show function". I suggest to open phpMyAdmin and run a test: SHOW FUNCTION STATUS WHERE Db = 'dbase_name'; in the SQL dialog box. Maybe the system is right that mysql.proc has a problem? Was MariaDB updated lately? Was mysql_upgrade --force run afterwards...
  15. Bitpalast

    Backup and Restore failed

    What does "skip_name_resolve" have to do with the issue described by @seqoi? Why is your @HHawk case "this issue as well" when you post a totally different description that is in no way linked to the initial post? I suggest you post your issue with a detailed description in your own thread...
Back
Top