Can't verify subscription status

[clarrysf]

I'm connected to the internet. No connection problems with anything else, only with Adobe.

Can't access Lightroom Classic or Acrobat DC.

Responses received:

1) We can't verify your subscription status.

2) We can't reach Adobe servers.

This problem reoccurs. I've had lengthy online chats with Adobe technical staff and somehow they fix it. Then when I try it on another occasion, the same thing happens again.

HELP!

[Todd Kelgard]

Same exact thing happening to me. Tried the same remedies, but no luck. Crazy frustrating.

[tanayshrivastav]

I am currently having the same problem. I believe that it is a problem on Adobe's end.

[DrLoveys]

agree -  they had me go into credential manager on windows and remove anything that says adobe but am I supposed to do this each and every time?  It only happens on one computer - not all my computers. 

[DrLoveys]

logging out of creative cloud and then back in and then opening app works.... sometimes 🙂

[compupix]

"We can’t verify your subscription status.We can’t reach the Adobe servers. This may be because you’re not connected to the internet. Check your connection and try again below. If you’re still having issues, please see our connectivity troubleshooting guide."

The troubleshoting guide didnt help.

I am logged in wth Creative Cloud Desktop.

There's no problem with my Internet connection.

Details:

My old computer died. I am loading all of my data, software, and settings over to a new comuter.

My old computer I had a couple of different versions of Bridge CC loaded without any verification issues. I've never had the current version before.

(A couple more days of this and I might start looking for that old app PTFB.)

The only solution that I can think of is to load an old version Bridge, see if it works. Right now, I have higher priorities.

Thanks!

[David__B · Accepted solution]

If you're using Windows 7 this may help: https://community.adobe.com/t5/download-install/win-7-users-getting-error-p206-unable-to-reach-adobe...

[gangeek]

i had same problem. i am running windows 7.

i added two keys into the registry and it worked. i will post these solutions if anyone is intersted, just reply here and when i see it i will post the info. 

[Studmi]

Would love to see these registry fixes please.

Am going round in circles here, and tried everything else Adobe has suggested, but still no fix.

Thanks

[Marie Leary]

Gangeek, please post solutions.Thanks.

[SusannahQ]

I'm also having the same issue, but on a Mac. I've tried changing the clock, signed out, closed everything down, re-signed in, etc and nothing has worked so far. I moved house and basically ever since (even though my internet is working) I keep getting the error. 

[Jarek G]

I have the same problem with my CC subsribtion using computer with Windows 10. My Internet connection is very good. This hapen once before but was solved by Adobe. This time I have no any valid help, just waisting all day and getting in trouble not reaching the deadline for assignment. Frustrated? Yes, very.

[Stefan25032081e2lq]

I can't believe that here it is now almost July of 2022 and this sh*t is still happening with no fix from Adobe. Used Acrobat on Saturday and now getting a 'can't verify your subscription' error. FIX THIS, ADOBE!

[gangeek]

My apologies that this reply is so late. I did not check back in here after getting this to work many months ago.

Although it is late now, I will still post the solution I used in case someone else runs into this problems.

And keep in mind I am running Windows 7 64-bit still, so I am unsure if this works for any other OS but it is worth a try. Here is solution:

Enable TLS 1.1 and 1.2 on Windows 7 at the SChannel component level
Per the TLS-SSL Settings article, for TLS 1.1 and 1.2 to be enabled and negotiated on Windows 7, you MUST create the "DisabledByDefault" entry in the appropriate subkey (Client) and set it to "0". These subkeys will not be created in the registry since these protocols are disabled by default.

Create the necessary subkeys for TLS 1.1 and 1.2; create the DisabledByDefault DWORD values and set it to 0 in the following locations:

For TLS 1.1
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client
DWORD name: DisabledByDefault
DWORD value: 0

For TLS 1.2
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
DWORD name: DisabledByDefault
DWORD value: 0