Tag Info

New answers tagged

1

$ sudo grep -ri lampp /etc should show you what did it. Maybe /etc/rc.local or some other cruddy init script.


0

The problem was in nginx - changing line: proxy_set_header X-Host $var_domain; to proxy_set_header X-Host $host; fixed the problem


2

Looks like mod_security is working perfectly. It blocked the request because the Host header only contained an IP address, which is what this rule is meant to do. You should be using an actual hostname to refer to your web site, in production. It's also a good idea in development too, but if you need to use an IP address in development you can always ...


0

First... stop using IfModule on bits that aren't optional. (not sure what is or is not required) They're only useful if you have a fall-back way of recovering if that module doesn't exist or isn't loaded. Otherwise, apache will start without error... despite the fact that 90% of your config won't actually be loaded. A quick way to test and ultimately ...


0

Turns out the first non-UCC certificate was under the same CommonName as the UCC certificate. Simply using the UCC certificate on all the VirtualHosts sovled the issue.


0

I can confirm the above solution worked for me but I had to fix my ProxyPassmatch settings as well. Old config <IfModule proxy_module> ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9000/home/YOURDOMAIN/public_html/$1 </IfModule> New config - different rewrite filter, plus code from above <IfModule proxy_module> ProxyPassMatch ...


0

If your error message is " Ping request cound not find host domain.ro. Please check the name and try again " the error does not lie with your apache configuration. The nameservers hosting your domain is not reporting any A-record for your domain (assuming the DNS-client you are trying to ping from is working correctly). Start by looking if a nslookup for ...


0

Authentication sequence and requirements still not clear to me, but other than that should be easy with apache. I have implemented a similar setup using cookies. You need to have 2 locations under the same domain (to allow access to the same cookies) - one protected , another not protected (used to display the login page and create a cookie upon successful ...


2

First have you enabled mod proxy on apache? Secondly try remove ProxyPreserveHost On In addition make sure the port is opening; easiest way to check is go to http://www.yougetsignal.com/tools/open-ports/ (Enter website address and port 80) Hope this helps


1

As @ikrabbe guesses, they are symlinked. # ls -las /etc/httpd total 16 4 drwxr-xr-x 4 root root 4096 Jun 19 12:43 . 4 drwxr-xr-x 50 root root 4096 Jun 19 12:43 .. 4 drwxr-xr-x 2 root root 4096 Jun 19 12:43 conf 4 drwxr-xr-x 2 root root 4096 Jun 19 12:43 conf.d 0 lrwxrwxrwx 1 root root 19 Jun 19 12:43 logs -> ../../var/log/httpd 0 lrwxrwxrwx 1 root ...


1

I'm just guessing: /etc/httpd/modules links to /usr/lib64/httpd/modules, so both are the same files.


0

Are you sure the socket is only in /tmp on CentOS 7? Recent versions of Fedora have two copies of the socket, one in /run/postgresql (which is where /var/run/postgresql is really located after links are resolved) which is the preferred version on modern systems, and one in /tmp for legacy clients that expect to find it there. In any case if you do need to ...


0

Just put your desired commands in /etc/rc.local file, and they will be executed at the end of each booting process.


1

I see 2 possible causes: When Apache 2.2 tries to load content behind ProxyPass url and it doesn't respond, then sometimes whole vhost using this ProxyPass stops working. Tested on Debian Squeeze and Wheezy with default Apache 2.2. Your server may be also experiencing random problems with DNS resolver, which affect mapping of ServerName to vhost. You can ...


3

The OS has filesystem cache, which caches read / write requests to the actual hardware device. Then to the specific questions: Apache doesn't do caching. The include() functions don't do caching in default PHP installations. If you install an OPCode cache like APC, Xcache or OPCache, then it will cache compiled versions of the code in memory. File system ...


4

Yes, if it has enough RAM, the file system of Linux will cache these files. All other layers rely on the FS cache. There might be higher levels of caching that caches the generated output of the site, but this has to be specifically configured with an appropriate module like APC.


0

Another approach is you could do killall httpd as a way to kill all processes named httpd.


0

Try: find / -name "httpd.pid" Then delete the pid file, if it exists. Also, just in case: systemctl stop httpd systemctl disable httpd Machavity is right too, whenever you grep from the output of ps you're going to see your grep command too. It's something you'll get used to.


1

You have to understand that when you grep httpd you'll not just get back any apache processes but the grep process as well. You're seeing your own command reflected back at you. # ps ax | grep httpd 1818 ? Ss 0:53 /usr/sbin/httpd 38729 ? S 4:38 /usr/sbin/httpd 38730 ? S 4:49 /usr/sbin/httpd 54915 pts/0 S+ ...


0

On a Red Hat based system, there actually is no such package which will pull in everything necessary for a basic LAMP stack. A minute or so with repoquery is sufficient to demonstrate this. To install such a stack, you need at minimum: httpd php php-mysql mysql-server


1

He may be thinking of yum groups, but even then there's not just one group that does everything you want. Try yum groupinstall "Web Server" yum groupinstall "MySQL Database server" yum groupinstall "PHP Support" That said, what you're doing is also fine: yum's job is to manage dependencies, so doing yum install httpd will automatically pull in everything ...


0

If you define only one virtual host, then all requests to httpd will be served by that virtual host, whether or not they match the ServerName or ServerAlias, because the first virtual host is also the default virtual host. Search for "default virtual host" in the Apache "Name-based Virtual Host Support" documentation. Note also that once you define any ...


-1

You need to define a VirtualHost for every web page that you want to show; even if 192.168.1.4 is the main one, you also need to define a VirtualHost where define "ServerAlias 192.168.1.4". If there's only one VirtualHost, you will be redirected always to the site defined in ServerAlias.



Top 50 recent answers are included