Skip to main content
D
default26816018t2yiwx
Participant
October 27, 2022
Answered

"Connection Error - could not connect to the authorization server"

  • October 27, 2022
  • 1 reply
  • 474 views

ADE suddenly stopped connecting to the authorization server (one day working fine, next day not), and I am now unable to return any of my library books.

 

I've read through MANY articles and forum posts, but most are years old and that might be why the suggested fixes didn't work.

 

  • My machine is Win10 (completely up-to-date)
  • I have full internet access (it's what I'm using right now), so connectivity should not be the issue.
  • I've tried turning off my anti-virus and firewalls to see if that was blocking something. 
  • I deauthorized ADE v.3 but couldn't re-authorize so I tried upgrading to v.4.5 which made no difference. 

 

Can anyone from Adobe give us some idea as to how the authorization process works so that we can at least have some idea what might be causing this issue?  I understand this is freeware but my local library only allows for downloads to ADE so there's no alternative.

 

Any help gratefully received!

    This topic has been closed for replies.
    Correct answer default26816018t2yiwx

    So, I've got it working again.

     

    In case anyone else has the same problem... I rebooted my fibre broadband modem and hub. Even though I had no other internet connectivity issues, this did the trick for me. Perhaps the connection to the authorization server works on a different protocol or something (I'm not a networks person, idk)?

     

    Anyway - go figure, switching it off and on again worked ;o)

    1 reply

    D
    default26816018t2yiwxAuthorCorrect answer
    Participant
    October 28, 2022

    So, I've got it working again.

     

    In case anyone else has the same problem... I rebooted my fibre broadband modem and hub. Even though I had no other internet connectivity issues, this did the trick for me. Perhaps the connection to the authorization server works on a different protocol or something (I'm not a networks person, idk)?

     

    Anyway - go figure, switching it off and on again worked ;o)

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