Teleport not working

[yostinso]

Is this a new Bug?

• I checked that the bug hasn't been reported before

Package Name

teleport

Package Version

v13.1.1

Device Model

x

Device Architecture

x86_64

Firmware Version

x

What happened?

See gravitational/teleport#4754 (comment)

Reproduction steps

see gravitational/teleport#4754 (comment)

Install Log

n/a

Service Log

No response

Other Logs

No response

[Gugatec]

Hi @yostinso

Thank you for your response

I can see that the service is running, also the teleport.yaml is create (although is version 2 and the other agents I installed is version 3).

Here is a little more info from the ps and some logging (honestly I don't know which log to look). I wish that there was something like "sudo journalctl -u teleport.service"

Let me know what else can I provide for further investigate it.

Cheers

Is this a new Bug?

• I checked that the bug hasn't been reported before

Package Name

teleport

Package Version

v13.1.1

Device Model

VirtualDSM - running on a DS220+

Device Architecture

x86_64

Firmware Version

7.1.1 update 6

What happened?

See gravitational/teleport#4754 (comment)

Either by using the precompiled release or compiling (used DSM 7.0 and 7.1, same results) the teleport_agent/spk doesn't connect. Teleport is running with elevated privileges

Reproduction steps

see gravitational/teleport#4754 (comment)

• Install on Synology Virtual DSM with firmware 7.1.1.upt6 on Synology VMM (mine is DS220+)
• Either use the yostinso precompiled spk 13.1.1 agent or use the one compiled by me/gugatec (dsm 7.0 and 7.1 tested)
• Using teleport server 13.1.1 issue tctl nodes add command and use the token and ca_pin info to configure SPK
• Issue sudo /var/packages/teleport/target/scripts/start on Synology ssh/shell to elevate privileges and restart SPK
• gugatec compiled spks https://drive.google.com/drive/folders/1cKp_Wbe8f8IBScLqgImDc3A_gzAsptCA?usp=sharing

Install Log

n/a

Service Log

No response

Other Logs

PS: (After booting)
root 20465 0.5 5.5 1442272 112808 ? Sl 09:00 0:02 /volume1/@appstore/teleport/bin/teleport start -c /var/packages/teleport/etc/teleport.yaml --pid-file=/volume1/@appdata/teleport/teleport.pid

(after synopkg stop teleport && synopkg start teleport)
SYSTEMD.LOG
2023-07-19T08:59:38+04:00 labarradsm systemd[1]: Reloading.
2023-07-19T09:00:15+04:00 labarradsm systemd[1]: Starting teleport's service unit...
2023-07-19T09:00:17+04:00 labarradsm systemd[1]: Reloaded Synology Schedule Daemon.
2023-07-19T09:00:17+04:00 labarradsm systemd[1]: Started teleport's service unit.
2023-07-19T09:00:17+04:00 labarradsm systemd[1]: Reloading.
2023-07-19T09:00:18+04:00 labarradsm systemd[1]: Stopping Synology Task Scheduler Vmtouch...
2023-07-19T09:00:18+04:00 labarradsm systemd[1]: Started Synology Task Scheduler Vmtouch.
2023-07-19T09:00:18+04:00 labarradsm systemd[1]: Starting Synology Task Scheduler Vmtouch...

SYNOSYSTEMD.LOG
2023-07-19T08:59:39+04:00 labarradsm synopkg[20013]: systemd_systemctl.cpp:219 synosystemd: Execute time for [/usr/bin/systemctl disable pkgctl-teleport.service] is 453 ms
2023-07-19T08:59:39+04:00 labarradsm synopkg[20013]: systemd_disable.cpp:25 synosystemd: [pkgctl-teleport.service] disabled.
2023-07-19T09:00:15+04:00 labarradsm synopkg[20430]: systemd_start.cpp:16 synosystemd: [pkgctl-teleport.service] starting ...
2023-07-19T09:00:17+04:00 labarradsm synosystemctl[20492]: systemd_reload.cpp:17 synosystemd: [synoscheduled] reloading ...
2023-07-19T09:00:17+04:00 labarradsm synosystemctl[20492]: systemd_reload.cpp:21 synosystemd: [synoscheduled] reloaded.
2023-07-19T09:00:17+04:00 labarradsm synopkg[20430]: systemd_start.cpp:20 synosystemd: [pkgctl-teleport.service] started.
2023-07-19T09:00:17+04:00 labarradsm synopkg[20430]: systemd_enable.cpp:17 synosystemd: [pkgctl-teleport.service] enabling ...

[Gugatec]

Regarding my knowledge on teleport, synology and *nix overall.

I would say that I'm between a power user and an engineer. I'm actually a IT project manager professionally. So my skills are not super advanced but I can do quite a lot in technical stuff.

I'm also just recently started with teleport, so my knowledge base is quite shallow in that regard.

My teleport cluster has two other agents, one in ubuntu that I used the teleport auto-generated script and the other is instaled manually on oracle linux that is the host of the teleport container, both show on the WEB UI as "tunnel".

I also tried the v3 format of teleport.yaml on the virtual dsm synology, but got the same result (no connection)

My teleport server has the ports 443 and 3080 as the proxy and I have the ports 3023, 3024 and 3025 opened (I'm still figuring out what does what on each of teleport services)

The main reason to provide you with this background is trying to narrow down what could be the issue, I'm assuming that is everything fine with teleport server.

I saw that teleport can connect in different ways, but didn't completely digest/understood it all so far.

Is the teleport spk connection type (tunnel) as well ?

Cheers