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

public_addr can no longer specify protocol #24796

Closed
Tener opened this issue Apr 19, 2023 · 2 comments · Fixed by #24871
Closed

public_addr can no longer specify protocol #24796

Tener opened this issue Apr 19, 2023 · 2 comments · Fixed by #24871
Assignees
Labels
bug test-plan-problem Issues which have been surfaced by running the manual release test plan

Comments

@Tener
Copy link
Contributor

Tener commented Apr 19, 2023

Expected behavior:

Prior to #23866 this used to work:

proxy_service:
  enabled: "true"
  public_addr:  ['https://teleport.example.com']

Now this needs to be:

proxy_service:
  enabled: "true"
  public_addr:  ['teleport.example.com']

Current behavior:

If https is part of the public_addr, these errors will be spammed:

2023-04-19T12:35:01+02:00 DEBU [PROXY:AGE] Failed to dial boson.tener.io:3080. error:[
ERROR REPORT:
Original Error: *net.OpError dial https: unknown network https
Stack Trace:
	github.com/gravitational/teleport/api@v0.0.0/client/alpn.go:139 github.com/gravitational/teleport/api/client.(*ALPNDialer).DialContext
	github.com/gravitational/teleport/lib/utils/proxy/proxy.go:102 github.com/gravitational/teleport/lib/utils/proxy.directDial.DialTimeout
	github.com/gravitational/teleport/lib/reversetunnel/agent_dialer.go:52 github.com/gravitational/teleport/lib/reversetunnel.(*agentDialer).DialContext
	github.com/gravitational/teleport/lib/reversetunnel/agent.go:364 github.com/gravitational/teleport/lib/reversetunnel.(*agent).connect
	github.com/gravitational/teleport/lib/reversetunnel/agent.go:319 github.com/gravitational/teleport/lib/reversetunnel.(*agent).Start
	github.com/gravitational/teleport/lib/reversetunnel/agentpool.go:314 github.com/gravitational/teleport/lib/reversetunnel.(*AgentPool).connectAgent
	github.com/gravitational/teleport/lib/reversetunnel/agentpool.go:273 github.com/gravitational/teleport/lib/reversetunnel.(*AgentPool).run
	github.com/gravitational/teleport/lib/reversetunnel/agentpool.go:257 github.com/gravitational/teleport/lib/reversetunnel.(*AgentPool).Start.func1

Notes:

I'm not sure why I put https:// in my test configuration, as all the docs for public_addr do not mention the protocol at all. That being said, it used to work, even if by accident, and no longer does.

Version: Teleport v13.0.0-alpha.1 git:v13.0.0-alpha.1-0-gf9b7326 go1.20.3

@Tener Tener added the bug label Apr 19, 2023
@Tener Tener added the test-plan-problem Issues which have been surfaced by running the manual release test plan label Apr 19, 2023
@greedy52
Copy link
Contributor

@Tener is your auth and proxy in the same process?

Do you mind giving the above fix a try? or I can do more testing when I'm back next week.

cc @smallinsky

@Tener
Copy link
Contributor Author

Tener commented Apr 20, 2023

@Tener is your auth and proxy in the same process?

Do you mind giving the above fix a try? or I can do more testing when I'm back next week.

cc @smallinsky

Yes, auth and proxy were in the same process.

The fix works like a charm, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug test-plan-problem Issues which have been surfaced by running the manual release test plan
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants