Skip to main content

Gateway Troubleshooting

Verification Needed

This section covers anticipated gateway troubleshooting scenarios. Details may change — verify with eCourtDate support.

This guide covers common issues you may encounter when configuring and using gateways in eCourtDate.

SMTP Gateway Issues​

Connection Refused​

  • Cause: The SMTP host or port is incorrect, or the server is not accepting connections.
  • Solution: Verify the SMTP host and port in your gateway configuration. Common ports are 25, 465 (SSL), and 587 (TLS). Ensure your network or firewall allows outbound connections on the configured port.

Authentication Failed​

  • Cause: The SMTP username or password is incorrect.
  • Solution: Double-check your SMTP credentials. Some providers require app-specific passwords or have separate SMTP credentials.

TLS/SSL Errors​

  • Cause: The encryption setting does not match what the SMTP server expects.
  • Solution: Verify the encryption setting (TLS, SSL, or None) matches your SMTP server's requirements. Port 587 typically uses STARTTLS, and port 465 typically uses implicit SSL.

Twilio Gateway Issues​

Invalid Credentials​

  • Cause: The Twilio Account SID or Auth Token is incorrect.
  • Solution: Verify your Account SID and Auth Token in the Twilio Console. Ensure you are using the correct credentials for your account (not test credentials unless intended).

Number Not Verified​

  • Cause: The sending phone number is not verified or approved in your Twilio account.
  • Solution: Ensure the phone number is active and properly configured in your Twilio account. For trial accounts, the recipient number must also be verified.

Rate Limits​

  • Cause: Too many messages are being sent in a short period.
  • Solution: Review Twilio's rate limits for your account type. Consider upgrading your Twilio plan or implementing message queuing to stay within limits.

Custom Gateway Issues​

Endpoint Unreachable​

  • Cause: eCourtDate cannot reach your custom gateway endpoint.
  • Solution: Verify the endpoint URL is correct and publicly accessible. Check that your server is running and not blocked by a firewall.

Timeout​

  • Cause: Your endpoint takes too long to respond.
  • Solution: Ensure your endpoint responds within the expected timeout window. Consider processing messages asynchronously — acknowledge the request immediately with HTTP 200 and process the message in the background.

Invalid Response Format​

  • Cause: Your endpoint returns an unexpected status code or response body.
  • Solution: Ensure your endpoint returns an HTTP 200 status code to acknowledge receipt. Check your server logs for errors during request processing.

General Tips​

  • Check the gateway status in the eCourtDate Console for error messages and delivery logs.
  • Test your gateway configuration with a single message before enabling it for bulk delivery.
  • Ensure all credentials and endpoints are current and have not expired or been rotated.

Contact Support​

For all gateway issues that cannot be resolved through the steps above, contact eCourtDate support at help@ecourtdate.com.