The Creative Cloud desktop application has a problem with WPAD automatic proxy detection. When the computer is configured to "automatically detect settings", the Creative Cloud application will not load the Apps list, giving the error "Download Error. Unable to reach Adobe servers. Please check your internet connectivity, firewall settings, and then try again." All other elements of the Creative Cloud application (logging in, accepting terms of use, the "Home", "Files", "Fonts" and "Behance" tabs have no issues using the automatically detected settings). I can refresh a netstat on the command line and see that the Creative Cloud application tries to make direct calls to the EC2 servers when attempting to connect to the "Apps" list instead of using the proxy.
If I manually configure a PAC file or manually configure the proxy on the computer, the Creative Cloud can connect successfully. The failure only occurs with "automatic detect settings". I have tested different WPAD server configurations, to include Apache on Unix, IIS7 on Windows, text/plain and application/x-ns-proxy-autoconfig MIME types, and CNAME vs A record for 'wpad'. Creative Cloud continues to fail to operate correctly.
The old version of Adobe Application Manager can successfully connect and download updates using "automatic detect settings". It will update itself (and installed apps) successfully. After it updates itself, it will connect and update itself a second time, this time replacing itself with the Creative Cloud application, which fails to connect. This behaviour is new to the Adobe Application Manager once it becomes the Creative Cloud application.
It seems from what "official" documentation I can find that this is currently "broken as designed" (see Adobe references at bottom of post). Connecting directly from a client to the internet without a proxy is prohibited by our information security policy (the chat support agent tried to tell me 3 times that the "solution" was to disable the proxy and open ports 80 and 443 to the internet). Manually configuring the proxy through a PAC file or manually setting proxy information causes other issues and performance problems (I strongly disagree with Adobe staff member Jeff Wright's assertion that automatically detecting the settings is "a common issue with most applications"--see reference at bottom of post).
While I could technically open the firewall or manually configure the proxy to make the Creative Cloud function properly, these are unacceptable workarounds as already stated. Considering that the previous iteration (Adobe Application Manager) functioned just fine with automatically detected settings, and that the rest of the Creative Cloud application functions properly with automatically detected settings, it seems that this should be a minor issue to correct with the application, to ensure that the application cataloging and downloading respects the same configuration as the rest of the client. What is the official Adobe position on the current broken functionality of the Creative Cloud application, and what is the timeline in implementing a fix?
Pertinent Adobe articles:
Creative Cloud Help / Troubleshoot download and install issues (http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation-download.html):
Corporate environments: Configure Hardware firewalls or proxies
Many organizations use a hardware firewall and proxy server that can prevent software from accessing an FTP server. A hardware solution applies to all computers within the corporate network. Most home networks do not use hardware firewall or proxy technology.
1. Contact your company's IT department to obtain firewall or proxy information.
2. Configure your browser with proxy or firewall information.
3. Configure your corporate firewall to by-pass the servers. The following servers are accessed:
ccmdl.adobe.com:80
swupmf.adobe.com:80
swupdl.adobe.com:80
Post from Adobe staff member Jeff A Wright (Reply 14: http://forums.adobe.com/message/5620841😞
Quote: "The automatic detection of settings or the automatic configuration script is not currently supported. Although to be honest when I worked regular in an environment, which utilized a proxy server, this seemed to be a common issue with most applications. The manual configuration was the most reliable method of utilizing a proxy server and allowing the applications to access the Internet."
2
Replies
AdChoices