Search results

That's just a Notice. Error would start with E:, as above. Do you have immunify360 installed?

Since I changed the IP to 85.10.234.30, I didn't get any further errors.

The server is at hetzner's datacenter in Falkenstein, Germany. The working drweb server 85.10.234.30 is in hetzner's datacenter in Nuremberg. I don't think increasing the log level will be of much help since 103 is a connection issue where the connection already fails at the TCP level - some of...

Unfortunately it didn't for me - but now I got return code 103 which, according to /opt/drweb/update.pl, is EXIT_STATUS_CONNECT_ERROR => 103, Worse is that I keep getting this error even now running /etc/cron.daily/drweb-update manually. Update: I checked all the round-robin IPs of...

You're looking in the wrong place. cron has two ways to start things: The per-user crontab and the system-wide /etc/crontab, which in turn runs the scripts in /etc/cron.hourly, daily, weekly and monthly. At the start of the line for cron.daily, I changed 25 6 to 40 5 for 5:40. Please do not use...

Try tcpdump port 443 and net 173.0 while PayPal is supposed to connect. If that doesn't output anything, you know that the packets don't even reach your server, and you should ask Strato.

Randomizing the update time should sort it out too. Mass changing to another server will only perform what essentially looks like a DDoS on that other server. If Plesk wants to keep using a fixed update time, Plesk should take care of proxy-caching the files on their own servers.

Why? A certificate is simply invalid outside its specified validity interval. If you renew a certificate, the old one isn't explicitly revoked, it simply runs out. This might be true if you only see the certificate as a way to, together with PFS, encrypt communication so that not just anyone...

That's not what I heard. What I understand how it went like (see also OCSP stapling - Wikipedia): Early SSL-supporting browsers only checked the certificate chain. Checking the certificate status requires extra data. If the browser connects somewhere to check the validity, in this case the CA's...

Isn't OCSP Stapling explicitly designed to prevent the CA gathering user information, which it would get if each browser would have to connect some revocation database on their own instead of the webserver doing it for them and deliver the recent revocation status stapled to the certificate, so...

But you don't have the package php7.4-cli installed? That's the one plesk wants to run in that script because it thinks it is there as there obviously is an /etc/php/7.4 in your system, otherwise it wouldn't try to run that part.

Do you use the full part to the php binary you need now, or what was your CLI solution? In /usr/lib/plesk-9.0/maxlifetime I see: if [ -d "/etc/php/7.4" ] ; then for d in `find "/etc/php/7.4" -mindepth 1 -maxdepth 1 -type d`; do update_max_lifetime "/usr/bin/php"...

Are you sure you didn't run autoremove? This looks like plesk-php* packages were removed. AFAIK plesk's scripts run /opt/plesk/php/7.4/bin/php directly without going through /etc/alternatives/php, so just php8.4 taking over the alternatives shouldn't affect plesk, but it DOES affect cli.

@ is not in there.

Now I want to know how you got Microsoft Defender to run on Linux.

If it's mostly stuck in unpacking, check the temperatures with lm-sensors. Might be a bad CPU fan.

Is that a real server or just a vhost?

Then the 500 actually comes from Apache. Check the Apache error log. (/var/www/vhosts/system/yourdomain/logs/error_log)

... by violating quite a bunch of standards. This can only work if the google mail server is the first to receive the mails, and then relays all it doesn't know to your internal server. It will definitely break such things as fallback MX.

What are your hosting settings? Do you use nginx only or as reverse proxy?