Server Troubleshooting Guide

Moesif server integrations can usually be installed in 15 minutes or less. If you don’t see your data show up in Moesif or experience issues, we recommend the following steps.

Enable Debug Mode

To assist debug, review your specific server integration docs on how to enable debug mode. The debug option that can be leveraged to print additional troubleshooting context into your application’s log output. Once collected, debug logs could be submitted to Moesif Support

For example, debug can be set to true for the Node.js SDK:

var options = {

  applicationId: 'Your Moesif Application Id',
  debug: true, // Enable debug mode

// 3. Initialize the middleware object with options
var moesifMiddleware = moesif(options);

Ensure Moesif is the last middleware

If you are using a Moesif SDK, you must ensure Moesif is initialized last in your “middleware stack”. The Moesif middleware should come after any authentication or authorization middleware you have. This ensures the Moesif middleware can read the identified user or identified company correctly. You should also ensure Moesif comes after any body parsers or decompression middleware you have.

Check presence of conflicting middleware

If you’re using a Moesif server SDK and already have other monitoring libraries, the two can conflict due to the way both instruments your application. This can especially happen if you have a custom exception handler or importing a commercial Application Performance Monitoring library. First, try to find the conflicting middleware by removing it or reordering it relative to the Moesif middleware. If the conflicting middleware is a commercial product, let our support team know and the version of the conflicting middleware.

Restart Server

If you are using an API gateway plugin, it may require the instance to be restarted. Try restarting the server first.

Verify Network Connectivity

From your container or virtual machine, verify if it can connect to Moesif Collector API by executing a simple curl command curl -XGET "" and receiving a 200 OK response. If not, there might be an issue connecting to the Moesif such as due to local firewall settings (See below).

Network Firewall Whitelist

Ensure the Moesif Collector API,, is whitelisted to your outgoing firewall rules.

While whitelisting via the domain is recommended, you can whitelist and for outgoing traffic if you’re unable to do so.

Relevant information that could be supplied to Moesif

If you still experience persistent integration & connectivity issues, please collect the below details and supply them to Moesif for further investigation into the root cause.

  • Moesif server integration and version
  • Programming language version
  • Web Framework or API gateway version
  • Operating System and/or cloud provider
  • Sample request made against your API including headers and body