Check whether a TCP listener can be reached from your Blesta monitoring server using PD Uptime & Status Pro. This helps distinguish a reachable website from a separate mail, database or control-panel port that is not answering.

Select the intended listener

Choose a hostname and the exact TCP port for a service you administer. Check that the monitoring server is expected to reach it; a private or firewalled database may deliberately refuse this connection.

A port connection is a narrow availability check. It does not sign in, run a database query, send a message or prove the application completed a useful transaction. Pair it with the application’s appropriate operational checks when those outcomes matter.

Add the monitor

1. Confirm Pro is active and open PD Modules → Uptime → Monitors → Add a monitor.
2. Enter What is it with a clear label for the listener.
3. Select the TCP port option under What to check.
4. Enter Address and the intended Port number.
5. Review the optional Whose service is it association, then choose Add monitor.

The port must be between 1 and 65535. Use the separate Port field rather than relying on a URL to supply it. Do not expose a previously private service to the public Internet merely to make a monitoring result green.

Check the observed result

Review State, Checked and the recorded reason after the next eligible round. A successful probe opens the connection and closes it. A timeout or refused connection can reflect routing or firewall policy between the monitoring server and target, rather than a failure visible to every customer.

Check Failed checks before it counts as down and alert recipients before expecting a confirmed incident notification. Do not share database credentials or private endpoint details unnecessarily.

See the PD Uptime & Status Blesta guide for related tasks, or explore PD Uptime & Status.