Skip to main content
Inspiring
February 13, 2019

P: No network connection, works in Classic

  • February 13, 2019
  • 18 replies
  • 2142 views

I'm using the latest Lightroom CC 2.1.1.    On my MacBook Pro 2018 running Mojave (latest), when running Lightroom CC it constantly displays "No network connection" and the cloud icon has an X through it.     Sometime it will start working for a short period and then disconnect again.  
  When using Lightroom CC Classic I have no issues connecting from the same laptop.   I tried different WIFI networks and all have the same behavior, so I don't think it's something specific with the Internet connection.   My iPhone and iPad both running LR CC can connect just fine on the same network.  I'm able to access Lightroom web using Safari without issues and checked the SSL certificates on my laptop.  I have both IPv4 and IPv6 setup on my home network.   Is it possible to find out more information to get some error message to why it is unable to connect?    I'm located in the US (no country-based firewall) and using Comcast Xfinity as my provider.  

 

I really want to migrate from Lightroom classic CC to the cloud based CC solution, but this is holding me up as a showstopper.   

 

Any help would be appreciated.

This topic has been closed for replies.

18 replies

Participating Frequently
April 11, 2022

Rick,

I am having this same issue as Christian but I' m not nearly as smart. Has there been a solution for this issued yet? I've tried removing and reinstalling and this hasn't helped one bit. While I have used mt personal MacBook at my work office before I don't do this often. No issues with any other Adobe app other than this but this is the one that I need the most. It does see  to work by the way on my iPhone 13 Pro.

 

Steve

Participating Frequently
June 2, 2021

Having the same problem on a 4 month old Mac Mini. This will soon be a three year old thread so why is it still an issue? The odd thing is that Photoshop and I assume all my other apps works fine. I moved the Apple photo library to an external SSD and was trying to reconnect Lightroom to the new location. It wasn't working so I uninstalled Lightroom and reinstalled it with the assumption that I could reset it during install. Nope. The only reason that I'm paying the monthly Adobe fee is because I really like the way I can organize photos in Lightroom. If I lose that, I'll abandon Adobe. Lightroom works fine from my Windows computer at work. Is this an Apple problem? Shall I abandon Apple?

Inspiring
August 18, 2020
Having the same problem. This seems to be a two year old thread so why is it still an issue?
Inspiring
August 13, 2020
I just switched to cc and am experiencing the same periodic disconnect with a local drive. Is there a solution yet?
selondon
Community Expert
Community Expert
May 9, 2020
I am having the same issue, already reported to the Lightroom team. I don’t use a NAS.
Inspiring
April 18, 2020
I have this issue too, but what do I do to fix it? Lightroom does not work, but Lightroom CC does work.
Participating Frequently
February 16, 2020
Any feedback from Adobe tech support team for this issue and this SSL certificate found by @808531 Lambert? Since DAYS I have this 'unable to connect to the server' error message and are no longer able to upload files to the cloud. I am fully frustrating and I am about to cancel my Adobe subscription and start looking for some Adobe`s competitors' solution.

Thanks

Inspiring
December 11, 2019
How do I install this certificate.. I just started having this problem.. 
onyxreal2Author
Inspiring
March 10, 2019
My company provided me the proxy SSL certificate files, is there a folder on the Mac where I can add those certificates so that the Lightroom application uses them?  Or the trust-store cannot be changed? 

Thanks,
Christian
onyxreal2Author
Inspiring
February 20, 2019
Thanks, I'm wondering why the Lightroom Classic does not see the issue?  Is it using the system-wide SSL certificate store maybe and it was done differently in Lightroom CC?   Any update if this will be fixed in the next release?

Thanks,
Christian