Proxy IP - Need to use the teleport ip and not the client ip #52519
Unanswered
GiovanniGit-IT
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Expected behavior:
Hello,
I only have a teleport server in standalone or there are resources on it (ssh, rdp, HTTPS application).
I would like the ip used when a client (user) connects to a resource to be that of teleport and not the client's public ip.
If you have any ideas, thank you in advance.
Current behavior:
When i start a https application in example, the used ip is the public ip of client and not teleport server ip.
Bug details:
Config teleport server:
`version: v3
teleport:
nodename: example
data_dir: /var/lib/teleport
log:
output: stderr
severity: INFO
format:
output: text
ca_pin: ""
diag_addr: ""
auth_service:
enabled: "yes"
proxy_protocol: off
listen_addr: 0.0.0.0:3025
cluster_name: example.example.com
proxy_listener_mode: multiplex
ssh_service:
enabled: "yes"
proxy_service:
enabled: "yes"
proxy_protocol: off
https_cert_file: /etc/letsencrypt/live/example.example.com/fullchain.pem
https_key_file: /etc/letsencrypt/live/example.example.com/privkey.pem
web_listen_addr: 0.0.0.0:443
public_addr: example.example.com
windows_desktop_service:
enabled: yes
listen_addr: "0.0.0.0:3028"
static_hosts:
ad: false
addr: X.X.X.X
labels:
environment: windows
app_service:
enabled: true
apps:
uri: "https://app.example.com"
public_addr: "app.example.com"
labels:
env: "app"
uri: "https://app2.example.com"
public_addr: "app2.example.com"
labels:
environment: "app2"`
Beta Was this translation helpful? Give feedback.
All reactions