GoLand module proxy configuration lacks per‑module override for private repositories

Resolving Private Module Proxy Leaks in GoLand

GoLand does not provide a native GUI table for per-module proxy overrides. Instead, it relies on the standard Go toolchain's logic. To prevent private modules from being requested via a public proxy, you must use the GOPRIVATE environment variable.

The Solution: Using GOPRIVATE

The GOPRIVATE variable tells the Go toolchain to bypass both the configured GOPROXY and the checksum database (GOSUMDB) for any module path that matches the specified patterns. This ensures that private dependencies are fetched directly from the source (e.g., via SSH or HTTPS) rather than being leaked to a public proxy.

To configure this in GoLand:

1. Navigate to Settings > Go > GOROMOD.
2. While there is a field for the Module Proxy (which sets GOPROXY), there is often no dedicated GOPRIVATE field in the basic UI.
3. Go to Settings > Appearance & Behavior > Path Variables or configure the environment variable at the OS level.
4. Alternatively, if you are using a specific Run/Debug configuration, add GOPRIVATE=github.com/your-org/* to the Environment field.

Explanation of IDE Behavior

Because GoLand acts as a wrapper around the Go CLI, it does not implement its own proxy routing engine. Consequently:

• Warnings: The IDE will not emit a specific "Private module leaked" warning. It only reports the standard output/error returned by the go command. If a proxy returns a 404 or 410 for a private repo, it will appear in the Build or Event Log window.
• Vendor/Refresh: Operations like go mod vendor or the IDE's module refresh trigger the Go toolchain. If GOPRIVATE is correctly set in the environment where the IDE is running, these operations will bypass the proxy for matching modules.

Verification

To verify that your private modules are bypassing the proxy, run the following command in the GoLand integrated terminal:

go env GOPROXY GOPRIVATE

Then, attempt to list the modules. If GOPRIVATE is working, the Go tool will attempt a direct connection to your VCS provider rather than the proxy URL:

go list -m all

Diagnostic Detail Needed: Are you using a project-specific .env file or a global OS environment configuration? This determines whether you should set GOPRIVATE in the IDE's global settings or within the specific Run/Debug configuration.