0 Membres et 1 Invité sur ce sujet
SSLUseStapling onSSLStaplingCache shmcb:/tmp/stapling_cache(128000)
SSLUseStapling on SSLStaplingCache shmcb:${APACHE_RUN_DIR}/stapling_cache(150000)
[Thu Jan 18 13:14:06.321673 2018] [ssl:error] [pid 27445] AH01941: stapling_renew_response: responder error[Fri Jan 19 13:18:53.277487 2018] [ssl:error] [pid 20704] AH01941: stapling_renew_response: responder error
SSLStaplingCache shmcb:${APACHE_RUN_DIR}/stapling_cache(150000)
SSLStaplingCache shmcb:${APACHE_RUN_DIR}/stapling_cache(512000)
However, with OCSP stapling problems that used to definitely be with the OCSP server, now might be trouble on your web server. Apache is definitely capable of fetching a “try later” response and then stapling that to certificates and sending those over, which is, -ugh- I don’t know how they thought that option was helpful.If you definitely have, or think you might have, OCSP stapling enabled, then short of disabling it, which may not be possible from cpanel, you could try restarting the Apache server itself if that’s possible and then try the site a couple of time, leaving a few seconds between each try ? I think that when it’s restarted it will fetch a fresh OCSP response and so it might get a good response this time.