teleport-update enable error

[alanxie1986]

ERROR REPORT:
Original Error: *errors.errorString Teleport proxy URL must be specified with --proxy or present in update.yaml
Stack Trace:
github.com/gravitational/teleport/lib/autoupdate/agent/updater.go:728 github.com/gravitational/teleport/lib/autoupdate/agent.(*Updater).find
github.com/gravitational/teleport/lib/autoupdate/agent/updater.go:363 github.com/gravitational/teleport/lib/autoupdate/agent.(*Updater).Install
github.com/gravitational/teleport/tool/teleport-update/main.go:340 main.cmdInstall
github.com/gravitational/teleport/tool/teleport-update/main.go:197 main.Run
github.com/gravitational/teleport/tool/teleport-update/main.go:64 main.main
runtime/proc.go:272 runtime.main
runtime/asm_amd64.s:1700 runtime.goexit
User Message: Teleport proxy URL must be specified with --proxy or present in update.yaml] teleport-update/main.go:224

If I add the --proxy parameter after teleport-update enable, what is this address? How should I upgrade?

[alanxie1986]

root@TelePort:~# tctl status
Cluster: teleport.xxxxx.net
Version: 17.2.7
CA pins: sha256:f0284c19527dad2d3f986439de83527c1d987b1c174df5ab422f8e63161f074d

authority rotation protocol status algorithm storage

---

host standby (never rotated) SSH active Ed25519 software
TLS active ECDSA P-256 software
user standby (never rotated) SSH active Ed25519 software
TLS active ECDSA P-256 software
db standby (never rotated) TLS active RSA 2048 software
db_client standby (never rotated) TLS active RSA 2048 software
openssh standby (never rotated) SSH active Ed25519 software
jwt standby (never rotated) JWT active ECDSA P-256 software
saml_idp standby (never rotated) TLS active RSA 2048 software
oidc_idp standby (never rotated) JWT active RSA 2048 software
spiffe standby (never rotated) JWT active RSA 2048 software
TLS active ECDSA P-256 software
okta standby (never rotated) JWT active ECDSA P-256 software

I want to upgrade to the latest version

[PeterPan1994]

I faced the same issue. The AI at teleport it's website also didn't know something about the mentioned config-file "update.yaml". But I was successful able to enable the update-function with:

sudo teleport-update enable --proxy teleport.MyDomain.com

"teleport.mydomain.com" is the exact URL I enter if I want to connect from external to my teleport WebUI. Hope this helps you.

[webvictim]

teleport-update enable assumes that a Teleport configuration file is located at /etc/teleport.yaml and the proxy address to use can be read from it. This is because in most cases people are attempting to enable managed updates on a server which already has Teleport configured.

As noted already, if you don't have a config file in place, you can run teleport-update enable --proxy teleport.example.com (replacing this with your own Teleport domain)