Gradle / IntelliJ miscommunication causing "Unable to start daemon process"

Question

My IntelliJ Idea projects have been working fine until I cloned a new project from our repo and installed Gradle.

This new project runs, but running the debugger causes the following error:

I've completed the steps recommended in this similar SO question. I have also read the Gradle Daemon guide.

Some helpful information:

-Gradle does respond to command line prompts, including --profile and --status:

-The project builds and executes; the problem is only the debugger. Is this a mapping issue between IntelliJ and Gradle?

-In the Settings menu, Gradle JVM: is set to "Use Project JDK (Java version "1.8.0_211") and this program is written in Java 8. Delegate settings set to: Build and run using intelliJ IDEA. Run tests using IntelliJ IDEA. Should these change to Gradle?

-I took the advice of one of the respondents and had one of our IT guys check out my ports and firewall settings. He was unable to solve the problem and said the issue is with Gradle.

So far, nothing has worked. What should I do?

Answer 1

I solved this problem after some tinkering:

In (IntelliJ) File > Settings > Build, Execution, Deployment > Gradle, I changed "Use gradle 'wrapper' task configuration" to "Use local gradle distribution."

Also, notice in this screenshot that "Gradle VM options" has a custom value; this was suggested as a solution in another post. This relates to memory management, as some people speculated that the daemon was crashing because of a RAM issue. My solution appears to work regardless of whether I alter that value.