Teleport desktop service issue with LDAP #51353
Unanswered
rajsardhara
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
-
I have suddently started getting below error for Windows Desktop service, This is not new setup, It has been working fine for few months.
Jan 22 09:30:12 teleport[76852]: github.com/gravitational/teleport/lib/service/supervisor.go:588 github.com/gravitational/teleport/lib/service.(*LocalService).Serve Jan 22 09:30:12 teleport[76852]: github.com/gravitational/teleport/lib/service/supervisor.go:313 github.com/gravitational/teleport/lib/service.(*LocalSupervisor).serve.func1 Jan 22 09:30:12 teleport[76852]: runtime/asm_amd64.s:1695 runtime.goexit Jan 22 09:30:12 teleport[76852]: User Message: updating CRL over LDAP Jan 22 09:30:12 teleport[76852]: creating CRL container Jan 22 09:30:12 teleport[76852]: error creating LDAP object "CN=Teleport,CN=CDP,CN=Public Key Services,CN=Services,CN=Configuration,DC=*****,DC=com" Jan 22 09:30:12 teleport[76852]: the LDAP server did not accept Teleport's client certificate, has the Teleport CA been imported correctly?] desktop/windows_server.go:383 Jan 22 09:30:12 teleport[76852]: 2025-01-22T09:30:12-05:00 INFO [WINDOWS_D] Starting Windows desktop service via proxy reverse tunnel. pid:76852.1 service/desktop.go:252 Jan 22 09:30:12 teleport[76852]: 2025-01-22T09:30:12-05:00 INFO [PROC:1] The new service has started successfully. Starting syncing rotation status. pid:76852.1 max_retry_period:4m16s service/connect.go:700 Jan 22 09:30:27 teleport[76852]: 2025-01-22T09:30:27-05:00 WARN [WINDOWS_D] skipping desktop discovery: LDAP not yet initialized pid:76852.1 desktop/discovery.go:101
I've already validated below:
Teleport Setup:
Multiple Auth and proxy instances running behind proxy.
Beta Was this translation helpful? Give feedback.
All reactions