Web Proxy Auto Discovery (WPAD) fails in Creative Cloud


the creative cloud desktop application has problem wpad automatic proxy detection.  when computer configured "automatically detect settings", creative cloud application not load apps list, giving error "download error.  unable reach adobe servers.  please check internet  connectivity, firewall settings, , try again."  other elements of creative cloud application (logging in, accepting terms of use, "home", "files", "fonts" , "behance" tabs have no issues using automatically detected settings).  can refresh netstat on command line , see creative cloud application tries make direct calls ec2 servers when attempting connect "apps" list instead of using proxy.

 

if manually configure pac file or manually configure proxy on computer, creative cloud can connect successfully.  failure occurs "automatic detect settings".  have tested different wpad server configurations, include apache on unix, iis7 on windows, text/plain , application/x-ns-proxy-autoconfig mime types, , cname vs record 'wpad'.  creative cloud continues fail operate correctly.

 

the old version of adobe application manager can connect , download updates using "automatic detect settings".  update (and installed apps) successfully.  after updates itself, connect , update second time, time replacing creative cloud application, fails connect.  behaviour new adobe application manager once becomes creative cloud application.

 

it seems "official" documentation can find "broken designed" (see adobe references @ bottom of post).  connecting directly client internet without proxy prohibited our information security policy (the chat support agent tried tell me 3 times "solution" disable proxy , open ports 80 , 443 internet).  manually configuring proxy through pac file or manually setting proxy information causes other issues , performance problems (i disagree adobe staff member jeff wright's assertion automatically detecting settings "a common issue applications"--see reference @ bottom of post).

 

while technically open firewall or manually configure proxy make creative cloud function properly, these unacceptable workarounds stated.  considering previous iteration (adobe application manager) functioned fine automatically detected settings, , rest of creative cloud application functions automatically detected settings, seems should minor issue correct application, ensure application cataloging , downloading respects same configuration rest of client.  official adobe position on current broken functionality of creative cloud application, , timeline in implementing fix?

 

pertinent adobe articles:

 

creative cloud / troubleshoot download , install issues (http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation-download.html):

 

corporate environments: configure hardware firewalls or proxies

 

many organizations use hardware firewall , proxy server can prevent software accessing ftp server. hardware solution applies computers within corporate network. home networks not use hardware firewall or proxy technology. 

 

1. contact company's department obtain firewall or proxy information.

2. configure browser proxy or firewall information.

3. configure corporate firewall by-pass servers. following servers accessed:

             ccmdl.adobe.com:80

             swupmf.adobe.com:80

             swupdl.adobe.com:80

 

post adobe staff member jeff wright (reply 14: http://forums.adobe.com/message/5620841):

 

quote: "the automatic detection of settings or automatic configuration script not supported.  although honest when worked regular in environment, utilized proxy server, seemed common issue applications.  manual configuration reliable method of utilizing proxy server , allowing applications access internet."

hi nick,

 

is there solution yet adobe?



More discussions in Downloading, Installing, Setting Up


adobe

Comments

Popular posts from this blog

Thread: Can not create raid array: mdadm: no raid-devices specified.

Thread: HOW TO: Package and theme GTK+ / Gtkmm apps in Linux for Windows

Thread: Twinview issues