The discussion is about a dev install bound to 0.0.0.0. darkpixlz is trying to start an Ubuntu dev install on a server version of the OS, but it’s not accessible because port 80 is taken by Pi-hole. They tried accessing it via localhost:4200, but failed.
darkpixlz wants to run the dev install on 0.0.0.0:4200 or 192.168.0.24:4200 instead. sam warned that binding to 0.0.0.0 can be risky, but darkpixlz assured that the machine isn’t forwarded to the internet.
A possible solution was found in a Meta Discourse post, which suggested using the --b 0.0.0.0 flag. However, darkpixlz reported that it still doesn’t work as expected, despite being able to access other content running on the same machine.
Hi,
I was trying to start an ubuntu dev install to work on my theme’s new version. It’s the server version of the OS so I cannot directly access Firefox. I can’t run a normal install because :80 is taken by Pi-hole (and setting up nginx is going to cause more problems than its worth).
If I go to it’s local IP and :4200, it says it can’t connect:
Is there a way to get it to run on 0.0.0.0:4200 (or for this matter 192.168.0.24:4200)? Thanks!
Its risky, cause you don’t want to open this to the world…
I think this does a reasonable job at answering?
The machine isn’t forwarded, it won’t be open to the internet.
My takeaway from the AI was --b 0.0.0.0, will try that when I can
