Skip to content
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

[Fleet] proxy configuration should allow a socks5-prefixed proxy url since Agent supports socks5 proxies #158659

Closed
bczifra opened this issue May 30, 2023 · 1 comment · Fixed by #174338
Labels
bug Fixes for quality problems that affect the customer experience Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@bczifra
Copy link
Member

bczifra commented May 30, 2023

Expected behavior:
Per https://www.elastic.co/guide/en/fleet/current/fleet-agent-proxy-support.html Elastic Agent supports Socks5 proxies, but the validation in

demands either an http or https scheme, so there is no way to specify a socks5://-prefixed proxy url in the Fleet UI.

Screenshots (if relevant):
socks5_error

@bczifra bczifra added bug Fixes for quality problems that affect the customer experience Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team labels May 30, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@nchaulet nchaulet changed the title Fleet's proxy configuration should allow a socks5-prefixed proxy url since Agent supports socks5 proxies [Fleet] proxy configuration should allow a socks5-prefixed proxy url since Agent supports socks5 proxies May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants