Hey @Andrew McMorris
I have to apologise you're getting a late reply!
I was out on leave for 3 weeks and I normally look out for questions in here!
To answer your question!
Rovo Dev CLI can work in environments with HTTP/HTTPS proxies, but some additional configuration may be required.
Proxy Support: Rovo Dev CLI relies on your system or environment proxy settings. You may need to set environment variables like HTTP_PROXY
, HTTPS_PROXY
, and NO_PROXY
for it to connect properly through your proxy.
Common Issues: If you're seeing error messages, it could be due to missing or incorrect proxy configuration, or your proxy requiring authentication.
Plans for Improvement: The team is aware that proxy support is important and is working to improve compatibility and documentation for proxy environments.
What you can try:
Set the appropriate proxy environment variables before running the CLI:
export HTTP_PROXY=http://your-proxy:port
export HTTPS_PROXY=http://your-proxy:port
export NO_PROXY=localhost,127.0.0.1
If your proxy requires authentication, include your credentials in the URL (if allowed by your IT policy).
If issues persist, please share the specific error messages or check the CLI logs for more details.
Let me know if this helps!
I'll definitely be passing on this feedback to the product team!
Kindest regards,
Jovana
Thanks for getting back to me!!
I've updated our variables to use as suggested and I can connect to our Jira and run commands all okay.
With Rovo I can Auth and get a green tick for that, but when I try and run any commands in Rovo Dev I just get the little animation circle icon which does not provide any output and our Usage does not change.
So there is something that appears to not be going through our Proxy. Would be good to know the endpoint acli is sending traffic to so can make sure it's not being blocked by our Proxy.
Cheers
Andy.