# 63001: Channel authentication failed. See Channel-specific error for details

Log Type: CARRIER

Log Level: ERROR

## Description

Twilio returns this error when a non-SMS messaging channel cannot authenticate your request with the underlying channel provider. Check the channel-specific failure details in `ChannelStatusMessage` or in your `StatusCallback` request to identify why the provider rejected authentication.

### Possible causes

* The channel authentication credentials are incorrect or no longer valid.
* Facebook identified a potential security issue and rotated the token used for the sender.
* The Facebook user who connected the Facebook Page to Twilio changed their password.
* The user de-authorized the Twilio app.
* Re-authentication can also fail if the account used for setup no longer has admin access to the Facebook Page.

### Possible solutions

* Review `ChannelStatusMessage` in your message status callback to see the error returned by the underlying channel.
* Reconnect Facebook Messenger in Console and authorize the Facebook Page again. During setup, connect with Facebook and select the Facebook Pages you want to authorize as Senders.
* Make sure the Facebook account you use to reconnect has admin access to the Facebook Page.
* If Facebook rotated the token, the connected user changed their password, or the app was de-authorized, re-authenticate the sender. If the issue continues, delete the sender and add it again.
* Review your Programmable Messaging logs for the affected Message SID while you troubleshoot.

#### Additional resources

* [Get started with Facebook Messenger (public beta)](/docs/messaging/channels/facebook-messenger)
* [Send a message with Facebook Messenger (public beta)](/docs/messaging/tutorials/send-message-with-facebook-messenger)
* [Debugging Tools for Programmable Messaging](/docs/messaging/guides/debugging-tools)