Copy link to clipboard
Copied
Hi all
I've been wanting to send documents for signature and can't seem to have access to the send for signature.
It says that the requests to the servers have been blocked by an extension.
If the system is down, do we have an idea when it might return to normal?
Thanks
Hello,
A potential issue was identified and fix has been deployed. Please let us know if you still face the same issue.
Thanks
Sameer Puri
Copy link to clipboard
Copied
Same here. Only impacts Chrome right now. But this is new behavior today and no extensions or settings have changed on my end. Very frustrating. This rollout to the new UI has gone poorly. At least they brought back the option to see signature documents in the old esign formatted view. But now all documents are blocked with this new error.
I can get it to work for awhile but then it always results in this same problem after it times out.
Copy link to clipboard
Copied
Thank you for sharing your experience Jeff. The signature program is still unavailable for me!
I hope this gets fixed asap as some of my clients are waiting to sign their contracts to move forward.
Copy link to clipboard
Copied
Catherine - Try different browsers and private/incognito mode and see if that helps.
Copy link to clipboard
Copied
Adobe-
Here is the error that is being thrown in Chrome. It happens after the credentials timeout. And instead of reestablishing the credentials or asking for sign on, it throws a error stating that an app is blocking the server requests.
These has been happening the past two days but was fine prior to that.
No changes on my end.
Here is the error:
Copy link to clipboard
Copied
Having the same problems. I MUST get documents out to our clients to sign. I haven't changed anything either. Adobe, I am so incredibly disappointed.
Copy link to clipboard
Copied
Hello,
A potential issue was identified and fix has been deployed. Please let us know if you still face the same issue.
Thanks
Sameer Puri
Copy link to clipboard
Copied
Thanks, Sameer. So far it looks better. Will let it time out for a longer time and see how it behaves.
Jeff
Copy link to clipboard
Copied
I was premature. Once it fully timed out I see the exact same behavior. Popup asks if I want to reload. When I do I end up with the gray "server request blocked"
Copy link to clipboard
Copied
Hi Sameer and Jeff
Thank you for sending the fixing team on this. I have just sent a document for signature with Chrome and it worked very well.
I had to disconnect and log in again into my account for it to work, so if you haven't tried this Jeff, it might help.
Copy link to clipboard
Copied
Thanks for confirming Catherine. Jeff, can you please log back in to your account and check if you are still impacted by the issue? We will take a look again, upon your confirmation.
Thanks
Sameer Puri
Copy link to clipboard
Copied
Hi Sameer
The same happened to me after the session timed out, it wasn't working anymore. I have to log out and back into my account to make it work again
Copy link to clipboard
Copied
Yes, my original problem is the same thing that Catherine is now experiencing. Some people were completely prevented from logging in. I never had that problem. But I continue to have the problem where the page loads fine but as soon as it times out it will never refresh/reload properly. I have to close out the window and start a new one.
Copy link to clipboard
Copied
Here is what it looks like on timeout:
And then upon clicking ok to reload (or just a browser refresh):
Still throwing this security exception error:
Which appears to be caused by a bad meta tag:
Copy link to clipboard
Copied
Hello Jeff,
Are those recent screenshots? Are you still facing the same issue? Please confirm so that we can start debugging the issue at the earliest.
Thanks
Sameer Puri
Copy link to clipboard
Copied
Yes! I took them right when I composed the reply. This is using the latest Chrome release on a MacBook Pro running OSX Mojave. I had the same exact issue in Incognito with all of my apps disabled.
Copy link to clipboard
Copied
Hello Jeff,
Thanks for the prompt reply. This look like a different issue than the one that was originally reported since this occurs only after the session times out. The original issue reported in the thread would occur even without the session timeout, and the fix that we deployed yesterday should have fixed that.
Please confirm if the understanding is correct. We will then start looking at this refresh upon session timeout issue.
Thanks
Sameer Puri
Copy link to clipboard
Copied
Very well could be. I was never completely prevented from signing on. My issue has always been the reload/refresh that doesn't work and requires a new window.
Started happening last Thursday I believe.
Copy link to clipboard
Copied
Just to confirm, reload/refresh upon session timeout, correct? Or do you see this issue even if your session hasn't timed out yet?
Thanks
Sameer Puri
Copy link to clipboard
Copied
Only upon timeout. Until I've seen the first screenshot above, everything works fine and I can refresh, change pages, view, etc.
After timeout, I can see documents but can't click on them. And the signature stuff always has the large grey server request blocked image.
Copy link to clipboard
Copied
I continue to have the problem. Yesterday tech support tried to convince me my password had expired. We went through all the resetting, logged out and back in, etc. I sent 2 documents within minutes of each other and now it's down again on Chrome.
Same message as the above screen shot, frown face, being blocked by an extension. I closed and tried in a new tab, it worked but apparently as others have mentioned after a while it no longer works, I haven't got the timed out reload message, just the Chrome frown face.
This is ridiculous.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now