Description
Summary:
When NEMOCLAW_PROXY_HOST and NEMOCLAW_PROXY_PORT are exported in the host shell before reinstalling NemoClaw, the resulting sandbox still uses the default proxy http://10.200.0.1:3128 instead of the configured custom proxy. This causes proxy override validation to fail.
Environment:
- Platform: macOS 26.1
- Hardware: Apple M4, 24 GB
- Runtime: Colima
- Docker ServerVersion: 29.2.1
- NemoClaw: v0.0.4
- Install path: pure release-style install from
~
- Shell: zsh
Repro steps:
- In the same host shell, export custom proxy variables:
`export NEMOCLAW_PROXY_HOST=1.2.3.4`
`export NEMOCLAW_PROXY_PORT=9999`
- Uninstall NemoClaw in the same shell:
`nemoclaw uninstall --yes`
- Reinstall NemoClaw in the same shell:
`curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash`
-
Complete onboarding with a new sandbox, e.g. proxy-test
-
Reload shell:
source ~/.zshrc
-
Connect to the sandbox:
nemoclaw proxy-test connect
-
Inside sandbox, check proxy envs:
echo $HTTP_PROXY
echo $HTTPS_PROXY
echo $NO_PROXY
echo $no_proxy
Actual result:
Inside sandbox, the proxy envs still use defaults:
HTTP_PROXY=http://10.200.0.1:3128
HTTPS_PROXY=http://10.200.0.1:3128
NO_PROXY=localhost,127.0.0.1,::1,10.200.0.1
no_proxy=localhost,127.0.0.1,::1,10.200.0.1
Expected result:
HTTP_PROXY and HTTPS_PROXY should reflect the custom values derived from:
NEMOCLAW_PROXY_HOST=1.2.3.4
NEMOCLAW_PROXY_PORT=9999
- Default proxy values should not be used
NO_PROXY and no_proxy should still match
inference.local should remain absent from NO_PROXY
Notes:
- This is not a shell persistence issue; the custom env vars were exported and preserved in the same terminal through uninstall and reinstall.
- Partial expected behavior is still correct:
NO_PROXY and no_proxy match
inference.local is absent
- The failure is specifically that custom proxy host/port are ignored.
Bug Details
| Field |
Value |
| Priority |
Unprioritized |
| Action |
Dev - Open - To fix |
| Disposition |
Open issue |
| Module |
Machine Learning - NemoClaw |
| Keyword |
NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL |
[NVB# 6045052]
[NVB#6045052]
Description
Summary:
When
NEMOCLAW_PROXY_HOSTandNEMOCLAW_PROXY_PORTare exported in the host shell before reinstalling NemoClaw, the resulting sandbox still uses the default proxyhttp://10.200.0.1:3128instead of the configured custom proxy. This causes proxy override validation to fail.Environment:
~Repro steps:
Complete onboarding with a new sandbox, e.g.
proxy-testReload shell:
source ~/.zshrcConnect to the sandbox:
nemoclaw proxy-test connectInside sandbox, check proxy envs:
echo $HTTP_PROXYecho $HTTPS_PROXYecho $NO_PROXYecho $no_proxyActual result:
Inside sandbox, the proxy envs still use defaults:
HTTP_PROXY=http://10.200.0.1:3128HTTPS_PROXY=http://10.200.0.1:3128NO_PROXY=localhost,127.0.0.1,::1,10.200.0.1no_proxy=localhost,127.0.0.1,::1,10.200.0.1Expected result:
HTTP_PROXYandHTTPS_PROXYshould reflect the custom values derived from:NEMOCLAW_PROXY_HOST=1.2.3.4NEMOCLAW_PROXY_PORT=9999NO_PROXYandno_proxyshould still matchinference.localshould remain absent fromNO_PROXYNotes:
NO_PROXYandno_proxymatchinference.localis absentBug Details
[NVB# 6045052]
[NVB#6045052]