Recent content by themew

Your PTR record is set to omeunegocio.pt which is causing this (based on the IP address in your 3rd graphic). Set your reverse to the domain of your email server and read the next DMARC email you receive if you're still ending up in spam for guidance.

@Peter Debik is right suggesting that we wait, but for those of us building new servers now, we can't wait until next summer. As a CentOS user for 20+ years and a Plesk user for 8+ years, it saddens and frustrates me that we're now currently looking at other OS's and (shudder) panels. Waiting...

Interesting that the double log entry issue does not occur in Ubuntu 20.04, but we see it in CentOS 8.

After seeing @danami 's attempt with the Plesk errors noted above, I upgraded a server running CentOS 8.3 and the Webmin opensource panel to CentOS 8 stream. No errors, effortless upgrade, panel works and a Magento 2.4.1 store with Elasticsearch, Percona, Redis, Varnish and PHP 7.4 also fired...

We recently tested a server using Plesk with Ubuntu 20.04 and didn't see the duplicate entry issue in the log. Wondering if this is error is OS specific...

@learning_curve Thanks for your reply. Are you using CentOS or Ubuntu on your servers where you're not seeing the double log entries?

Issue 1: Site using NGINX only and SOURCE reports in the log on the current date as nginx SSL/TLS access, but when the date changes to tomorrow, the source changes the log entry to Apache SSL/TLS access on the exact same log entry. Scrolling up through the log displays all entries as Apache...

Seeing double log entries as well in CentOS 8.2 in all logs.

Post your DMARC report when you receive it from Google and we'll know more... Plus your PTR is still incorrect. 195.201.131.63 reverses to s1.futurenode.dk and doesn't reverse to your mail.futurenode.dk (either does your other domain). Your server hostname needs to be fixed and/or your...

mail.geekblog.dk and mail.futurenode.dk doesn't have any DMARC policy enabled according to mxtoolkit. Start with quarantine and watch your DMARC email that you get daily for results. When you see 100% in the DMARC email reports you should be fine.

Currently running Plesk current Obsidian version with CentOS 8, Composer, ElasticSearch, PHP 7.4, Redis and Magento 2.4.1 on a VPS with absolutely no issues at all. Updates from CentOS, Plesk and the various repositories come in and work. TLS 1.3 and NGINX work out of the box with Plesk.

I am trying to use an ed25519 ssh key on my CentOS 8 server. No problems uploading the key and using the key with the server, works great, but I when I try to change PasswordAuthentication, ChallengeResponseAuthentication and UsePAM to no I get the error: ExecStart=/usr/sbin/sshd -D $OPTIONS...

I've upgraded about a dozen CentOS 8 servers to MariaDB 10.4 for Magento 2.4 using the instructions in the Plesk link you referenced and have never had an issue. The 'Upgrade MYSQL databases' command should be MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin and you'll have no errors...

Regardless of what Microsoft tells you, as the proof is in the DMARC email you'll receive from the email servers. If you believe you've got things working, send an email to a gmail, yahoo and hotmail and/or comcast account as these servers all send DMARC reports. Each server will return a DMARC...

We have this issue with Microsoft whenever we move servers. Our IPs are clean but Microsoft requires you to set up an SNDS postmaster account. If you've already done this with Microsoft, you've got delivery issues with your server. If not, this has always solved our issues with delivery...