• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Release port 5432 for internal use (localhost)

Émerson Felinto

Regular Pleskian
I tried to create a docker instance however it needs access to a service that uses port 5432 as you can see in the print below.

Screenshot 2018-03-10 at 19.28.35.png

From what I understand about the problem I need to free port 5432 for internal use (localhost) but how do I do this on the firewall. Which rules should I add?
 
It's not able to connect as there is nothing running on the Docker discourse container on port 5432 by default.

[root@plesk ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e559d908dfa7 bitnami/discourse "/app-entrypoint.s..." 7 minutes ago Up 8 seconds 0.0.0.0:32769->3000/tcp discourse
[root@plesk ~]# docker exec -it e559d908dfa7 bash
root@e559d908dfa7:/# lsof -i:5432
root@e559d908dfa7:/#
 
Back
Top