• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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