New answers tagged web-hosting
Port 80 is going to your dd-wrt config page. All you need to do is change that dd-wrt config page to another port. Then forward port 80 to the desired IP.
You need to setup Apache for that. Add a line like the following to your httpd.conf: AddType application/x-httpd-php .extension and it should work.
Short answer: yes. It's far far easier to use a subdomain since otherwise you would need a proxy. To extend on this, suppose you have site1, site2, and site3 on different web servers. Rather than trying to mess with a proxy, simply add a subdomain to your domain like site1.domain.com that points to the proper web server. The more complicated method (if you ...
You would want the SQL server to be as close as possible to your current VPS; preferably in the same datacenter for best results. It doesn't matter where it is for end-users because it should be your website accessing the database and not the users.
Change the CNAME for foo to an A record now. Point it to the same IP address as www. Then, when you are ready to go live with your web site on the new server, just change the A record. This has the additional benefit that you need not make any change on the old server.
You can just put a .htaccess in every Directory you don't want to get accessed with this content: Order deny,allow Deny from all
I disagree with both responses provided at this point because there are ways within BoxTrapper to mitigate backscatter SPAM. Note, that the SPAM referenced here are the "Challenge" notifications sent by Box Trapper to authorize the release of pending e-mails. I don't know of any major cPanel hosting company that enables Box Trapper by default. It's ...
This system should do the job. It's is capable of running modern Linux and Windows operating systems. Install an operating system on it and configure it for your web hosting needs. It can run VMware as well, but your RAM is a bit low for that. If you have questions about how to install and configure an operating system, seek the help of a consultant or a ...
First a remark. You should have used chown -R owner-user:vhost-group /path/to/webroot chmod -R 640 /path/to/webroot chmod -R u+X,g+X /path/to/webroot if /path/to/webroot didn't happen to be empty. The kind of stupid but unfortunately correct answer to your question is simply: Sorry, your question does not make sense. Why? You define (i.e. accept the ...
The first virtual host you define will be the "default" host. Thus all requests for domains not configured elsewhere will go to this first host. If you want requests for domains not configured on a server, but directed to it anyway to be ignored you need to create a separate, "catch all" dummy virtualhost that does just refuses all requests, and that is ...
You need to narrow the Listen directives to 192.168.1.90, like Listen 192.168.1.90:80 Listen 192.168.1.90:443 otherwise Apache will listen on all IP's (and incoming requests hit the default virtualhost).
You are on the right path with the Virtual Server setup. You need to take a closer look at your settings, and make sure Router Administration is disabled for the WAN port. It may be named something else, but you should see somewhere that blocks external access to the routers webconfig. Just to make sure though, are you testing from an external source? It's ...
It is not a PPTP problem. You would have the same problem with any VPN software. It is a simple routing problem. You most likely have your default gateway pointed at the VPN, you would have to for it to be of any use for torrent hiding. If your default gateway is AIMed at the VPN, then routing will not work right. Short of some advanced policy routing ...
Do you have any .htpasswd files on your server? This should be sufficient # password protection allowing multiple resources AuthType Basic AuthName "Restricted Area" AuthUserFile /home/path/.htpasswd AuthGroupFile /dev/null Require valid-user # allow public access to the following resources SetEnvIf Request_URI "(path/to/directory_01/)$" allow ...
Top 50 recent answers are included