• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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: 29
  • Screenshot 2022-09-14 at 19.36.01.png
    Screenshot 2022-09-14 at 19.36.01.png
    39.6 KB · Views: 27
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