This page is for those who host on their own Windows server and are trying to diagnose the cause of a 404.
- If your browser on the server is displaying the page (http://127.0.0.1) properly, it's a networking problem:
- check server.xml for address binding.
- Check the Noodle block and allow lists.
- check port forwarding, routing, firewalls, and dns on the server, client, and every device inbetween.
- If your browser on the server is displaying the wrong page or anything other than a timeout, it's a service conflict (logs contains "Address already in use"):
- Use a different port or stop and disable other services using port 80.
- Windows - built in:
- sc config http start= disabled
- net stop http /y
- Linux - list what is using the port:
- netstat -lnp | grep ":80"
- Windows - built in:
- Use a different port or stop and disable other services using port 80.
- If there is no noodle.log it's a .bat or Java problem:
- run the intranet.bat one line at a time to isolate the problem.
- reinstall Java and check intranet.bat can find it.
- If there is no java.exe in the task manager it's a config problem:
- look in the log folder for errors.