Tag Info

Hot answers tagged

3

(summary of comments) You have a conflicting SSL virtual host from the Ubuntu/Debian default-ssl virtual host. a2dissite default-ssl will fix the immediate problem. The Apache HTTP Server Wiki has a guide to configuring name-based SSL virtual hosts which you should review. The guide shows them all in one file, but you can split the different VirtualHost ...


1

You can just set it to localhost. Edit /etc/apache2/conf.d/httpd.conf: ServerName localhost The ServerName directive can be use in two contexts: server config or virtual host. In server config context, ServerName directive is used when creating redirection URLs. In virtual host context, ServerName directive is used to uniquely identify a virtual host. ...


1

The transport method of the connection between the client and this httpd instance is totally independent of the transport method between the httpd instance and the server you are proxying to. That means, just put the proxy lines (at least ProxyPass and ProxyPassReverse) to your HTTPS configuration: NameVirtualHost *:443 <VirtualHost *:443> ...


1

This is a hard situation. The requests seem to match a malicious pattern, so your task is to block the IPs making malicious requests from your server. These days there are all kinds of fancy hardware to do this. If you can't get that then you are down to manually creating firewall rules or apache rules to ignore or block requests from certain IPs. For ...



Only top voted, non community-wiki answers of a minimum length are eligible