Fix Acrobat Sign 500 or 502 Errors When Sending E-Signatures
Question details
Users are unable to send documents for electronic signature because the application or web browser displays a 500 or 502 server error.

- Product
- Acrobat Sign
- Device & OS
- not provided
- Scenario
- Attempting to send a document for e-signature using the desktop app, mobile app, or web browser.
- Observed behavior
- The process fails and a 500 or 502 error message appears, typically indicating a temporary backend service outage.
Ensure your device has a stable internet connection and visit the official system status page of your software provider to check for any ongoing global server outages.
Wait for Service Restoration and Retry
Since 500 and 502 errors typically indicate a temporary server-side service outage, waiting a short period before trying again is the most effective approach.
A 500 (Internal Server Error) or 502 (Bad Gateway) error means that the software's backend servers are temporarily unable to process your request. This is rarely an issue with your local application or device.
Visit the official Adobe System Status webpage to verify if Acrobat Sign is currently experiencing a known outage.
Wait for 15 to 30 minutes, then refresh your web browser or restart your Acrobat Sign desktop/mobile application.
Once the application has reconnected to the server, select your document and try sending the e-signature request again.

Capture the Error and Contact Support
If the system status shows no outages but you continue to experience the 500 or 502 error after waiting, you should document the issue and contact technical support.
Sign and Share PDFs Seamlessly with WPS Office
If your current e-signature platform is experiencing server downtime, you can use WPS Office's robust built-in PDF tools to sign your documents locally and share them without relying on external web servers.
- 1. Open your PDF: Launch WPS Office and open the PDF document that needs to be signed.
- 2. Access signature tools: Navigate to the 'Insert' or 'Protect' tab in the top ribbon and click on the 'PDF Signature' button.
- 3. Create your signature: Draw, type, or import an image of your signature, then place it in the appropriate field within the document.
- 4. Save and share: Save the signed PDF to your local drive and instantly share it with your recipients as an email attachment directly from WPS Office.

Frequently Asked Questions
What does a 502 error mean when sending an e-signature?
A 502 Bad Gateway error usually indicates that one internet server received an invalid response from another. In the context of e-signature applications, it means the platform's backend servers are temporarily failing to communicate, usually due to high traffic or maintenance.
Will I lose my document if a 500 error occurs while sending?
No, your document drafts and templates are typically saved safely in your account cache or local storage. Once the server connection is fully restored, you can resume your workflow without losing the document.
Can I bypass a 500 server error by clearing my browser cache?
Clearing your browser cache can occasionally resolve local loading issues, but 500 and 502 errors are almost always caused by problems on the provider's servers. You generally have to wait for the provider to fix the outage on their end.
Are there ways to sign documents offline when servers are down?
Yes. While cloud-based e-signature requests require an active server connection, you can use desktop applications like WPS Office to open the PDF, apply a digital signature locally, and send it via email once your internet connection is available.




