-
|
I have installed Teleport and am now trying to connect a Debian machine. I have installed the client but the Teleport instance does not recognize the client. 
Teleport is behind a reverse proxy. I have tried it both through Cloudflare Tunnels and through the Nginx reverse proxy, but it doesn't work with either. Here my server config: ---
version: v2
teleport:
nodename: skyt81
data_dir: /var/lib/teleport
log:
output: stderr
severity: INFO
format:
output: text
auth_service:
enabled: true
listen_addr: 0.0.0.0:3025
proxy_listener_mode: multiplex
cluster_name: your-server-url
ssh_service:
enabled: true
labels:
ressource: vm
proxy_service:
enabled: true
web_listen_addr: 0.0.0.0:3080
# -- (Optional) when using reverse proxy
public_addr: ['teleport.myserver.me:443']
https_keypairs: []
acme: {}
app_service:
enabled: false
# -- (Optional) App Service
# enabled: trueHere is my Client Config (Auto generated): version: v3
teleport:
nodename: skyv26
data_dir: /var/lib/teleport
join_params:
token_name: 68cc5b7xxxxxxxxxxxx
method: token
proxy_server: teleport.myserver.me:443
log:
output: stderr
severity: INFO
format:
output: text
ca_pin: sha256:41459b06460db9cxxxxxxxxx
diag_addr: ""
auth_service:
enabled: "no"
ssh_service:
enabled: "yes"
labels:
teleport.internal/resource-id: 55122314-2f74-4143-ba11-e86bb2a3b445
proxy_service:
enabled: "no"
https_keypairs: []
https_keypairs_reload_interval: 0s
acme: {}Here is the Client Status: And here are the server logs when trying to connect the agent: I hope someone can help me with that :) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 14 replies
-
|
typically the issue is that it's not allowing multiplex traffic to go through. This likely only allows https traffic. Please see https://goteleport.com/docs/reference/architecture/tls-routing/ for a description of the traffic needed. |
Beta Was this translation helpful? Give feedback.
-
Yeah this is the output:
No i can't find any node there. |
Beta Was this translation helpful? Give feedback.
-
|
OK, this looks like a Teleport RBAC/permissions problem rather than a connectivity problem. Can you take a screenshot of your user entry in the web UI (under Access -> Users) which shows the roles that your user has assigned, and then share this along with the output of |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
The You should also assign the |
Beta Was this translation helpful? Give feedback.
-
|
Yeah i can see them now. Thank you! It now says if i click on Connect (Search Logins...). Shouldn't this work directly since the client is installed? |
Beta Was this translation helpful? Give feedback.
-
|
You need to add a login that you can use on the servers, then log out and log back in again: #11820 (comment) You can also edit this under the "Users" section in the web UI (same place you added the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, I somehow didn't understand it all although I have read up on it. Is there a guide for beginners somewhere that covers the most important things? |
Beta Was this translation helpful? Give feedback.
-
|
Glad things are working for you now! This guide is a good starter for how to get a server enrolled and access set up to it: https://goteleport.com/docs/enroll-resources/server-access/getting-started/ There is also a getting started guide for Teleport RBAC here: https://goteleport.com/docs/admin-guides/access-controls/getting-started/ |
Beta Was this translation helpful? Give feedback.
-
|
One other thing to check: have you customised the RBAC on your Teleport server at all? Do you have any |
Beta Was this translation helpful? Give feedback.
-
The config files above is everything i did. I'm using Docker to deploy the Teleport Server: services:
teleport:
image: public.ecr.aws/gravitational/teleport-distroless:17.2.1
container_name: teleport
restart: always
volumes:
- /docker/teleport/data:/var/lib/teleport
- /docker/teleport/config:/etc/teleport
ports:
- "3080:3080" |
Beta Was this translation helpful? Give feedback.
The
editorrole only grants you the right to edit roles, permissions etc on the cluster - it doesn't grant any user access to servers or resources.You should also assign the
accessrole to your user (using the "Edit" link next to the user) then log out and back in again. This should then show resources you can access.