Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My ISP blocks incoming connections to port 80, but I want to run a webserver from a home computer. I also have a domain name registered.

What are the easiest/best ways to host my site?

My only idea so far is: pay for a hosting account, set up apache there to route requests from there to my home connection on an open port (eg 8080)


locked by HopelessN00b Mar 16 '15 at 17:00

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off topic by John Gardeniers, Iain, mailq, gravyface, Ben Pilbrow Oct 15 '11 at 16:34

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

Get a different ISP. – Ward Oct 15 '11 at 7:15
Forget it. Just pay a hosting account. No need to do that at home. Low end hosting is dead cheap. – TomTom Oct 15 '11 at 7:18
There are tons of reasons to do this and other people who would be interested in solutions. Also, almost every broadband ISP in Canada does this. – Will Oct 15 '11 at 7:23
Please do us the courtesy of reading the FAQ. – John Gardeniers Oct 15 '11 at 8:23
Question must be as least re-tagged. Problem have nothing common with any used tag. Even just "apache" (not "apache2") applicable only partially. It's a question about "dns" and "SRV-records". But it's offtopic anyway, according to FAQ – Lazy Badger Oct 15 '11 at 8:41

Why pay for hosting? Couldn't you get a free hosting account somewhere, point your domain to it, and then use a simple redirect for all traffic?

I assume this is for a small website you built at home because it was convenient. Maybe a dev environment or running some scripts you want access to from anywhere. If you actually want to run a production environment from home AND your provider blocks port 80, you're crazy.

One question would be - do you want to domain name to show up when browsing the site? If not, simple redirects from to IP.ADDR.AT.HOME would work just fine (see the following link for all kinds of ways to redirect:

If you want your domain name to show up, here's some hacking I would do:

The big problem I see is because you're trying to redirect everything from one server to another, you're gonna have to convert POST arguments to GET (since posting to a 3rd party server which only redirects means your post data will get lost).

If your hosting provider allows some scripting language, you could use PHP or Perl to redirect all requests:

  $args = $_GET;
  $postArgs = $_POST;
  $paramString = (empty($args) ? '' : '?');
  if (empty($args)) $paramString = (empty($postArgs) ? '' : '?');
  $first = true;
  foreach ($args AS $key => $value) {
          $paramString .= (!$first ? '&' : '') . $key . '=' . $value;
          $first = false;
  foreach ($postArgs AS $key => $value) {
          $paramString .= (!$first ? '&' : '') . $key . '=' . $value;
          $first = false;

  $uri = $_SERVER['REQUEST_URI'];
  header("Location: http://IP.ADDR.AT.HOME:8080$uri$paramString");

Really depends on what you want to do.

Free hosts have very bad SEO. – Calmarius Dec 25 '12 at 23:09

It is almost inconceivable that your ISP both permits you to run a web server and blocks port 80. If your ISP does not permit you to run a web server, then you can't run one. You are trying to find a technical solution to something that is not a technical problem. You do not have the right to run a web server.

Delirium. Web for internal work may be easy on policy, with blocking 80 port on border for internetworking. – Lazy Badger Oct 15 '11 at 9:38
Is it just me, or does this comment make absolutely no sense at all? – gravyface Oct 15 '11 at 15:47
@gravyface I'm not sure what he's trying to say? I think he's saying a webserver for LAN stuff is ok. – Jacob Oct 15 '11 at 18:17

Not the answer you're looking for? Browse other questions tagged or ask your own question.