ContactSign in
← All documentationSearch guides

Diagnose ERR_CONNECTION_REFUSED

A refused connection concerns listeners or transport, not a bad password.

  • Administrator
  • Intermediate
  • 1 min read
  • Reference: 101.18.15
  • Reviewed

Before you begin

Exact address, protocol, port and provider console.

Use the controls offered by your installed version and account permissions. This guide describes the workflow; it does not grant additional access.

Follow the steps

  1. Confirm the IP is the intended installed server.
  2. Use protocol and port printed by the installer.
  3. Inspect web-service state and listening ports through trusted root access.
  4. Review configuration errors and firewall/provider rules before changing anything.
  5. Retest the same URL after a targeted correction.
Server terminal · read-only
systemctl status apache2 --no-pager
ss -ltn

Read-only administrator checks. Inspect output privately; do not post raw logs containing secrets.

Check the result

The login responds at its intended endpoint.

If something goes wrong

A downloaded installer does not prove Apache is listening. Do not expose unrelated ports or disable the entire firewall.

Prepare useful details for support