| 1 |
Mick wrote: |
| 2 |
>> I'd take that as a big broad hint that it is looking somewhere else |
| 3 |
>> for certificates in this release and it found default certs. |
| 4 |
>> |
| 5 |
> +1 |
| 6 |
> |
| 7 |
> Check in your default apache (most likely) or vhosts configuration files that |
| 8 |
> you have SSLCertificateFile and SSLCertificateKeyFile paths pointing to where |
| 9 |
> your certs and private key are stored. It may be that you were not very |
| 10 |
> careful with etc-update and it restored default settings? |
| 11 |
> |
| 12 |
Many thanks!!! |
| 13 |
|
| 14 |
While I remain sceptical that it was etc-update that spannered my |
| 15 |
configuration, stating the obvious to me overcame this... I've still no |
| 16 |
idea what did cause this to go wrong - but... essentially, my config was |
| 17 |
looking for /etc/ssl/apache2/server.crt, while the certificates I was |
| 18 |
checking were /etc/apache2/ssl/server.crt - and similarly for the key. |
| 19 |
I'm still a little baffled about how it appeared to work previously... |
| 20 |
but I now see what is wrong - even if I'm puzzled about how I got here... |
| 21 |
|
| 22 |
I guess, one might ask if default certificates are a good idea - and, if |
| 23 |
they are - maybe we should ask why they don't "work". For my purposes, |
| 24 |
however... solved! Thanks again. |
Archives