Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
The operating system my web server runs on is (include version): ubuntu 16.04
I can login to a root shell on my machine (yes or no, or I don’t know): yes
Previously I used rapid ssl cerificate. Aftet it expired I moved to lets encrypt free ssl and installed on my server. But site uses still old ssl certificated after couple of refreshes taking new ssl certificate and resources(css, images, scripts) are not loading gives NET::ERR_CERT_DATE_INVALID error.
It is odd that Apache would randomly serve up different certificates on different requests for the same domain.
I think one of two theories are likely.
First is that Apache has screwed up and has half the workers on old configuration, and half on new. I have seen this happen in the past. In that case, do a hard restart of Apache:
service apache2 stop
killall -9 apache2
service apache2 start
The other theory is that (somehow) it is doing a round-robin between duplicate virtual hosts, as @JuergenAuer suggests. In that case, please additionally show the output of:
Have you tried doing the hard restart (including orphaned processes) of apache2 as I suggested in the earlier post? I’d be curious to see whether killing off all the processes makes any difference.