Skip to main content

Common Issues and Solutions

Webhook Not Being Received

Verify your webhook is properly configured and enabled:
Common issues:
  • isEnabled: false - Webhook is disabled
  • Empty events array - No events configured
  • Invalid URL format - Must be valid HTTPS URL
  • Missing or incorrect headers
Test if your webhook endpoint is reachable:
Requirements:
  • Must use HTTPS (not HTTP)
  • Must respond within 10 seconds
  • Must return HTTP 2xx for success
  • No redirects (301/302) allowed
Ensure the events you’re expecting are actually occurring:
Verify:
  • Events are occurring in your community
  • Event names match exactly (case-sensitive)
  • User actions are completing successfully

Authentication Failures

Nudj sends custom headers that your endpoint must verify:
Common mistakes:
  • Case sensitivity in header names
  • Missing Bearer prefix
  • Wrong environment variable
  • Headers not configured in webhook settings
Ensure your secrets are properly configured:
Best practices:
  • Use different secrets for development/production
  • Never commit secrets to version control
  • Use a secure secret generator
  • Rotate secrets regularly

Processing Errors

Webhooks must respond within 10 seconds:
Optimize webhook processing for high throughput:
Handle malformed webhook payloads gracefully:

Debugging Techniques

Enable Detailed Logging

Request Inspection Tools

Webhook Testing Tools

Error Monitoring and Alerting

Webhook Health Checks

Error Notifications

Performance Optimization

Async Processing

Caching Strategies

Testing and Validation

Integration Testing

Common Solutions

Network and Connectivity

Ensure your firewall allows incoming HTTPS traffic:
Configure your load balancer for webhook traffic:
  • Enable session affinity if needed
  • Set appropriate timeout values (>10 seconds)
  • Configure health checks
  • Ensure SSL termination is properly configured
Verify your domain configuration:

Getting Help

Check the Logs

Start by examining your application logs and webhook processing logs for error patterns.

Test Locally

Use ngrok or similar tools to test webhooks against your local development environment.

Verify Configuration

Double-check your webhook configuration using the Admin API endpoints.

Contact Support

Reach out to support@nudj.cx with specific error messages and webhook IDs.
When contacting support, please include:
  • Webhook configuration (without secrets)
  • Specific error messages and stack traces
  • Webhook IDs that failed
  • Timeline of when issues started
  • Your endpoint URL (for connectivity testing)

Debugging Checklist

1

Verify Webhook Configuration

  • Webhook is enabled (isEnabled: true)
  • Events array contains expected event types
  • URL is valid and reachable
  • HTTP method is appropriate
  • Headers are correctly configured
2

Check Endpoint Implementation

  • Endpoint responds within 10 seconds
  • Returns HTTP 2xx for successful processing
  • Properly verifies webhook signatures
  • Handles JSON parsing errors
  • Implements idempotency
3

Test Network Connectivity

  • Endpoint is accessible from external networks
  • SSL certificate is valid
  • Firewall allows HTTPS traffic
  • DNS resolves correctly
4

Monitor and Log

  • Comprehensive logging is enabled
  • Error monitoring is configured
  • Health checks are implemented
  • Metrics are being tracked
Still having issues? Check our Implementation Guide or review the Event Catalog to ensure you’re handling webhooks correctly.