Replies: 2 comments
-
i can now login by switch the uri to http:10.x.x.x/reports/browse instead of https, but now i get 400 bad request |
Beta Was this translation helpful? Give feedback.
0 replies
-
On the face of it, this looks like the web server is expecting an HTTP/1.1 connection but Teleport is actually using HTTP/2 to connect to it. This shouldn't happen. With that said, your app config also looks a bit off. Correct indentation and spacing are very important in YAML. Try this and restart: apps:
- name: is-report
uri: https://is-report.example.com/reports/browse
public_addr: is-report.teleport.exmple.com
labels:
xx: xx |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
iam proxying my power bi report server web UI through teleport,
the UI is has a NLB and NFW on front,
iam accessing through the original url normally but through teleport it prompts the report server's basic auth page
and after i log in it shows a black screen with internal server error
Teleport/teleport agent Version:
14.3.14
Report server logs:
received a request with an unmatched or no authentication scheme. 401
teleport agent logs:
{"caller":"reverseproxy/reverse_proxy.go:216","component":"app:service","level":"error","message":"Error forwarding to https://is-report.example.com/reports/browse, err: stream error: stream ID 3; HTTP_1_1_REQUIRED; received from peer","timestamp":"2024-04-18T08:57:54Z"}
teleport agent config:
iam not sure if this is related to teleport not supporting basic auth
or redirection issue or could be certificate issue!
any ideas ?
Beta Was this translation helpful? Give feedback.
All reactions