Member-only story
HTTP 403 — When Your Corporate Proxy Decides Gradle Isn’t Welcome
A field guide for Android developers stuck behind a firewall that hates the open internet.
Could not GET 'https://services.gradle.org/distributions/gradle-8.5-all.zip'.
Received status code 403 from server: Forbidden- Forbidden. Not 404. Not a network timeout. Forbidden.
If you’ve ever worked at a bank, a hospital, a government office, or any company with a security team that takes its job seriously, this error will eventually find you. And it will always find you on the day you need to ship something.
Let me walk you through what’s actually happening, why your “internet works fine” excuse won’t help, and how I finally got my Kotlin Android project to build behind a corporate proxy without sacrificing my sanity.
What’s actually going on
When you click Sync, Gradle reaches out to download the distribution defined in your gradle/wrapper/gradle-wrapper.properties file. On a normal network, your laptop opens an HTTPS connection to services.gradle.org, exchanges a TLS handshake, and pulls down the zip. Easy.
On a corporate network, things are not easy.
Most enterprise networks route all outbound traffic through a proxy server — something like…
