Daniel Barrett wrote: > On December 9, 2020, Dan Ritter wrote: > >> Thanks Dan. Mistake on my part, but adding ServerName didn't change > >> the 403 error behavior. > >> > >> I should add that my localhost has ~10 other websites running on it > >> (all over http) and SSL doesn't work in any of them (same 403 error). > > > >OK, what does the log say? > > Sorry, I should have said: hitting the https site (403 error) produces > no messages at all in the error.log and access.log.
Is apache actually using port 443? sudo netstat -tlnp | grep 443 Kill the non-apache thing (or understand it, first), and check that somewhere in the apache config is Port 443 and then restart apache. There should always be a log entry for a 403. -dsr- _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
