CentOS

Well I have to say that it is resolved but I don't 100% understand what the problem was. That is to say I removed and re-applied all the changes to move to the new cert/key set set the permission to 777 then back to 744 because I didn't want it being too open and then restarted httpd and it came up ...

For those who may be interested, I have opened a ticket with the ElRepo folks and they are working on a newer RPM that should move the kmod-alx support up to handle the E2400 and E2500 hardware
https://elrepo.org/bugs/view.php?id=891

Excellent! Thank you very much!

This is on a current Centos 6.10 machine. We have been using the certs from letsencrypt.org and the auto renewal using certbot and all was fine, the certificate and private key were working perfectly. Now due to some policy change we can't use certbot any longer and have switched to dehydrate. This ...

It tells me: $ lspci -nn | grep -i net 02:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1] (rev 10) And according to my research I installed kmod-alx that supposedly knows about it (but does not appear to): $ rpm -q kmod-alx kmod-alx-0.0-10.el6.e...

I'm working on moving a working server based on Centos 6.10 (Final) that is running on old Core 2 Duo hardware to a newer i3 box. The only hold-up right now is that integrated ethernet hardware the new box is based on Atheros Killer 2400 which Centos 6 does not support - yes, I know that Centos 7 do...