Error 117: Firewall and Proxy Configurations for Adobe Servers

Adobe Error 117 occurs when the Creative Cloud installer or desktop app cannot establish a handshake with Adobe licensing and distribution servers. This network block is caused by local software firewalls, network proxies, or corporate Deep Packet Inspection (DPI) appliances blocking outbound traffic on ports 80 and 443. Resolving Error 117 requires configuring explicit domain whitelists, bypassing local proxy tunnels, and opening key network paths to restore server access.

Fast-Fix: The 45-Second Solution

To resolve Adobe Error 117 immediately, disable active proxy servers in your operating system’s network settings and white-list ports 80 and 443 in your firewall. Whitelist *.adobe.com, *.adobe.io, and *.adobelogin.com in your security suite. If on a corporate network, bypass SSL inspection for Adobe authentication domains and restart the Creative Cloud desktop app.

Quick Status Snapshot

• Severity Tier: Moderate
• Project Risk: Low (Prevents software downloads, updates, and cloud licensing; local disk assets remain unaffected)
• Root Cause: Outbound traffic blocked by local firewall rules, strict proxy authentication, or SSL/TLS decryption filters.
• Rare Cause: Hardware gateway filtering blocking WebSockets (wss://) traffic on enterprise routers.

Low-Friction vs. High-Friction Scenarios

• If it happens on a personal home network: A third-party security suite (like Bitdefender, Norton, or Malwarebytes) or local Windows/macOS firewall rule is blocking outbound connections for Adobe Desktop Service.
• If it happens on an enterprise or university network: A proxy server or gateway filter requires NTLM/Kerberos authentication or performs SSL decryption, causing the Adobe setup to drop the connection during certificate validation.

Service-Level Mechanism

During installation or initialization, the Adobe Desktop Service attempts to establish secure HTTPS and WebSocket sockets to endpoints like cc-api-data.adobe.io. Error 117 triggers when an outbound packet is dropped or met with a proxy challenge (HTTP 407 Proxy Authentication Required) that the installer cannot resolve automatically. Think of a security checkpoint at a high-security facility: if your delivery truck arrives at the gate without the exact pass specified in the manifest, the guard turns the truck around instantly rather than letting it idle in the loading bay.

Escalation Variables

• Corporate Endpoint Policies: Group Policy (GPO) or MDM profiles forcing all HTTP/HTTPS traffic through an internal proxy server.
• VPN Tunnel Routing: Split-tunneling configurations that redirect authorization domains through an internal corporate pipeline while routing public installer payloads elsewhere.
• Third-Party Network Filter Drivers: Virtual network adapters installed by VPNs or security tools causing routing loops.

The Cost of Delay: Immediate → Next Session

Failing to fix Error 117 blocks all Creative Cloud installation, update, and entitlement checks. While previously installed apps may launch initially under offline grace periods, those applications will lock up or drop into trial mode during subsequent launches when cloud token refreshes fail.

What To Do Right Now

1. Turn off active VPNs, web shields, and network monitoring utilities.
2. Open system proxy settings and toggle Use a proxy server to Off.
3. Open Windows Defender Firewall (or macOS Socket Filter) and verify that Adobe Desktop Service has both Inbound and Outbound permissions enabled.
4. Relaunch the Creative Cloud desktop app as an Administrator.

Hard-Stop Failure Signals

• HTTP 407 Errors in Logs: Persistent proxy authentication prompts in installation logs indicate an enterprise network proxy requirement that cannot be bypassed locally without network admin credentials.
• Man-in-the-Middle Certificate Alerts: Persistent invalid security certificate warnings across web browsers indicate corporate SSL inspection intercepting HTTPS traffic.

The Professional Recovery Sequence

Method 1: Disable System Proxy Settings

Windows:

1. Press Win + I to open Settings, then navigate to Network & internet > Proxy.
2. Under Automatic proxy setup, turn Automatically detect settings to On.
3. Under Manual proxy setup, click Edit next to “Use a proxy server” and toggle it Off.

macOS:

1. Go to System Settings > Network.
2. Select your active network connection (Wi-Fi or Ethernet) and click Details.
3. Select the Proxies tab.
4. Ensure Web Proxy (HTTP) and Secure Web Proxy (HTTPS) are toggled off, then click OK.

Method 2: Configure Firewall Domain Whitelisting

Ensure your local or perimeter firewall allows outbound access over ports 80 and 443 for the following essential domain patterns:

• .adobe.com
• .adobe.io
• .adobelogin.com
• .ftcdn.net
• .ingest.adobe.io

For a complete breakdown of clearing local DNS blocks caused by invalid lookup tables, see Error P207: How to Flush DNS for Adobe CC Authentication.

Method 3: Bypass Proxy for Adobe Endpoints (PAC File / OS Settings)

If you must operate on a network that requires a proxy server for general web access, add Adobe domain exceptions directly to your OS bypass list:

1. In Windows Proxy Settings, scroll to Manual proxy setup.
2. In the text field labeled Don’t use the proxy server for addresses that start with the following, enter:Plaintext *.adobe.com; *.adobe.io; *.adobelogin.com
3. Save the changes and test the connection using the Creative Cloud desktop app.

Method 4: Test Connectivity via Command Line

To verify whether a local firewall or proxy is blocking communication with Adobe endpoints, perform a quick socket check using PowerShell or Terminal:

Windows PowerShell:

PowerShell

Test-NetConnection -ComputerName cc-api-data.adobe.io -Port 443

If the output shows TcpTestSucceeded : True, your local network path is clear. If it returns False, a local firewall rule or network appliance is actively dropping the packets.

macOS Terminal:

Bash

nc -zv cc-api-data.adobe.io 443

Required Resource Allocation

• Privileges: Local Administrative access to modify OS proxy settings and firewall rules.
• Port Access: Open outbound communication over TCP ports 80 (HTTP) and 443 (HTTPS).
• Network Credentials: PAC file bypass exceptions or proxy credential overrides if working within managed corporate networks.

Final Render

Disabling unauthenticated proxies and ensuring open outbound paths on ports 80 and 443 removes the barrier causing Error 117. Once the network layer passes secure handshakes directly to Adobe endpoints, software installations and licensing syncing will complete without interruption.