Grails’ false “proxy” problem


I haven’t used Grails in a while so I chose to use it for a small web application I needed to build yesterday. Mostly because I wanted to see what was new in version 3.2.4. I have a bit of a history with Grails, it’s now like a running joke with me that almost every single time I use Grails, I have to struggle through some weird setup issue. So I was really curious what today’s problem would be.

The Problem: Error occurred running Grails CLI: proxy

I downloaded the new version and set up my PATH, JAVA_HOME, and GRAILS_HOME. Crossing my fingers, I tried to create a simple hello world app:

grails create-app HelloWorld

And true to my luck, something went wrong. Grails gave me the following lovely error.

Error occurred running Grails CLI: proxy (Click for stack trace)

Error occurred running Grails CLI: proxy (NOTE: Stack trace has been filtered. Use --verbose to see entire trace.) proxy
at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(
at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(
at org.apache.http.impl.client.DefaultRequestDirector.execute(
at org.apache.http.impl.client.AbstractHttpClient.execute(
at org.apache.http.impl.client.DecompressingHttpClient.execute(
at org.eclipse.aether.transport.http.HttpTransporter.execute(
at org.eclipse.aether.transport.http.HttpTransporter.implGet(
at org.eclipse.aether.spi.connector.transport.AbstractTransporter.get(
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(
at org.springframework.boot.cli.compiler.grape.AetherGrapeEngine.resolve(
at org.springframework.boot.cli.compiler.grape.AetherGrapeEngine.resolve(
at org.springframework.boot.cli.compiler.grape.AetherGrapeEngine.resolve(
at org.grails.cli.boot.GrailsDependencyVersions.<init>(GrailsDependencyVersions.groovy:53)
at org.grails.cli.boot.GrailsDependencyVersions.<init>(GrailsDependencyVersions.groovy:49)
at org.grails.cli.profile.repository.MavenProfileRepository.<init>(MavenProfileRepository.groovy:53)
at org.grails.cli.GrailsCli.createMavenProfileRepository(GrailsCli.groovy:333)
at org.grails.cli.GrailsCli.execute(GrailsCli.groovy:234)
at org.grails.cli.GrailsCli.main(GrailsCli.groovy:159)Error |
Error occurred running Grails CLI: proxy

At first glance, it looks like I have a proxy problem, and google seems to agree. Searching that error led me to posts claiming I needed to fix my proxy settings, maybe pass them along in GRAILS_OPTS, then offer up a goat sacrifice to the vengeful Grails gods to atone for using meteor.

There is one really small, insignificant, little problem though… I’m not behind a proxy.


It took me 2 hours to find the source of the problem. It turns out I had a leftover folder from long long ago in my home directory.


This was the source of all my misery, it wasn’t a proxy problem. Grails, for some reason, was looking for a host which was named “proxy”. I deleted the folder and alles klar.

So side note, when upgrading to 3 from 2 please delete those .<folders> created in your home directory. Just like when you have a weird problem while working in Grails, using the “clean” can sometimes fix it.



About Michael

Michael 'phoexer' Musangeya is a Python Software Engineer who has a creepy fascination with photography, video games, and books.

Check Also

Setting up my own CI/CD

So I’m a fan of automation because I don’t like repeating stuff and I’m lazy. …

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.