Tag Info

New answers tagged

0

First stop the service: /etc/init.d/httpd stop Open configuration file of apache /etc/httpd/conf/httpd.conf Add DirectoryIndex homepage.html Here you can add. <VirtualHost *:80> ServerAdmin webmaster@example.com DocumentRoot /home/vb1.be ServerName vb1.be ServerAlias www.vb1.be ErrorLog logs/vb1.be-error_log ...


1

Use the DirectoryIndex directive: The DirectoryIndex directive sets the list of resources to look for, when the client requests an index of the directory by specifying a / at the end of the directory name. Local-url is the (%-encoded) URL of a document on the server relative to the requested directory; it is usually the name of a file in the directory. ...


1

You can run any service on any port (modulo privileges). That HTTP is on port 80 is pure convention, there's no technical reason to do this. So yes, you could run HTTP on port 1 (unless it is being used by another program). If it didn't work for you, then either you still need to fix the server configuration (check what netstat -ntl says), or, as goldilocks ...


23

I'm going to use Firefox as an example, because its open source and easy to find the information for, but this applies (probably with slightly different lists of ports) to other browsers, too. In August 2001, CERT issued a vulnerability note about how a web browser could be used to send near-arbitrary data to TCP ports chosen by an attacker, on any ...


6

apache restarts just fine but on the web it does not work. Port 80 is the default HTTP port for browsers as well as servers. This means in order to access a server that's operating on a non-standard port from a browser, you need to include the port in the address, e.g.: http://localhost:79/rest/of/url Without the :79 after the hostname, the browser ...


0

You can't ping from your Windows host to your Linux guest, Linux firewall is blocking the requests. Can you SSH from your windows into your Linux? ssh user@ipadress Make sure your ports are open (firewall is not blocking). For SSH you need port 22 to be open, for DNS port 53. You can open up ports like this. iptables -I INPUT -p tcp --dport 22 -j ACCEPT ...


1

On the box you are using to try to reach the web page, what are your name servers set to? If on Windows from a cmd prompt you can run: ipconfig /all If in Linux, your name servers should be in /etc/resolv.conf Make sure they are set to only use your new name server. By default, the system will search for the SOA (Start of Authority) and return whatever ...


0

Not sure if apache can read SANs.. This is still on their to do list I guess, that's why it's only a warning that may be safely ignored and I am not sure again if it is fixable. It may depend on your distro. Some say that removing default_host fixes this issue but then again that might be for those without SANs.


0

This doesn't seem like a YaST thing (YaST will only do very basic things for Apache)...you might find something in the advanced setting where you can add the module. However, you're probably going to still have to make a file in /etc/apache2/conf.d to tell Apache what to do when it comes across such a file. Here is a link for some more information. In ...


0

As far as iptables is concerned: ## default policy for OUTPUT iptables -P OUTPUT DROP ## allow related/established traffic, e.g. for incoming connections iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT ## whitelist some APIs (here 10.0.0.1) ## or package repositories, or your DNS (here 8.8.8.8), ... iptables -A OUTPUT -p udp --dport 53 ...


0

Im sorry but I cannot leave a comment yet (not enough rep) It sounds like there may be a conflict on port 80. You may need to change the port number used by one of the applications. It would probably be better to change the Webmin port to another number. This should be possible in the config files.


0

It's quite a minimal config for a basic virtual host. Create a new config file in /etc/httpd/conf.d/ and name it (for example) after your domain. It has to end in .conf though: # nano /etc/httpd/conf.d/example.net.conf <VirtualHost example.net:80> DocumentRoot /var/www/example.net/ </VirtualHost> Make sure there's viewable content in ...


0

I didn't know the ISPs blocked port 80 for customer machines. Appearently it was the problem. Monday I will know for sure if, in fact, it was only that.


0

I had the same problem when upgrading openssl from 0.9.8zb to 1.0.1i. $/tmp/src/openssl-1.0.1i/ ./config --prefix=/usr/local/openssl -fPIC $/tmp/src/openssl-1.0.1i/ make test $/tmp/src/openssl-1.0.1i/ sudo make install $/tmp/src/httpd-2.2.27/ ./config --enable-so --enable-ssl=shared --with-ssl=/usr/local/openssl ... $configure: error: ... Error, SSL/TLS ...


1

Use Allow/Deny instead: <Location /test/manager/> Order Deny,Allow Deny from 192.168.1.0/24 Allow from 192.168.1.4 192.168.1.5 192.168.1.6 </Location> Notice that this allows also any other IP, which I think is not what you want. If so, swap the Order and remove the Deny line: <Location /test/manager/> Order Allow,Deny Allow ...


0

Sorry, I have found the reason. This is totally because of the SSL CERT problem. Not really because of above notices. How do I do was that I enabled the Apache Detailed Logs and then that's the real move. It shows what really is happening, by showing the Failure at the loading of mod_ssl module, while starting the Apache. Then I realized it is because of ...


1

service apache fullstatus is an alias for /usr/sbin/apachectl fullstatus. From the manual of apachectl: fullstatus Displays a full status report from mod_status. For this to work, you need to have mod_status enabled on your server and a text-based browser such as lynx available on your system. The URL used to access the status report can be set ...


1

Yes, you can ignore it. ServerAdmin directive has no default value, so if you don't specific a value, apache won't process it. See more: Directive Quick Reference


0

A lot of inbound traffic isn't necessarily bad. I'm theorizing that whoever compromised your site noticed the lack of his vulnerability and is scanning your server for a new one. (Which he/she might or might not find.) As for your actual question: If your server uses name based virtual hosts (which I believe everyone who hosts multiple sites should) you can ...


0

(The following assumes Apache httpd.) If you have the handler configured, you can see status information at http://your.host/server-status, which includes the last request each thread/process handled. A snippet of example output from http://www.apache.org/server-status: Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request 0-3 14945 ...


2

How about using a re-write rule to block the 192.168.1.7 system from reaching the subdirectory? RewriteEngine on RewriteCond %{REMOTE_ADDR} ^192\.168\.1\.7$ [NC] RewriteCond %{REQUEST_URI} ^/ldap/manager/.* [NC] RewriteRule ^(.*)$ - [R=404,L] Edited from the original answer; this now sends back a 'forbidden' error ...



Top 50 recent answers are included