Search results

I would love to do the same (not upgrading and not caring about updates) but some things are a must to upgrade. For example: - Eventual critical security patches in some software - Some scripts that work with essential services - for example the letsencrypt.sh script Think about the second...

After updating to this version the Exim stops working with the following errors in /var/log/messages: Nov 29 12:32:44 srv2 kernel: pid 23374 (exim), jid 0, uid 12: exited on signal 11 Nov 29 12:32:48 srv2 kernel: pid 23483 (exim), jid 0, uid 12: exited on signal 11 Nov 29 12:32:49 srv2 kernel...

I understand why they drop FreeBSD from the support list - they invest a lot in patching the software and keeping the code in the build script and it does not pay off. It was a design problem to start from. FreeBSD's major strength is the ports/packages collection - it's super stable and well...

When doing ./build versions I get: grep: The -P option is not supported It will not continue unless hitting CTRL+C on that point.

It enabled OSCP but it is still not in "Must Staple" mode?!? SSLLabs shows: OCSP Must Staple No Revocation information OCSP OCSP: http://r3.o.lencr.org DigiCert shows something strange: OCSP Staple:Good OCSP Origin:Good CRL Status:Not Enabled

I am not with nginx combo and I am not with CSF (I actually use ipfw on FreeBSD). Increasing the ServerLimit, etc. did NOT fix the issue. It just made it crash a bit later than "usual". I downgraded.

The problem is that DA counts the invalid login towards user "invalid" and not user "test". Therefore the message system sends the following messages: As you can see, user "invalid" becomes a "catch all" user for all failed SSH logins.

Same here on FreeBSD. Here is what happens in the logs: HTTPD was running but not generating workers as you said. I read around the forums and fount a solution to increase the ServerLimit and MaxRequestWorkers. I did yesterday and so far it did not fall down, but I am still monitoring.

In the third column DA parsed the log and said that the user is called "invalid".

The brute force monitor is showing the following: 1631... 116.110... invalid 1 sshd3 Sep 14 03:17:08 srv2 sshd[89172]: Failed keyboard-interactive/pam for invalid user test from 116.110... port 44658 ssh2 As you can see it incorrectly parses the username as "invalid" instead of "test".

Reinstall everything from custombuild.

It got even weirder!!! Going to https://srv2.<serverhostname>:2222 shows valid TLS certificate. It uses the wildcard certificate. Going to https://srv2.<serverhostname>/ (so default port 443) shows the TLS warning that the certificate is expired. I tried renewing it as shown in the help...

Thanks. It will be a tough fight as this is a big free webmail provider in Bulgaria...

No, my Exim is the receiving system... The sending system is... I don't know what. It's a popular free webmail - abv.bg

Well I do not use Postfix. DA is with Exim...

One user is complaining that e-mail sent to a domain on the server was bounced back with the following error: SMTPUTF8 is required, but was not offered by host What could be the issue?

Even weirder today everything is suddenly fine :) I guess it was some kind of cache or something...

The server hostname is srv2.<server domain>. I have wildcard sertificate added for <server domain>. I have not added srv2.<server domain> as separate hosting. Opening https://srv2.<server domain> shows expired certificate notice and I see old LetsEncrypt cert there. Opening https://<whatever...

Webmin+Virtualmin should be a good... and maybe only... option for FreeBSD from now on.

I am sad but I guess that's it...