-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using CML behind a proxy #336
Comments
Hi @rene-rex, thanks for the feedback! |
That would be great, thanks! I happy to test a fix whenever you have one. |
I think that tomorrow we will have the PR 🚀 |
Are there any updates on this? I am currently also facing this problem with |
Since I am unable to use CML due to this bug, I moved on. So I can't help you here @pirnerjonas |
Thanks for writing @rene-rex. Yeah, I think I will also be unable to use CML then.. |
@pirnerjonas @rene-rex priority 0 now ;) |
@pirnerjonas @rene-rex @0x2b3bfa0 while we had a solution for GL the problem is fundamentally GH. Basically they have the same blocker: |
Hi
Everything running on my GitLab runner must go through a proxy to get anything from the outside world. So, I set the corresponding variables as usual:
However, this results in an error at cml-publish:
I tried to prefix the variables with http/https since it is complaining about an invalid URL but this just gave me another error:
The IP is anonymized above. Any idea how to make CML play nicely with the proxy?
The text was updated successfully, but these errors were encountered: