New answers tagged

1

Check out mod_proxy. Something like this should work. <VirtualHost *:80> ServerName domainOne.tld #put info to point to your PHP app here </VirtualHost> <VirtualHost *:80> ServerName domainTwo.tld ProxyRequests Off ProxyPreserveHost On <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass / ...


3

Changing the webserver port also requires changing the SELinux policy for the webserver which is well documented : Run the semanage port -a -t http_port_t -p tcp 82 command as the root user to add the port to SELinux policy configuration. Run the semanage port -l | grep -w http_port_t command as the root user to confirm the port is added... ...


3

This looks like you have deployed a (puppet) template rather than the actual configuration file.


0

I had this issue yesterday on Centos7, nothing in the logs to suggest what the issue was. I could run apache, but not from systemctl - it would be available for about 90 seconds before deciding it had failed to start and then killing the service. My situation turned out to be DNS being blocked on a new firewall I was not aware of; unblocking the DNS ...


1

Similar issue, apache2 was responding to 443, nothing in the logs /etc/apache2# openssl s_client -connect localhost:443 -state -debug gave me the following SSL_connect:unknown state read from 0x1182fe0 [0x1189010] (7 bytes => 7 (0x7)) 0000 - 48 54 54 50 2f 31 2e HTTP/1. SSL_connect:error in unknown state 139790287365792:...


0

This kind of looks like something important got removed with the package installation. the errors relate to policy kit. Can you confirm that polkit and dbus are both still installed? rpm -qi dbusand rpm -qi polkit logs may also contain information but seems here a policy is preventing the start of these services due to dbus not responding...because dbus is ...


1

With SELinux the filesystem has extra "permissions" above and beyond the regular UNIX ones. If you were to run ls -Z ... (-Z is an SELinux extension to ls(1)) on files under /var/www/html across both machines I suspect you will see the following: On server A: drwxr-xr-x root root system_u:object_r:httpd_sys_content_t /var/www/html/ On server B: drwxr-xr-...


0

From what I can tell mod_proxy_html only really understands HTML 4.01 and XHTML 1.0 based on https://httpd.apache.org/docs/2.4/mod/mod_proxy_html.html#proxyhtmldoctype. Searching whether a <table> is allowed within an <a> turns up http://stackoverflow.com/questions/6013943/table-tag-inside-anchor-tag amongst other answers which suggests that it'...


0

So I found that another service had a defined status for TCP port 5000. But by replacing the -a option with -m for modify, added tcp port 5000 to http_port_t So the command that worked was: # semanage port -m -t http_port_t -p tcp 5000


2

On the systems I have to hand (C6, C7 and F24), tcp port 5000 has an SELinux context of commplex_port_t. This will be why, when you try to add it you get the error message /usr/sbin/semanage: Port tcp/5000 already defined To change the context of tcp port 5000 from commplex_port_t to http_port_t you will need to use the -m | --modify switch -m, --modify ...


0

Sounds like you are using RHEL/CentOS 6.x, as it uses Apache 2.2.15 as the base version. The whole idea with RHEL and its derivates is that during a life-cycle of one major release the software versions do not change at all. Instead the severe bugs are fixed by backporting them and all kinds of small enhancements (such as support for new hardware) are made....


0

Check if your mysql server is up and running if everything else is correct. Run the below command, /etc/init.d/mysqld status If everything is correct your wordpress should install correctly as sun rises every morning.


0

What are the hardware specs on the server? Could you try running systemctl status httpd -l and show us the output? After starting it you could run top and hit shift+m and make sure it's not eating up all of your machines memory.


-1

I was also facing the same issue until I fount out the root cause of the problem... Problem: Currently, my website is running on Wordpress with XAMPP on windows cloud server and the CPU usage is going 100% Solution: checked my Apache log file(access.log) and some one continuously was trying to access the xmlrpc.php file and 10 requests every seconds that ...



Top 50 recent answers are included