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

This question already has an answer here:

We used to work with a local Apache instance (WAMP) as a development environment, but we installed recently a PRTG server on the same machine, so it listens to the same port, as it is a web-based tool.

We are not able to reach our Apache server anymore as web requests on the server IP keep going to PRTG.

I changed the PRTG listening port to 8080 so that we would have 2 web servers listening to 2 dfferent ports.

It doesn't seems to work well: when I try to reach with a browser (Firefox, Chrome) it instantly changes to, and I get to PRTG home page.

Why does it changes from what I requested ? Should I use a totally different non-standard port ? What solutions do I have ?

share|improve this question

marked as duplicate by HopelessN00b Mar 8 '15 at 22:11

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

You should really take this up with PRTG support. – John Gardeniers Dec 4 '12 at 10:11

there are two potential causes to be checked first:

  1. Set PRTG on port 8080 but with HTTPS since there is a forwarding to port 80. See also this KB post.
  2. It is "only" hit 80 on localhost/ port, it is the report generator in PRTG, you can that solve with this.

Bonus Solution: Go to "Windows Service Management Console" and make sure to start the PRTG web server after the Apache. PRTG will only take ports that are not already taken by the Apache.

share|improve this answer

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