• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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. WebHostingAce

    Resolved SUPER WEIRD port issue

    Please check if you have SERVER.B.DOMAIN in Tool & Settings > Server Settings. How about if you ping SERVER.B.DOMAIN from the SERVER.B.DOMAIN server itself. Do you receive a response? To me this sounds like SERVER.B.DOMAIN not resolving to a IP within the server itself. Please check.
  2. WebHostingAce

    Resolved The timeout specified has expired: AH01075: Error dispatching request to : - without URL in my logs - Error 502 - since php 8.2.13 - randomly

    In addition to Peters reply, have you tried? # journalctl -xe and # journalctl -u httpd.service might help to find out the reason for Apache stopped.
  3. WebHostingAce

    Resolved SUPER WEIRD port issue

    Is this SERVER.B.DOMAIN behind any proxy? such as CloudFlare? Usually the CloudFlare keeps this port 8080 open while the rest such as 465 closed.
  4. WebHostingAce

    Issue DNS Server

    dig @8.8.8.8 yourdomain.tld It works. Doesn't seems to be blocked.
  5. WebHostingAce

    Issue Deleted FTP users still showing on /etc/passwd

    Do you have this ftpuser2 in the psa database? SELECT * FROM `sys_users`; Tools and Setting > Database Servers > Select the Plesk Database Server > Webadmin (the small icon) > psa database > sys_users table
  6. WebHostingAce

    Issue Deleted FTP users still showing on /etc/passwd

    I tried to recreate this issue but couldn't. CentOS Linux 7.9.2009 (Core) Version 18.0.56 Update #4
  7. WebHostingAce

    Resolved Completing migration from one server to another server

    Once the Migration Tool complete the task, There is no connection between the new server and old server. On the new server, You can click on the "Finish Migration" (It would be a good idea to take a full server backup and save it locally from the old server before deletion.)
  8. WebHostingAce

    Resolved Apache fails to (re)start with Atomic ModSecurity

    We can mark this as resolved for now.
  9. WebHostingAce

    Resolved Completing migration from one server to another server

    Please note complete DNS propagation can take up to 48 hours. Also your PC/Browser might using your local DNS cache.
  10. WebHostingAce

    Question Install Freescout with Docker

    In "tiredofit/freescout" settings, try 127.0.0.1 for DB_HOST
  11. WebHostingAce

    Resolved Apache fails to (re)start with Atomic ModSecurity

    Thank you @Peter Debik. Currently this sever is running Plesk 18.0.57 #2. This issue only happened twice on one server out of all my server running Atomic Mod Security. Only similar post I found is Resolved - ModSecurity (once again)
  12. WebHostingAce

    Resolved Problem sending emails to myself

    If you are receiving all other external email but not the emails to yourself, it is a very unusual situation. Please see the Mail Log in Tools & Settings > Log Browser. Also please note, The AWS EC2s comes with port 25 outgoing blocked.
  13. WebHostingAce

    Resolved Apache fails to (re)start with Atomic ModSecurity

    Thank you @trialotto I checked this. The issue was showing as, Upon checking the Rule ID in I did a grep to the whole / to see if this Rule ID was mentioned anywhere else in the server. But did not find any duplicate.
  14. WebHostingAce

    Resolved logparser Process

    When investigating, there was a 16GB Apache log in one of the domain. The log rotation was disabled on this domain.
  15. WebHostingAce

    Resolved logparser Process

    I understand this process is related to "Website Log Check". But what could be causing this process to run this long?
  16. WebHostingAce

    Resolved logparser Process

    Hi, I have this long running process which use 100% CPU thread.23780 root 30 10 243156 28092 5276 R 100.0 0.2 270:28.63 /usr/bin/python3 -Estt /usr/local/psa/admin/sbin/logparser --timeout 86400 --variables INTERVAL=1800 TS_FROM=2023-11-28T03:30:17+10:00...
  17. WebHostingAce

    Farewell post

    Hi @IgorG, It is with a mix of gratitude and sadness that we bid you farewell from the Plesk Forum. Your presence has been a shining beacon of support, and your contributions have made a lasting impact on the entire community. Your name has become synonymous with quick solutions and invaluable...
  18. WebHostingAce

    Issue Domain is not resolvable

    This is the expected behavior when you are using CloudFlare for DNS because the IP address in Plesk does not match the CloudFlare DNS IP address. (CloudFlare hides the real IP of the website(Proxy)) Please see Issue - website DNS not resolving, but website working to turn off these warnings.
  19. WebHostingAce

    Resolved DKIM is valid but signature fails

    Please re-copy paste the default._domainkey from the Plesk DNS.
  20. WebHostingAce

    Resolved DKIM is valid but signature fails

    If you are using external DNS provider, Please make sure to to have both _domainkey and the default._domainkey exactly as currently in Plesk DNS. As far as I can see from the image provided above, default._domainkey does not look correct.
Back
Top