Hot answers tagged

3

You'll can change which port it's listening on, either the proxy server or Apache, whichever is most convenient. Information on how to do this for apache is here - effectively, have a line stating Listen XXX where XXX is the port number you wish to use in your apache conf. Then, visit http://127.0.0.1:XXX in your web browser.


2

I have the same problem as well. Seems like a trojan hidden in one of the Chrome extension. Just don't know which one. I have found this webpage on the same topic: http://www.eenyhelp.com/answer/bug-811371-chromium-unwanted-redirection-chromium-help-215926861.html Quick and dirty way to block it: block access to www.free-merchants.com (either on the ...


2

For me it was the chrome extensions "Facebook Album Downloader". Deactivate and it is gone. I reported it on the Chrome store. You should to the same. I found it by deactivating all Chrome extensions and then re-activating them one by one until the problem shows up.


2

So I found a differential. Question is: What does this mean, and how does one correct it? Expanding on what user @Dirk noted, SELinux is a system which relies on "contexts" to increase the security of your system, a context describes what kind of actions can be performed on a certain file or directory or what can a file be used for. In this case, ...


1

If you want to simply hide the "unsecure" automatic directory listing you can do two things: One would be to simply put a blank index.html file in the root directory (/var/www/) and when your IP is entered, it will simply display a blank white page. Another option you can do would be in your site configuration file inside the <VirtualHost> tag add ...


1

If you have cron installed (you should have it anyway), do crontab -e and put the command: minute hour day month dayofweek command # this part is provided by crontab, just for reference. 0 0 * * * /bin/systemctl restart httpd.service


1

You could run your script via a cronjob. For this, add this to your crontab-file: 59 23 * * * /bin/sysemctl restart httpd.service This will execute /bin/sysemctl restart httpd.service one time at 23:59 every day of every week of every month.


1

Even though the cron solution is certainly the best option, you can also use some Systemd directives to get almost the same result. As root, create the /etc/systemd/system/httpd.service.d directory: mkdir /etc/systemd/system/httpd.service.d cd /etc/systemd/system/httpd.service.d Create the restart.conf file and paste the following lines into it: ...


1

for those of you who comes here, it was the masquerading. firewall-cmd --zone=public --remove-masquerade and it works. Zone public because the configuration described in the question wasn't the active one, and both bond0 and both1 were added to zone public


1

Apache is indeed multithreaded, as it spawns a new process for each new connection. As for the child processes lifetime, it's killed when the connection is aborted, either by a disconnect or timeout.


1

Assuming you have a simple httpd configuration, a neat way to implement what you are looking for would be: Create a file named /etc/httpd/conf.d/gitlab.conf with the contents: ProxyPass "/gitlab" "http://123.456.789:8888" ProxyPassReverse "/gitlab" "http://123.456.789:8888" Create another file named /etc/httpd/conf.d/kanban.conf with the contents: ...


1

You are not explicitly disabling the RC4 suite, and therefore are implicitly allowing it. You can add :!RC4 to the end, but your allowed cipher suites are not best practice, so I suggest using the line below instead: SSLCipherSuite ...



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