Skip to main content

SSH - port 22: Operation timed out

Comments

4 comments

  • cPanelAnthony
    Hello! It sounds like you're either using the wrong SSH port or are blocked in the server's firewall. From your local machine, what happens if you install and run nmap to your server's IP address on port 22? Replace the fake IP with your server's IP. Once again, you would run this from the local machine that's having connection issues. nmap 000.000.000.000 -p 22
    0
  • Jonas Everraert
    Hi! I get the following output: [CODE=bash]Starting Nmap 7.92 ( https://nmap.org ) at 2021-12-07 20:24 CET Nmap scan report for server (x.x.x.x) Host is up (0.0076s latency). PORT STATE SERVICE 22/tcp filtered ssh Nmap done: 1 IP address (1 host up) scanned in 0.59 seconds
    0
  • cPanelAnthony
    Hi! I get the following output: [CODE=bash]Starting Nmap 7.92 ( https://nmap.org ) at 2021-12-07 20:24 CET Nmap scan report for server (x.x.x.x) Host is up (0.0076s latency). PORT STATE SERVICE 22/tcp filtered ssh Nmap done: 1 IP address (1 host up) scanned in 0.59 seconds

    This indicates that there is a firewall issue. "filtered" indicates the port is refusing your connection. You should check with your systems administrator, web hosting provider, etc... To see if your IP may be blocked.
    0
  • Jonas Everraert
    This indicates that there is a firewall issue. "filtered" indicates the port is refusing your connection. You should check with your systems administrator, web hosting provider, etc... To see if your IP may be blocked.

    Ok, thank you. I have contacted my hosting provider.
    0

Please sign in to leave a comment.