You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aborting SSH handshake because the proxy "eb56ad65-b896-4aba-9572-a11994ea807f.localhost" is already claimed by some other agent. localCluster: targetCluster:localhost reversetunnel/agent_dialer.go:78
#48412
This discussion was converted from issue #48404 on November 04, 2024 23:20.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Expected behavior:
I try to add resource since 14 days :)
Current behavior:
On my resource
root@ubuntu:
/teleport/config# systemctl restart teleport/teleport/config# sudo systemctl status teleport.serviceroot@ubuntu:
● teleport.service - Teleport Service
Loaded: loaded (/lib/systemd/system/teleport.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-11-04 15:48:13 EST; 20s ago
Main PID: 369919 (teleport)
Tasks: 12 (limit: 2384)
Memory: 63.9M
CPU: 590ms
CGroup: /system.slice/teleport.service
└─369919 /usr/local/bin/teleport start --config /etc/teleport.yaml --pid-file=/run/teleport.pid
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Discovery request channel opened: teleport-discovery. leaseID:1 target:test.inno.com:443 localCluster>
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] handleDiscovery requests channel. leaseID:1 target:test.inno.com:443 localCluster: targetCluster:loca>
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Received discovery request: [eb56ad65-b896-4aba-9572-a11994ea807f] leaseID:1 target:test.inno.com:443>
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU Performing ALPN legacy connection upgrade. hostname:test.inno.com:443 client/alpn_conn_upgrade.go:286
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Aborting SSH handshake because the proxy "eb56ad65-b896-4aba-9572-a11994ea807f.localhost" is already claime>
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Changing state connecting -> closed. leaseID:2 target:test.inno.com:443 localCluster: targetCluster:l>
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Failed to connect agent: ssh: handshake failed: proxy already claimed. localCluster: targetCluster:localhos>
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Active agent count: 1 localCluster: targetCluster:localhost reversetunnel/agentpool.go:423
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Active agent count: 1 localCluster: targetCluster:localhost reversetunnel/agentpool.go:423
Nov 04 15:48:14 ubuntu teleport[369919]: 2024-11-04T15:48:14-05:00 DEBU [PROXY:AGE] Active agent count: 1 localCluster: targetCluster:localhost reversetunnel/agentpool.go:423
lines 1-20/20 (END)
/etc/teleport.yml:
version: v3
teleport:
nodename: ubuntu
data_dir: /var/lib/teleport
join_params:
token_name: 27fea99c04fa82e4fc953c36f469da7a
method: token
proxy_server: test.inno.com:443
log:
output: stderr
severity: DEBUG
format:
output: text
ca_pin: sha256:ed773b2fd1ce2f115c5b1cc4e3de956bb69e3a6912d2a1c78d3a7aeb2e27f493
diag_addr: ""
auth_service:
enabled: "no"
ssh_service:
enabled: "yes"
labels:
teleport.internal/resource-id: 9f9d847d-f117-400f-b8e9-998808b4843e
proxy_service:
enabled: "no"
https_keypairs: []
https_keypairs_reload_interval: 0s
acme: {}
my docker-compose.yml
version: '3'
services:
teleport:
image: public.ecr.aws/gravitational/teleport-distroless:16.4.3
volumes:
- ./teleport/data:/var/lib/teleport
- ~/teleport/certs:/etc/teleport/ssl
- ./teleport.yml:/etc/teleport/teleport.yaml
ports:
- "3080:3080"
- "3022:3022"
- "3023:3023"
- "3024:3024"
- "3025:3025"
expose:
- 80
environment:
VIRTUAL_HOST: test.inno.com
VIRTUAL_PORT: 3080
VIRTUAL_PROTO: https
LETSENCRYPT_HOST: test.inno.com
LETSENCRYPT_EMAIL: [email protected]
depends_on:
- letsencrypt-nginx-proxy-companion
nginx-proxy:
image: jwilder/nginx-proxy
ports:
- 80:80
- 443:443
volumes:
- /etc/nginx/vhost.d
- ./certs:/etc/nginx/certs
- /usr/share/nginx/html
- /var/run/docker.sock:/tmp/docker.sock:ro
letsencrypt-nginx-proxy-companion:
image: jrcs/letsencrypt-nginx-proxy-companion
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
volumes_from:
- nginx-proxy
and my teleport.yml
A Sample Teleport configuration file.
Things to update:
1. license.pem: Retrieve a license from your Teleport account https://teleport.sh
if you are an Enterprise customer.
version: v3
teleport:
nodename: localhost
data_dir: /var/lib/teleport
proxy_server: "tel-3.innovqube.com:3024"
log:
output: stderr
severity: DEBUG
format:
output: text
ca_pin: ""
diag_addr: ""
auth_service:
enabled: "yes"
listen_addr: 0.0.0.0:3025
proxy_listener_mode: multiplex
ssh_service:
enabled: "false"
proxy_service:
enabled: "yes"
public_addr: "https://test.inno.com:443"
tunnel_listen_addr: "0.0.0.0:3024"
web_listen_addr: "0.0.0.0:3080"
https_keypairs: []
https_keypairs_reload_interval: 0s
acme: {}
TLS certificate for the HTTPS connection. Configuring these properly is
critical for Teleport security.
https_key_file: /etc/teleport/ssl/test.inno.com/key.pem
https_cert_file: /etc/teleport/ssl/test.inno.com/fullchain.pem
Bug details:
Beta Was this translation helpful? Give feedback.
All reactions