On my system (Librem 14) when using a simple http server, say python2.7 -m SimpleHTTPServer or python3 -m http.server or even node’s http-server -p <some_port>, I am NOT able to access the server it is running from via http://<lan_ip>:<port>/ on other machines connect to the same network, BUT I AM able to access this from a browser locally only, so on the host machine and even on a virtual machine running on the host machine.
When running this same simple http server application on other similar systems (debian) on my network it works fine. I have no firewalls running, I’ve tried running the server as root, no luck. I cannot figure why I cannot access the tcp port remotely.
I have the same problem with my Librem 14 running PureOS. I suspect that PureOS uses some unusual kind of firewall that nobody knows how to configure. See this other thread:
One idea is that it could be that “nftables” is used instead of the old “iptables” that everyone is used to, I wrote something about that in the other thread. Maybe then the problem can be sorted out using some nftables commands, but I did not get around to trying that myself yet.
If you solve it, please write about the solution here, I’m sure others will have the same problem.
Nope my description was perfectly accurate in fully describing the issue. If you had read all of it you would have noticed the part where i stated “i have no firewalls running,” so obviously not a problem with iptables nor nftable (which i don’t even have installed). Also if the service was bound to the loopback i believe i would not be able to access the service from the LAN ip address on a virtual machine (however, this i may be wrong about). Whether or not i’m using the correct port is just insulting.
Thanks for sharing this thread - I will definitely post the solution when I find it. I do not have nftables installed, i do have iptables, although with no rules, and the service is not running. So perhaps i just need to keep digging.