• 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.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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 ElasticSearch ports not accessible from WAN

Stefan Saeys

New Pleskian
Server operating system version
CentOS Linux 7.9.2009
Plesk version and microupdate number
18.0.46 Update #1
I’m running Plesk with Docker image elasticsearch:7.3.2.

In elasticsearch settings:
port 9200 is mapped to port 4960
port 9300 is mapped to port 49159.

Plesk Firewall has been configured to allow all external traffic to ports 49160 and 49159 (both UDP and TCP).
Disabling Plesk firewall doesn’t solve the issue. WAF is disabled.

I still have Imunify360 enabled but do not see anything that blocks traffic from my internet WAN IP (whitelisted anyway).
Any suggestions appreciated.
 

Attachments

  • Screenshot 2022-09-14 at 19.35.22.png
    Screenshot 2022-09-14 at 19.35.22.png
    187.4 KB · Views: 30
  • Screenshot 2022-09-14 at 19.36.01.png
    Screenshot 2022-09-14 at 19.36.01.png
    39.6 KB · Views: 28
How did you start this ElasticSearch?

If you did start from the CLI with bind to localhost. You will not be able to access it externally.
 
Back
Top