Skip to content
English
Go to shippypro.com
  • There are no suggestions because the search field is empty.

How to fix BRT errors

Here's what to do when a known incident prevents you from creating BRT labels.

Are your BRT labels still failing to generate after you retry? Here's what to do if Support confirms a known incident.

Known BRT label-creation incidents and connection-reset errors

You may see a connection-reset message such as cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104.

📌 Note: If Support confirms that your error is part of a known incident, do not assume that your BRT credentials or the recipient's address are incorrect. Follow the incident updates rather than changing these details based on the connection error alone.

Check the ShippyPro Status page for real-time incident updates.

Once resolution is confirmed, you can resume shipping and correct affected orders. Follow How can I fix orders in error? for the correction procedure.

If you need to check whether your error is part of a known incident, or it persists after resolution is confirmed, see How to get in touch with ShippyPro Support Team.

For other BRT errors, consult the BRT troubleshooting guide in Italian.