Android Studio setup wizard cannot download the SDK add-on list
Unable to access Android SDK add-on listShort answer
The setup wizard and SDK Manager need internet access. Behind a firewall, set the proxy in Android Studio's HTTP Proxy settings, not only in gradle.properties, because the IDE setting overrides it. If the log says peer not authenticated, the Java certificate store lacks the proxy's certificate.
Fix it fast
1Find out which cause you have
Check whether the machine can reach the SDK repository at all from a terminal. If a direct connection works and Android Studio's does not, the problem is proxy or certificate handling inside the IDE.
curl -I https://dl.google.com2Match what you see, then jump to its fix
- 1
The wizard fails on a network that only allows internet through a proxy.The IDE has no proxy configuredFix - 2
Gradle builds download through the proxy but the wizard and SDK Manager still fail.The proxy is set only in gradle.propertiesFix - 3
peer not authenticated in the log from Gradle sync or the SDK ManagerJava does not trust the proxy's certificateFix
- 1
What does the error look like?
Unable to access Android SDK add-on listpeer not authenticated
Cause 1 of 3
The IDE has no proxy configured
1Check
Open the proxy page: Settings (Android Studio, Settings on macOS) then Appearance and Behavior, System Settings, HTTP Proxy.
# Android Studio: File > Settings > Appearance & Behavior > System Settings > HTTP Proxy2Fix
Choose Auto-detect proxy settings, or Manual proxy configuration and enter host and port, then Apply. The docs note that Android Studio requires an internet connection for the Setup Wizard.
# Manual proxy configuration: host name, port number, then Check connection3Verify
Reopen the SDK Manager (Tools, SDK Manager) and confirm the package list loads.
# SDK Manager lists platforms and toolsConfirmed by developer.android.com
Cause 2 of 3
The proxy is set only in gradle.properties
1Check
The IDE's HTTP Proxy page overrides gradle.properties inside Android Studio, so a proxy set only there does not help the IDE tools.
grep -n "systemProp" gradle/gradle.properties ~/.gradle/gradle.properties2Fix
Enter the same proxy in the IDE settings. Keep the systemProp.http and systemProp.https entries in gradle.properties for command-line and CI builds.
# gradle.properties (command line and CI)
systemProp.http.proxyHost=proxy.company.com
systemProp.http.proxyPort=443
systemProp.https.proxyHost=proxy.company.com
systemProp.https.proxyPort=4433Verify
Run Check connection in the IDE proxy page.
# HTTP Proxy page: Check connectionConfirmed by developer.android.com
Cause 3 of 3
Java does not trust the proxy's certificate
1Check
The docs say the root cause is a missing certificate in the JDK's cacerts file. Test with a direct connection first to rule out the proxy.
curl -I https://dl.google.com2Fix
If you are behind a proxy and a direct connection works, add the proxy's certificate to the cacerts keystore with keytool. On Ubuntu, an empty cacerts file is a known issue and is fixed by reconfiguring ca-certificates-java.
keytool -importcert -alias corp-proxy -file proxy.cer -cacerts
# Ubuntu, empty cacerts:
sudo /var/lib/dpkg/info/ca-certificates-java.postinst configure3Verify
Sync a project or open the SDK Manager again.
# SDK Manager loads without peer not authenticatedConfirmed by developer.android.com
How do I stop it coming back?
- Set the proxy in the IDE and in gradle.properties on any machine behind a firewall.
- Ask the network team for the proxy certificate before first install.
- Install from the full download rather than relying on the wizard when the network is restricted.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fixMobile apps
The emulator says the GPU driver is unsupported and falls back to software
vulkan-1.dll cannot be found
The emulator picks a graphics mode when it starts.
4 causes, each with a fix