Skip to content

My port monitor is down but the service works

Your mail client connects, or you can sign in over SSH, yet the port monitor says Down. Two of our checking places agreed that the port did not answer as the monitor expects. On port 22 (SSH), only Newark checks, so it was Newark 3 times in a row. Work through these in order.

1. Read the last result

Open the monitor and unfold Last result. The result names what went wrong, and What our checks saw at the top of the page says what probably happened and what you can try. Every result: what the results mean.

2. A firewall lets only some addresses in

No answer from the port means the connection got no answer within 10 seconds: a firewall that drops connections from addresses it does not know looks exactly like this. If the port works from your office or your home but not for us, allow our checks on that port, IPv4 and IPv6. Then press Check again now on the monitor's page to see the result at once.

A tool that bans addresses after connections that never sign in, such as fail2ban, can ban our checking servers too, since we connect and never sign in. Add our addresses to its list of addresses it never bans.

3. The service listens only inside the server

Port closed means the server refuses connections on this port. A service that listens only on the server itself, or on a private network, works for programs on that server and is closed for everyone else. Let it listen on the server's public address, or watch the port it does publish.

4. The greeting does not match

Answers, but not as a mail server should: 421 ... shows the first line the service said. A 421 usually means the service is busy or refusing work; its logs say why. If another kind of service runs on this port, choose its greeting in the monitor's Settings, or None: connect only (greetings).

Connects, but the service says nothing means no first line came within 5 seconds. Web servers, search engines and control panels never speak first: choose None: connect only for them.

5. The port expects TLS, or does not

No secure connection on this port means the port is one where the service speaks TLS from the first byte (465, 993, 995 and 990), but this service does not. Check that you watch the TLS port, such as 993 rather than 143 (ports we check).

6. The name or the address

Server name not found means the name has no address: check the spelling under Server address, and that the name still points to the server. If the name has an IPv6 address, the service must listen on it too, since we may connect over either.

Still stuck

Tell us the monitor's server address, the port and the time it shows.