Suggest enabling PROXY protocol in DTW troubleshooting #49791
Conversation
codingllama
added
no-changelog
github-actions
bot
requested review from
mmcallister,
ptgott,
r0mant,
xinding33 and
zmb3
|
🤖 Vercel preview here: https://docs-kfrw2c9hz-goteleport.vercel.app/docs |
|
PTAL @tigrato. |
|
🤖 Vercel preview here: https://docs-a7c2hw0h6-goteleport.vercel.app/docs |
|
Friendly ping @tigrato. |
| @@ -12,3 +12,6 @@ | |||
| - `tsh` v15.0.0 or newer. [Install tsh for Linux](../../installation.mdx#linux). | |||
| - To authenticate a Web UI session you need [Teleport Connect]( | |||
| ../../connect-your-client/teleport-connect.mdx#installation--upgrade) | |||
| - Correct end-user IP propagation to your Teleport deployment: X-Forwarded-For | |||
There was a problem hiding this comment.
can we add https://goteleport.com/docs/reference/config/#reference-configurations as reference?
# Enables the Proxy service to take client source IPs from the
# "X-Forwarded-For" headers for web APIs.
#
# In order to prevent IP spoofing, it is important to ensure that the Proxy
# service is placed behind a layer 7 load balancer or reverse proxy that
# sets client IPs in the "X-Forwarded-For" headers. Requests with more than
# one IPs will be rejected.
trust_x_forwarded_for: false
We really need a doc to guide people ensuring the IP addresses are correct and how to configure them. That would be awesome using debug app access to validate them.
cc @ptgott
There was a problem hiding this comment.
Done for the links, PTAL.
public-teleport-github-review-bot
bot
removed request for
r0mant and
mmcallister
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
🤖 Vercel preview here: https://docs-hzuc2fb01-goteleport.vercel.app/docs |
|
@codingllama See the table below for backport results.
|
Suggest enabling PROXY protocol as a way to solve "IP mismatch" errors.
Related to https://github.com/gravitational/cloud/issues/11289.