Search results

The log entry indicates the email client doesn't use any TLS version used by the server or the server doesn't use any of the TLS versions used by Outlook. Are you using a recent Outlook version? You can try to replace Courier with Dovecot from Plesk installer.

Hi, The functions.php file contains the malicious code. You can restore the file from an available backup, replace it with the functions.php from the theme package or try to remove the malicious code manually. Removing the file will break the WordPress theme.

Hi, You should also set the email address and password in the SMTP settings. Change the none dropdown. For the maillog, there is the logbrowser extension (Log Browser extension - Plesk) or via SSH, logged in as root, in /var/log/maillog.

Hi, What do you have in the maillog when the error is encountered? Monitor it while you click the button in Outlook. Can you also show us what options you have when you toggle the show advanced settings button?

Hi, Do you have a backup from where you can extract those 3 files? If you do, compare the files to see if you have injected code. Did you also run a manual scan?

Hi, You will have to open a support ticket with them at Sign in to your account. If you have access in SNDS, you should also check if your IP address is not blocked. This is not a Plesk issue. It's one of Microsoft's measures to block SPAM.

You need to implement in nginx conf.d Module ngx_http_realip_module Add a set_real_ip_from directive for each Cloudflare subnets. IP Ranges (you have links to plain text lists in the article)

Hi, Cron task execution is logged in /var/log/cron. You will find there all the tasks that were executed. How do you back up your data? Is it scheduled within this timeframe?

Do you have, by any chance, the LiteSpeed extension?

That leaves you with a strace: dnf install strace strace -s1024 -o output.txt httpd -X -e Debug zip the output.txt file and send it in a private message. The file will contain references of all the hosted files, system users and IP addresses. Don't post it in the thread!

Understood. How about: systemctl reset-failed httpd systemctl start httpd

Try the following: httpd -X -e Debug Should tell you why it doesn't start

What do you consider a real firewall? Did you try Imunify360?

We also observed high traffic volumes from that huge subnet. The simplest approach is to block it since you don't expect traffic from a different hosting company. In your case, firewall blocking won't help since your firewall will see only Cloudflare IP addresses. You can block in nginx but it...

Interesting. Taking another look at my /etc/nginx/plesk.conf.d/server.conf, it's exactly the same as yours. If you reconfigure, do you still get the error message? plesk sbin httpdmng --reconfigure-all

Do you use a custom template? What do you have in: ls /usr/local/psa/admin/conf/templates/

What is the output of the following? plesk bin server_pref -s | grep ssl

I ran into a similar issue. In my case, it pointed out that I didn't have TLS1.3 enabled: plesk bin server_pref -s | grep ssl Since ssl-protocols didn't have TLSv1.3, I used: plesk bin server_pref -u -ssl-protocols 'TLSv1.2 TLSv1.3' Afterwards, I reconfigured the webserver and I had HTTP/3...

If you have 2 servers, just perform a migration with Plesk Migration Manager. The restore approach should also work.

Remove the AAAA records.