Tag Info

New answers tagged

0

There was a typo in worker.properties worker.local.local.max_packet_size=65536 instead of worker.local.max_packet_size=65536


0

Ok, so to upgrade, do the following: make sure that in the file /etc/yum.repos.d/remi.repo, that you enable the remi-php56 repo [remi-php56] enabled=1 And you can then do 'yum update php`. If you get problems such as inconsistency between Modules API and PHP API, the installation still works. But you may end up having to update PECL + PERL. What I did ...


1

You can use RedirectMatch Directive RedirectMatch 410 <appropiate rule> Update: For a custom error page, you can add: ErrorDocument 410 /410error.html An alternative method if you have many files is to use the following: # Is the request for a non-existent file? RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d ...


0

After looking at your comments, this is how I would achieve what you're looking for: (There may be a better way to do this, but this works) Set 2 different roots with the DocumentRoot property: <VirtualHost *:443> ServerAdmin webmaster@localhost ServerName example.com DocumentRoot /var/ssl_content </VirtualHost> <VirtualHost *:80> ...


1

It's hard to say exactly where the duplication is occurring based on the information you've provided. Essentially, a rule is being included twice which is usually defined within the modsecurity.conf file. You may be including this file twice, or you have copied its content into another apache conf file. To find the problem, you'll need to search for the ...


0

Define "Fails". Do you have an SSL cert installed for the default vhost? Do you just get a browser warning about the wrong cert? Or do you actually get back the wrong content? Does your browser support SNI? SNI is needed to handle multiple SSL certs installed at the same IP.


2

Since you are defining NameVirtualHost *:80 in your httpd.conf the only VirtualHost definition you have is being used when connecting via the IP. Put the following into /etc/httpd/conf/httpd.conf (at the end) or in a new file called /etc/httpd/conf.d/000-default.conf: <VirtualHost *:80> DocumentRoot /var/www/html ServerName servername.host.com ...


0

Answering my own question... Yes, CentOS 5 DOES support SHA256 signed certs. A Clean VM works just fine, there must be an apache configuration problem. There is nothing useful in the error_log... Take a closer look at your ssl_error_log there isn't anything useful regarding apache halts due to ssl stuff in the error_log. By default apache uses ...


2

I'm doing something similar - with a laravel install in the home directory of the ec2-user so that when I want to update the site, I can do so without root permissions. The crucial bit, or the part that got me stuck was that you need to allow directory execute access to the home directory of the ec2-user. Not doing this caused me quite some time wondering ...



Top 50 recent answers are included