AariaSec

Uninstall AariaSec

Read this before removing anything by hand. AariaSec sets proxy environment variables so command-line tools route through it; deleting the application without clearing them leaves your terminal pointed at a proxy that no longer exists, and the symptom — everything fails except browsers — is confusing enough that it is worth avoiding.

The safe order is always: quit, then uninstall.


1. Quit properly

Quit from the tray or menu bar — right-click the shield, choose Quit. That clears the routing variables, releases the port, and stops the child processes.

Do not force-quit for this. Task Manager and kill -9 skip the cleanup, which is the situation the rest of this page exists to repair.

2. Remove the application

Windows — Settings → Apps → AariaSec → Uninstall. The uninstaller stops the app first (its watchdog would otherwise re-set the variables you are trying to clear), removes the CA certificate, clears all six environment variables, and removes the scheduled task.

macOS — drag AariaSec from Applications to the Trash, then remove the CA from Keychain Access (search for "AariaSec", delete the certificate).

Linux

sudo dpkg -r aariasec # Debian / Ubuntu

3. Verify nothing was left behind

Windows

reg query HKCU\Environment | Select-String 'PROXY|CERT|CA_'
Get-NetTCPConnection -LocalPort 8080 -State Listen -ErrorAction SilentlyContinue
Get-Process aariasec,aariasec-api,aariasec-proxy -ErrorAction SilentlyContinue

All three should return nothing.

If you installed the machine-wide build, the first query looks at the wrong hive and will return nothing whether or not the variables are set. Check this one too, from an elevated prompt:

reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" |
 Select-String 'PROXY|CERT|CA_'

macOS / Linux

env | grep -Ei 'proxy|ssl_cert|ca_bundle'
lsof -nP -iTCP:8080 -sTCP:LISTEN

If you already removed it the hard way

Clear the variables manually. All six, not just the proxy pair — leaving SSL_CERT_FILE pointed at a deleted CA bundle breaks HTTPS for Python and Node, because that variable replaces the trust store rather than extending it.

foreach ($v in 'HTTPS_PROXY','HTTP_PROXY','NO_PROXY','SSL_CERT_FILE','REQUESTS_CA_BUNDLE','NODE_EXTRA_CA_CERTS') {
 [Environment]::SetEnvironmentVariable($v, $null, 'User')
}

Sign out and back in for that to reach running applications.


Your data

Detection history, fingerprints and the audit log live in the AariaSec data directory and are removed with it unless you keep the data folder.

There is no server-side copy to request deletion of, because there was never a server-side copy. Nothing was uploaded, and no prompt or response content was ever stored anywhere — including locally.