This question already has an answer here:
- Why not use a WAMP stack? 4 answers
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 xxx.xxx.xxx.xxx:80 with a browser (Firefox, Chrome) it instantly changes to xxx.xxx.xxx.xxx:8080, 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 ?