127.0.0.1:8080 won't load on a remote machine

[maredzki]

I'm trying to diagnose some tuning errors and it would be nice if I could load the webpage on a remote machine. The pi is headless so I would have to connect it to a monitor.

Is that possible at all?

Thanks much!!!

 

[NebraskaCoder]

What software are you using?

 

[maredzki]

boatbods OP25

 

[NebraskaCoder]

Use the ip address as 0.0.0.0:8080 when starting OP25.

 

[maredzki]

I've checked, there is no firewall ports that are being blocked, it seems it just listens on localhost/127.0.0.1 and not on the wifi interface. I wonder if I can just change the IP to my wifi interface and make it a go

 

[maredzki]

Use the ip address as 0.0.0.0:8080 when starting OP25.

Ok, checking now... brb

 

[maredzki]

Ok, checking now... brb

That worked!

Thank you.

 

[NebraskaCoder]

You're welcome. For other people reading, in the command line the -l option should be

-l http:0.0.0.0:8080

where 0.0.0.0 is all ip addresses listened on (or 127.0.0.1 for local computer access only) and 8080 is the port you want to listen on (8000 is the documented port).

 

[maredzki]

My PI was throwing tuning errors for a while and I didn't even know.

Anyway to monitor this easily?

 

[NebraskaCoder]

My PI was throwing tuning errors for a while and I didn't even know.

Anyway to monitor this easily?

You can watch the console for errors. You can also redirect the console errors to a file on the system by adding 2>stderr.log at the end of your command line. You can also redirect it to the temp folder by adding the following:

 2>/tmp/op25err.log

And then monitor it by using tail -f (path to file) such as:

 tail -f /tmp/op25err.log

 

[NebraskaCoder]

If redirecting to a file, you would need to monitor the file on a separate terminal.

 

[maredzki]

I think I will have to check with PRTG or something and get alerted automatically.

Thanks!

 

[NebraskaCoder]

Yup. If you can monitor it and get alerted, that is another method.

 

[boatbod]

If you are running headless you generally need to run with the http console (or log in with ssh) because bad things happen if you try to start op25 at boot time configured for curses with no actual terminal available. All my streaming servers run headless this way, and it is a simple matter to pop up a browser, punch in the ip address and check the console/plots for anything untoward.

One thing to be careful of: DO NOT feel tempted to port forward the http terminal through a firewall without adding your own security via SSH tunneling or similar. The httpd server is completely insecure and likely to be susceptible to all sorts of exploits.