Search results

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.

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.

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

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

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

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

We can mark this as resolved for now.

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

In "tiredofit/freescout" settings, try 127.0.0.1 for DB_HOST

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)

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.

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.

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

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

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

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

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.

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

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.

Ok. This might be related to your issue. Please check. https://support.plesk.com/hc/en-us/articles/12377509447447-A-website-hosted-in-Plesk-shows-wrong-website-content-when-opened-over-HTTPS-after-migration-from-a-legacy-Plesk-version...