Skip to content

Troubleshooting

  1. Check the container is running: docker ps --filter name=acme-connector.

  2. Check its health: curl http://localhost:8080/healthz. It should reply ok.

  3. Check the logs for errors:

    Terminal window
    docker logs acme-connector --tail 50
  4. Make sure the host can reach Acme. See Test connectivity.

Message in the logs Cause Fix
enrollment token invalid The token was mistyped or already used. Create a new connector in the portal and use its token.
region mismatch ACME_REGION does not match your organisation. Set ACME_REGION to the region you chose at sign-up.
tls handshake failed A proxy or firewall is inspecting traffic. Exclude connect.acme-service.example from TLS inspection.
connection timed out Outbound port 443 is blocked. Allow the addresses or set ACME_PROXY_URL.
  • Check the host name and port.
  • Check the connector host can reach the data source. A firewall between them is the most common cause.
  • Check the read-only account and password are correct.
  • Check the Entity ID and Reply URL match exactly, including your organisation ID.
  • Check the user’s email in your IdP matches their email in Acme.
  • Sign in with an Owner account that uses a password to review the SSO settings.
Problem Cause Fix
A wiper never shows as Reporting The wiper cannot reach the connector. Check TCP 8883 is open from the wiper to the connector host and that port 8883 is published in your connector settings.
The pairing code is rejected The code expired or was already used. Select Generate pairing code again and enter the new code.
A wiper shows Learning for a long time Acme needs about 14 days of data. Wait, and check the wiper keeps reporting. Gaps in reports extend the learning period.
No alert emails arrive No recipients are set, or emails are filtered. Check Features > Window Wiper Insight > Alerts and allow mail from support@acme-service.example.

See Window Wiper Insight for setup steps.