I found the issue. I didn't realize that this started up something on localhost. I had to update my NOPROXY setting to include that