Welcome to the Alteryx Knowledge Base
Created/Edited -
Alteryx One App (AOA) gets stuck in a sign-in loop on Windows Server when corporate endpoint protection (e.g., Sophos, Zscaler, Netskope) performs TLS inspection. Attempting to manually apply the Native TLS workaround by editing the settings file in Notepad may cause AOA to crash with a JSON parse error.
Alteryx One App (AOA) fails to sign in on Windows Server 2019 — user encounters an infinite sign-in loop. AOA launches successfully but authentication fails with invalid peer certificate: UnknownIssuer error in the Rustls TLS stack. Additionally, applying the useNativeTls: true workaround via manual Notepad editing causes AOA to crash on launch with: "Failed to set up the app. The base URL is not available in the settings file."
- Alteryx One App version 1.0.384
- Windows Server 2019 (Remote Desktop environment)
- Sophos Endpoint Protection (performing TLS inspection)
- EU1 region (eu1.alteryxcloud.com)
- Okta SAML SSO
- Admin (/ALLUSERS) installation
- Windows PowerShell 5.1 (default on server)
- Administrator access to the Windows Server
- PowerShell 7 installed (recommended) or access to Windows PowerShell 5.1
- Knowledge of the correct AOA region and base URL for your organisation (e.g.,
eu1.alteryxcloud.comfor EU,us1.alteryxcloud.comfor US)
Two interrelated issues:
- Sign-in loop — Sophos endpoint protection performs TLS inspection, presenting its own certificate in the chain. AOA's default Rustls TLS stack has its own trust store and does not use the Windows certificate store, so it cannot validate the Sophos certificate → InvalidCertificate(UnknownIssuer).
- Crash when applying fix — Manually editing alteryx-one-settings.json in Notepad on Windows Server introduces invisible characters (UTF-8 BOM or smart quotes). AOA's strict JSON parser cannot parse the corrupted file, fails to read the baseUrl and useNativeTls settings, and panics on launch. The fallback default-settings.json was also corrupted by the same manual editing, leaving AOA with no valid configuration source.
Create both settings files using PowerShell to guarantee clean UTF-8 encoding without BOM.
⚠️ Replace the location and baseUrl values with your region:
- US:
"location":"US","baseUrl":"us1.alteryxcloud.com" - EU:
"location":"EU","baseUrl":"eu1.alteryxcloud.com"
Option 1 — PowerShell 7+ (recommended):
Remove-Item "$env:APPDATA\Alteryx\alteryx-one-settings.json" -Force -ErrorAction SilentlyContinue
Remove-Item "C:\Program Files\Alteryx\AlteryxOne\default-settings.json" -Force -ErrorAction SilentlyContinue
Remove-Item "$env:LOCALAPPDATA\Alteryx\AlteryxOne\Tokens\*" -Force -ErrorAction SilentlyContinue
Set-Content -Path "$env:APPDATA\Alteryx\alteryx-one-settings.json" -Value '{"location":"EU","baseUrl":"eu1.alteryxcloud.com","useNativeTls":true}' -Encoding UTF8NoBOM
Set-Content -Path "C:\Program Files\Alteryx\AlteryxOne\default-settings.json" -Value '{"location":"EU","baseUrl":"eu1.alteryxcloud.com","useNativeTls":true}' -Encoding UTF8NoBOM
Option 2 — Windows PowerShell 5.1 fallback:
$json = '{"location":"EU","baseUrl":"eu1.alteryxcloud.com","useNativeTls":true}'
[System.IO.File]::WriteAllText("$env:APPDATA\Alteryx\alteryx-one-settings.json", $json)
[System.IO.File]::WriteAllText("C:\Program Files\Alteryx\AlteryxOne\default-settings.json", $json)
Enterprise deployment via Group Policy:
- Create the config files using the PowerShell commands above
- Copy both files to the NETLOGON share (or another central location accessible from servers)
- Computer Configuration > Preferences > Windows Settings > Files:
- Source:
\\domain\NETLOGON\default-settings.json - Destination:
C:\Program Files\Alteryx\AlteryxOne\default-settings.json - Action: Update
- User Configuration > Preferences > Windows Settings > Files:
- Source:
\\domain\NETLOGON\alteryx-one-settings.json - Destination:
%APPDATA%\Alteryx\alteryx-one-settings.json - Action: Update
- If applying both policies to an OU containing only computers, enable loopback processing:
- Computer Configuration > Policies > Administrative Templates > System > Group Policy > Configure user Group Policy loopback processing mode
- Mode: Merge
Verification:
After relaunching AOA, check %LocalAppData%\Alteryx.AlteryxOne\logs\aoa_tauri.log:
- ✅
HTTP client configured to use Native TLS stack— fix applied successfully - ❌
HTTP client configured to use Rustls TLS stack (default)setting was not picked up
Note: default-settings.json only seeds settings for users who have never run AOA before. For existing user profiles, the per-user alteryx-one-settings.json must also be recreated.
- Verification: After relaunching AOA, check
%LocalAppData%\Alteryx.AlteryxOne\logs\aoa_tauri.logforHTTP client configured to use Native TLS stackto confirm the fix is applied. - For enterprise-wide deployment, the settings files can be pushed via Group Policy using Computer Configuration and User Configuration file preferences. See the Group Policy deployment section below.
default-settings.jsononly seeds settings for users who have never run AOA before it will not update existing user profiles.