-
Setup and onboarding
- Explore Adobe Admin Console
- Sign-in and access
-
Licensing
- Licensing overview
- Licensing types
-
Identity and SSO
- Set up identity
- Integrate with Microsoft Entra
- Integrate with Google Sync
- Integrate with other SSO providers
- Troubleshoot
-
Directories, domains, and access
-
Directories and domains
- Create a directory for SAML identity providers
- Verify domain ownership
- Set up domains for directory authentication
- Move domains across directories
- Encrypted and trusted directory domain transfers
- Move directories between Admin Consoles
- Delete directories and domains
- Automatic account creation overview
- Enable automatic account creation
- Automatic federated account creation FAQ
- Domain enforcement
- Directory trusting
-
Directories and domains
-
Settings
- Asset settings
- Manage encryption
-
User management
- Understand user management
- Manage users and groups
- Manage admins
- Manage user roles
- Migrate users
-
Products and entitlements
- Manage products
- Manage product profiles
- Special programs plans
- Manage entitlements
- Manage automatic assignment
- Manage product access
- Manage self-service policies
- Manage app integrations
- Frame.io integration
- Manage product permissions
- Manage storage and assets
-
Manage services
- Configure services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
-
Deploy apps and updates
- Prepare for deployment
- Manage pre-generated packages
- Create packages
- Customize end-user experience
- Deploy packages
- Use third-party deployment tools
-
Manage Shared Device Licensing (SDL)
- Shared Device Licensing overview
- Deploy Shared Device Licensing
- Manage SDL profiles and user access
- Activate shared device licenses
- Use the Shared Device Licensing toolkit
- Recover shared device licenses
- Shared Device Licensing identity FAQ
- Shared Device Licensing deployment FAQ
- Shared Device Licensing access FAQ
- Known issues in Shared Device Licensing
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Contracts and renewals
- Reports and logs
-
Get started with Global Admin Console
- Get started
- Manage your organization
- Reports audit
-
Get help
- Support options
-
General troubleshooting
- Microsoft Purview Information Protection support in Acrobat
- Use the Creative Cloud Cleaner tool to fix installation issues
- Fix app launch errors on Shared Device Licensing machines
- Technical support boundaries for virtualized or server-based environments
- Resolve trial and license expired errors
- Migrating to OAuth Server-to-Server Credentials
- Manage device authentication for Creative Cloud and Acrobat Pro
Troubleshoot missing WebSocket upgrade headers
Issue
Adobe logs have shown an increase in HTTP 400 errors for WebSocket endpoints in Adobe Express. The error response indicates missing Upgrade headers in client connection requests.
Enterprise clients may see these 400 responses when trying to establish WebSocket connections. This can happen when a proxy server in your enterprise environment strips or blocks the Upgrade header before the request reaches Adobe's servers.
Resolution
If your enterprise environment routes traffic through a proxy server, configure the proxy to treat the Upgrade header as hop-by-hop and pass it through unchanged on WebSocket connection requests. Stripping this header at the proxy causes the connection to fail with an HTTP 400 error.
See WebSocket proxying configuration for more details.
