Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

51108: Twilsock: Service instance disabled


ERROR: 51108

error-51108 page anchor
ERROR

Twilsock could not connect because the Service instance you requested is disabled. This usually means the SID or configuration your client is using points to a Service instance that is no longer active for the Twilio product you are trying to reach.

Possible causes

possible-causes page anchor
  • The client is configured with a disabled Service instance SID.
  • The Service instance was disabled in Console or through an API update.
  • Your application is using an outdated configuration value from a previous environment, such as development or staging.
  • The access token or client configuration points to a different Service instance than the one you intended to use.
  • Confirm that your application is using the correct Service instance SID for the environment you want to access.
  • Check the status of the Service instance in Twilio Console and make sure it is active.
  • If the Service instance was intentionally disabled, update your application to use an active Service instance instead.
  • Review your deployment configuration and token generation flow to make sure they reference the correct Twilio Service instance.
  • If you no longer need the disabled Service instance, create or select an active one and update all client-side and server-side configuration values that reference it.

Additional resources

additional-resources page anchor