• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. P

    Resolved No Firewall changes possible with 18.0.52

    My server still has the issue. I suspect that the problem may be related with fail2ban which also modifies the iptables. My last 2 attempts to reload the firewall rules with the 18.0.52 version resulted in the inaccessibility of my server and I needed to restore my vserver from the latest backup...
  2. P

    Resolved No Firewall changes possible with 18.0.52

    After my server was restored, I added the following timeouts to /opt/psa/admin/conf/panel.ini [ext-firewall] confirmTimeout = 45 confirmTimeoutCli = 60 Alas, I still get the timeout error after 5s I did also check the processor load during run of the firewall script and I don't see any...
  3. P

    Resolved No Firewall changes possible with 18.0.52

    Update: I did copy the script which was shown in the web gui into /tmp/firewall.sh and ran it from the ssh console. Result was that my server became inaccessible from ssh and from the plesk gui and I am now in the process of restoring it from the latest backup on yesterday 22:00
  4. P

    Resolved No Firewall changes possible with 18.0.52

    What I did from the given support thread was plesk installer remove --components psa-firewall plesk installer add --components psa-firewall and after your post, I also went to the extension catalog and installed the firewall extension from there. This brought back the GUI, but the initial error...
  5. P

    Resolved No Firewall changes possible with 18.0.52

    Strange ! As I wrote I have removed and installed the firewall extension so I guess I have the latest extension in place but now I do not even get the firewall GUI page anymore.
  6. P

    Resolved No Firewall changes possible with 18.0.52

    Things have become even worse after I did find https://support.plesk.com/hc/en-us/articles/12387716023063-Unable-to-activate-Plesk-Firewall-Error-The-firewall-rules-management-has-not-been-enabled I did remove and re-install the firewall component and now the firewall admin page is not even...
  7. P

    Resolved No Firewall changes possible with 18.0.52

    I am faced with the same problem. This thread says resolved but: What is the solution? I am running SSH on a different port for security reasons, and I haven't changed the firewall config for more than a month. With the latest update, the GUI has changed to become worse and I cannot do any...
  8. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    Thank you for the hint and for your time
  9. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    Yes, it is enabled and it contains logs from the past weeks.
  10. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    I did clear the cache and I even did open the stat page with another browser (chrome instead of my usual firefox) but the problem persisted. The statistics are all at '0' for the current month as well as for the previous months. I guess that this is in-line with the "Never updated.." I also...
  11. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    I found old threads which deal about the same problem but also without a solution. https://talk.plesk.com/threads/awstats-does-not-generate-statistics-for-all-domains.79223/ https://talk.plesk.com/threads/awstats-not-updating-for-one-domain.295103/
  12. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    I re-ran plesk daily -f ExecuteWebStatistics and the timestamps on the html files in the "current" directory all got updated. Nonetheless, on the linked "index.html" page it still says "Never Updated.."
  13. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    yes, the link is there for both of the domains.
  14. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    Yes, it is enabled for both domains. All the checkboxes on both domains are set the same and have the AWStats set.
  15. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    I have 2 domains and your answer helped me to get the web statistics for one of it working. The other domain still shows the "Never updated .." message.
  16. P

    Issue Never updated (See 'Build/Update' on awstats_setup.html page)

    My server has awstats installed from the plesk module installer but when I check the usage statistics it is completely empty. At the top it says: Last Update: Never updated (See 'Build/Update' on awstats_setup.html page) But where is the awstats_setup.html page?? A search on "awstats" or...
  17. P

    Issue apache mpm_event alert AH03104 unable to create worker thread

    I think I eventually found the solution on HTTPS unter Apache/Ubuntu systemctl show apache2.service | grep TasksMax gave me a result of 60, and I did increase it to 120 with the given command: systemctl set-property apache2.service TasksMax=120 So far the problem did not show up again. I am...
  18. P

    Issue apache mpm_event alert AH03104 unable to create worker thread

    I did check the items from your link between the old and my new server and I don't see any differences. Thus, I suppose the whole issue is related to plesk 18 on Ubuntu 22 as opposed to plesk on Ubuntu 20. It may also be though, that the new vServer platform has issues with the hosting server...
  19. P

    Issue apache mpm_event alert AH03104 unable to create worker thread

    I haven't changed anything in the apache conf from the default values. And the settings on the old server are the same as the settings on the new server which I migrated to. I use logwatch on both servers and I do only see the alerts so frequently on the new server. I did already restart the...
  20. P

    Issue apache mpm_event alert AH03104 unable to create worker thread

    Add On: On my old Ubuntu 20 Server with Plesk Obsidian 18.0.51 I did only find the AH03104 error 11 times in the past year. The old server did only have 4GB of RAM instead of the 8GB on my new server. Also, the old server had 2 CPUs instead of 4 CPUs now. Resources are much better now than...
Back
Top