[Help] Internal TOS6 postgresql listening to the network
Posted: 18 Dec 2025, 17:55
Hello.
I tried to contact support through the chat, but it looks like I was not understood at all, redirecting me to external documentation as I was speaking about a docker container or something I installed myself.
I am speaking about the internal postgresql installed with TOS6, not something I installed myself in anyway.
And it is something you could check with just a "nmap" or internal "lsof" commands
The internal postgresql port tcp/5432 it is exposed to the LAN, and I think it is serious on one hand and could be easily fixed. With my limited knowledge I think either in of the two following fixes:
- Create a default firewall rule that disallow incoming external traffic on port tcp/5432
OR
- modify the postgresql configuration to only listening to the loopback interface (I do not know the implications that this could have with your own software)
Perhaps with the TOS7 beta would be a good time to think about it.
Thanks!
I tried to contact support through the chat, but it looks like I was not understood at all, redirecting me to external documentation as I was speaking about a docker container or something I installed myself.
I am speaking about the internal postgresql installed with TOS6, not something I installed myself in anyway.
And it is something you could check with just a "nmap" or internal "lsof" commands
The internal postgresql port tcp/5432 it is exposed to the LAN, and I think it is serious on one hand and could be easily fixed. With my limited knowledge I think either in of the two following fixes:
- Create a default firewall rule that disallow incoming external traffic on port tcp/5432
OR
- modify the postgresql configuration to only listening to the loopback interface (I do not know the implications that this could have with your own software)
Perhaps with the TOS7 beta would be a good time to think about it.
Thanks!
