Skip to main content
C
CIPP5C43
Participant
November 26, 2025
Question

Chrome error when embedding https://secure.na2.adobesign.com in an iframe and redirecting back to ou

  • November 26, 2025
  • 1 reply
  • 547 views

Hi Adobe Sign Support Team,

We are integrating Adobe Sign into our internal web application and would like to confirm whether our current embedded approach is recommended.

At the moment, we are embedding the following URL inside an <iframe> on our site:

https://secure.na2.adobesign.com/xxx

The signing page loads correctly in both Microsoft Edge and Google Chrome, and users can complete and sign the document without any issues.

However, after the signer clicks Submit / Finish and Adobe Sign redirects back to our internal application URL (on a private network, not accessible from the public internet), we see the following error in Chrome:

“The connection is blocked because it was initiated by a public page to connect to devices or servers on your private network. Reload this page to allow the connection.”

In Edge this redirect still works, but in Chrome it is blocked.

Could you please help clarify:

  1. Is it a supported or recommended practice to embed https://secure.na2.adobesign.com/ directly in an iframe for an internal (private network) web application?

  2. Are there any official guidelines or best practices for implementing embedded signing with Adobe Sign when the redirect/return URL is on a private network?

Thank you in advance for your assistance.

Best regards,

1 reply

creative explorer
Community Expert
creative explorerCommunity Expert
Community Expert
November 26, 2025

@CIPP5C43 the issue is very likely the '(on a private network, not accessible from the public internet)' — as it is not recommended or supported. The official documentation strongly encourages using the Adobe Sign API to generate an embedded signing URL and utilizing the JavaScript Widget to load it. The PNA error you're seeing is the direct result of using this non-recommended method in a modern browser environment with private network redirects. 

Your best bet is start here: https://developer.adobe.com/adobesign-api and Acrobat Sign Developer Guide

m
Souvik Sadhu
Community Manager
Souvik SadhuCommunity Manager
Community Manager
November 26, 2025

Hi @CIPP5C43,

 

Hope you are doing well. 

 

Adding to the comments by creative explorer,

 

The error you see is not coming from Acrobat Sign, but from Chrome’s new “Private Network Access” security checks. Chrome is blocking a navigation from a public origin (https://adobe.ly/3KokfaU) to a private-network URL (your internal app). 

The reference tag components are here: https://adobe.ly/4iqrU59

 

Now, answering your questions:

1. Embedding using <iframe>:

  • Yes, embedded signing is a supported scenario in Acrobat Sign, and many customers embed Sign pages or widgets in their own applications.

  • At the account/group level, there is a security setting called “Prevent Adobe Acrobat Sign from being embedded in third-party websites.” If enabled, this setting can block iframes. If it’s disabled or your domain is allow-listed, embedding is allowed. Info here: https://adobe.ly/3XmZ242

2. This change was introduced by Google Chrome with version 97 back in 2021. You can find the trail here: https://adobe.ly/3M30R3E

 

Now, that being said, here's a suggestion that might work for you:

  1. Start the signing process from your internal app via Acrobat Sign REST APIs. You can take this help page as a reference: https://adobe.ly/44yEklz

  2. Open the signing URL (in an iframe or a new tab).

  3. When the signer finishes, rely on either:

    • Acrobat Sign webhooks to your back-end, or

    • Periodic status checks using the agreements API from your server.

  4. Your UI can poll your own back-end to know when the agreement is signed and update the page accordingly, without needing Sign to redirect back into the intranet.

Again, this keeps Chrome out of the “public → private” decision path.

 

Hope this helps. 

 

Regards,
Souvik.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices