If a secure signing link throws an error, fails to load, or appears broken, the issue is almost always caused by local security software, browser incompatibility, or an outdated email application cutting the secure link in half.

🛠️ Follow this step-by-step troubleshooting checklist to resolve the issue.

1. Disable VPNs, Proxies, and Remote Desktop Tools

Are you using a corporate VPN, a proxy server, or a remote desktop environment (like Citrix or Remote Desktop)?

• The Problem: Verified uses advanced, real-time security protocols to authenticate digital signatures. Corporate firewalls and VPNs often flag these secure handshakes as suspicious and block the connection entirely.

• The Fix: Temporarily disconnect from your VPN or remote desktop, close your browser, and click the link again using your standard internet connection.

2. Check for "Truncated" Links in Older Email Clients

Are you using an older desktop email application, such as Outlook 2007 or legacy corporate mail clients?

• The Problem: To ensure absolute cryptographic security, Verified utilizes long, complex security tokens in its URLs. Legacy versions of Outlook cannot handle long web addresses and will literally cut the link in half, rendering it useless.

• The Fix:

  • Carefully copy the entire link text from the email and paste it directly into your browser's address bar.

  • Alternatively, open your email using a web browser (Outlook Webmail / Office 365) or access the invitation link via a mobile device.

3. Switch to a Supported Web Browser

Your web browser might be running outdated security scripts, or it may have extensions installed that block the platform's signing scripts.

• The Fix: Try copying the signing link and opening it in the latest version of a universally supported browser: Google Chrome, Microsoft Edge, Mozilla Firefox, or Apple Safari.

4. Verify the Document Integrity (For Senders)

If you are the sender and multiple recipients report that the link is crashing or throwing a document error, the problem might lie with the underlying file structure.

• The Problem: Older PDF formats, heavily encrypted files, or PDFs containing active, fillable form fields can cause the signing engine to fail.

• The Fix: Before launching a new envelope, ensure the document is completely static. If needed, run the file through an online PDF validator or "flatten" the document using your system's Print to PDF feature to clear out hidden metadata constraints.