Opened ports 8983/9983, but still can't access Solr web interface

Question

Debian 12, Solr 9.7.0, standalone installation with 1 core

I can interact with Solr from the command line using curl/localhost. I can even access the web interface from the command line using Links browser, but I'd like to use the GUI.

I've created the security groups opening ports 8983 and 9983 to My IP only, and attached them to my instance. (And I can SSH successfully.)

I added SOLR_JETTY_HOST="0.0.0.0" to /opt/solr/bin/solr.in.sh and restarted solr.

However, `sudo ss -tulpn | grep 8983` seems to indicate that solr is still only listening on 127.0.0.1

`tcp   LISTEN 0      50     [::ffff:127.0.0.1]:8983            *:*    users:(("java",pid=9324,fd=48))`

What else must I do?

re:Post Agent · Accepted Answer

Based on the information provided, it seems you've taken several correct steps to access the Solr web interface, but there are a few additional points to consider:

1. Firewall settings: While you've configured the AWS security groups correctly, make sure that the local firewall on your Debian instance (if enabled) also allows incoming traffic on ports 8983 and 9983.

2. Solr configuration: Check if Solr is configured to listen on all interfaces, not just localhost. In your solr.in.sh file, ensure that SOLR_JETTY_HOST is set to 0.0.0.0 instead of localhost or 127.0.0.1.

3. Correct URL: Confirm that you're using the correct URL format. It should be http://[EC2-Public-IP]:8983/solr or http://[EC2-Public-DNS]:8983/solr.

4. Instance public IP: Verify that you're using the correct public IP address of your EC2 instance, as it can change if the instance is stopped and started.

5. Network ACLs: If you're using custom Network ACLs, ensure they're not blocking the traffic to these ports.

6. VPC settings: Check that your VPC and subnet configurations allow inbound traffic from your IP to the instance.

7. Solr service status: Confirm that the Solr service is running and listening on the correct ports using a command like 'netstat -tuln | grep 8983'.

If you've verified all these points and are still unable to access the Solr web interface, you may want to check the Solr logs for any error messages or configuration issues that could be preventing external access.

Remember, allowing inbound traffic on any port represents a potential security vulnerability, so ensure you're following best practices for securing your Solr instance.  
**Sources**  
[Security Groups and Classic Ports | AWS re:Post](https://repost.aws/articles/ARWPW6FQCKSyWsUZNLO_GGBw/security-groups-and-classic-ports)  
[View web interfaces hosted on Amazon EMR clusters - Amazon EMR](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-web-interfaces.html)

randy_weinstein · Answer

Since you can SSH, it sounds like an issue with: NACL, Security Group, Host-based firewall, or Application source filtering.
I'd reconfirm the direction as an Inbound rule on the Security Group. Make sure the in and outbound NACLs are open. Confirm that host-based firewall, ie. iptables, is not running. Confirm that the web server allows connections from any IP address.

[Solr has this nice looking Reference Documentation: SolrCloud on AWS EC2](https://solr.apache.org/guide/8_0/aws-solrcloud-tutorial.html)

Opened ports 8983/9983, but still can't access Solr web interface

Relevant content