Skip to main content

Unable to access Port 8984

Aryup
Hello everyone! I'm on a CentOS 7.9 serveur with WHM/cPanel I installed Solr recently and i'm unable to connect to the default port of solr : 8984 connexion is timed out by the server. I use CSF as a firewall and the port 8984 is allowed in TCP_IN TCP_OUT UDP_IN UDP_OUT My IP is whitelisted in CSF and Modsec and i allowed every connexion in the Host Access Control. The result of the command netstat -npl | grep :8984
tcp6 0 0 127.0.0.1:8984 :::* LISTEN 21423/java
I don't know why this port would be blocked, does anyone have a clue on what i could have missed? Thank you!

Comments

13 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! If you temporarily disable CSF, does that allow you to connect to the port? If not, you might want to ask your provider to see if there is something external to your machine that could be blocking this port.
    0
  • Aryup
    Hello, thank you a lot for your answer. I did what you suggested and disabled CSF, i'm still unable to reach that port. Meanwhile, as you suggetsed i have open a ticket to my provider. I will post here the update as soon as he get back to me. Thank you!
    0
  • cPRex Jurassic Moderator
    That sounds good - let us know what they have to say!
    0
  • quietFinn
    The result of the command netstat -npl | grep :8984
    tcp6 0 0 127.0.0.1:8984 :::* LISTEN 21423/java
    I don't know why this port would be blocked, does anyone have a clue on what i could have missed? Thank you!

    Did you open port 8984 in TCP6_IN in CSF?
    0
  • Aryup
    Hello, quietFinn. The port 8984 is open in TCP6_IN in CSF Thank you.
    0
  • Aryup
    Hello everyone, Our provided said that they do not block any port of our server, therefore the problem is from our end. We are still looking for that issue and don't have a clue of what could block that port.
    0
  • cPRex Jurassic Moderator
    If you try an nmap test to the port, does that connect? For example, here's what a test to the cPanel mailserver looks like: # nmap -p 25 mx1.cpanel.net Starting Nmap 6.40 ( http://nmap.org ) at 2021-06-24 13:20 EDT Nmap scan report for mx1.cpanel.net (208.74.121.68) Host is up (0.032s latency). PORT STATE SERVICE 25/tcp open smtp
    We want to see that port listed as open when you perform your test from a remote machine to the server having an issue.
    0
  • Aryup
    Hello cPRex Here is the result of the nmap command you asked nmap -p 8984 domain.com Starting Nmap 7.91 ( https://nmap.org ) at 2021-07-01 10:21 Paris, Madrid (heure d?"t") Nmap scan report for host.name.com (1.2.3.4) Host is up (0.010s latency). PORT STATE SERVICE 8984/tcp closed unknown Nmap done: 1 IP address (1 host up) scanned in 1.01 seconds
    As you see the port 8984 seems closed. Every settings we could think of goes the other way regarding the port 8984.
    0
  • cPRex Jurassic Moderator
    If everything on the server-side seems good, which it does from what you've said, there has to be something external to the machine causing this. This could be on your local network, or something at the hosting level, but it sounds like you won't be able to fix the problem yourself since it's not on the server.
    0
  • Aryup
    Hello, thank you for your answer. So, i'm back to step one, i guess i missed something on our server. Oddly, the port is accessible on a fresh install of cPanel. The port is still accessible after CSF is installed without the port on TCP_IN so i'm starting to loose faith in our system. We will continue to looking forward this issue.
    0
  • cPRex Jurassic Moderator
    So you're saying that after a fresh install, the port works? And then after CSF is installed, it's still working? That's odd to me, since that is not one of the default ports included in the CSF list. If it was working after the initial cPanel installation it sounds like there was another change made that caused the issue. If you have a way to re-trace the steps you performed on another installation with the same provider that could be a helpful test.
    0
  • Aryup
    Hello everyone. Quick update on that issue. We installed a new serveur and the issue went away. To this day we still have no clue of what we could have done wrong to close that port. We are no longer working with that server so that issue become irrelevant. Thank you a lot for the support and for your time!
    0
  • cPRex Jurassic Moderator
    Thanks for following up. I'm glad things are working well for you now, although I don't have a good explanation of the earlier behavior you experienced.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post