Troubleshoot access issues

Available in Classic and VPC

You might run into the following problems when using Search Engine Service. Find out causes and possible solutions.

Cannot connect via SSH

You cannot connect via SSH and connection timeout occurs.

Cause

This can occur if access is restricted to specific sources. Also, if firewall rules are incorrect, or if the port is blocked.

Solution

• Check the cluster’s ACG settings on the manager node.
• Run telnet {host} 22 or nc -zv {host} 22 command to verify port connectivity.
• If you still cannot connect after configuring the ACG, capture the connection attempt screen and contact Customer Support.

Cannot access OpenSearch Dashboards on port 80 over SSL VPN (Windows OS)

You cannot access OpenSearch Dashboards on port 80 over SSL VPN (Windows OS).

Cause

This occurs due to Windows TCP stack settings.

Solution

Change the environment settings as follows so you can access through port 80:

1. Run cmd.exe as an administrator.
2. Enter chcp 437.
3. Enter the command netsh interface tcp show global and verify that RFC 1323 Timestamps is set to disabled.
4. Enter netsh int tcp set global timestamps=enable.

Troubleshoot "No server is available to handle this request" error messages

"No server is available to handle this request" during ALB connectivity test

Cause

Search Engine Service does not currently support public SSL certificates.
Even if the ALB performs SSL termination, internal communication allows only HTTP, which causes this error.

Solution

• If you use a public SSL certificate on a Load Balancer, use HTTP for internal communication.
• If you must use public SSL end‑to‑end, install OpenSearch yourself and operate it behind a reverse proxy (for example, Nginx).