• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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