No connection to RasberryPi console after update

After an update of TeamViewer (to version 15.10.5 H) I am not able to connect to my (headless) RaspberryPi in "console mode" anymore. When booting into the "desktop mode" there is no problem establishing the TeamViewer connection.

Problem: RaspberryPi boots into "console mode", internet connection is establised and also TeamViewer is running. On my client PC the device is shown in the device list as normal. If I try to connect it says "connecting" for some seconds (30-60) and than stops with no error. When booting the Raspberry into "desktop mode" everything works fine.

System information:

Hardware: Raspberry Pi 3 Model B+

Operating System: Raspbian GNU/Linux 9 (stretch)

Kernel: Linux 4.19.66-v7+

TeamViewer Version: 15.10.5 H

Find more posts tagged with

Linux

Debian

Issue

TeamViewer 15

Comments

Knutowskie

Same here. Upgraded my headless pi and same issue.

2020/11/29 13:30:44.260 2471 **Please do not post TeamViewer IDs** S ConnectionGuard: incoming remote control in sessions: **Please do not post TeamViewer IDs**(1)
2020/11/29 13:30:44.293 2471 **Please do not post TeamViewer IDs** S Negotiating session encryption: client hello received from **************, RSA key length = 2048
2020/11/29 13:30:44.293 2471 **Please do not post TeamViewer IDs** S Negotiating session encryption: client hello received from **************, RSA key length = 2048
2020/11/29 13:30:44.335 2471 **Please do not post TeamViewer IDs** S Negotiating session encryption: server hello sent
2020/11/29 13:30:44.370 2471 **Please do not post TeamViewer IDs** S Negotiating session encryption: client handshake received
2020/11/29 13:30:44.370 2471 **Please do not post TeamViewer IDs** S Negotiating session encryption: client handshake received
2020/11/29 13:30:44.440 2471 **Please do not post TeamViewer IDs** S Negotiating session encryption: server handshake sent, encryption established with AES key length 256
2020/11/29 13:30:44.440 2471 **Please do not post TeamViewer IDs** S NegotiateEncryptionV2::CreateEncryption: handshake successful, local fingerprint: SHA256:**************, remote fingerprint SHA256:**************
2020/11/29 13:30:50.506 2471 **Please do not post TeamViewer IDs** S HandleSigChld: Child exited: 2556 exit code 1
2020/11/29 13:30:50.506 2471 **Please do not post TeamViewer IDs** S ProcessControlBase[4]: Process 2556 in session ************** has terminated
2020/11/29 13:30:58.182 2471 **Please do not post TeamViewer IDs** S Estimated RTT to Router: 14 ms, Reliability: 3, Carrier: 1
2020/11/29 13:31:00.138 2471 **Please do not post TeamViewer IDs** S Estimated RTT to **Please do not post TeamViewer IDs**: 13 ms, Reliability: 3, Carrier: 1
2020/11/29 13:31:01.138 2471 **Please do not post TeamViewer IDs** S Estimated RTT to **Please do not post TeamViewer IDs**: 14 ms, Reliability: 3, Carrier: 1

nicolasr75

I think I have the exact same problem. Two IDs and when a user runs a graphical session, everything works fine. Without it, the attempt to connect times out. Here are a few snippets from my log file that may be of interest. Of course it doesn't mean, your log looks the same!

2020/11/02 23:25:11.058 1176 ********* S CommandHandlerRouting[2]::CreatePassiveSession(): incoming session via DE-NUR-ANX-R004.teamviewer.com, protocol Tcp
2020/11/02 23:25:13.722 1176 ********* S CTcpConnectionBase[2]::ConnectEndpoint(): Connecting to endpoint 2a00:11c0:77:351:94:16:6:167:5938
2020/11/02 23:25:13.740 1176 ********* S DesktopProcessStarterLinux::StartSystemProcessInSession(**Please do not post TeamViewer IDs**,/opt/teamviewer/tv_bin/TeamViewer_Desktop)
2020/11/02 23:25:13.820 1176 ********* S XClient[:0]: Unable to open XAuthority file "/var/run/lightdm/root/:0" (err=13)
2020/11/02 23:25:13.830 1176 ********* S DesktopProcessStarterLinux: user for process launch: root (0)
2020/11/02 23:25:13.831 1176 ********* S XClient[:0]: Unable to open XAuthority file "/var/run/lightdm/root/:0" (err=13)

...

2020/11/02 23:25:20.146 1176 ********* S HandleSigChld: Child exited: 1267 exit code 1
2020/11/02 23:25:20.146 1176 ********* S ProcessControlBase[4]: Process 1267 in session **Please do not post TeamViewer IDs** has terminated
2020/11/02 23:25:29.183 1176 ********* S Estimated RTT to ********: 19 ms, Reliability: 3, Carrier: 1
2020/11/02 23:25:29.205 1176 ********* S Estimated RTT to Router: 17 ms, Reliability: 3, Carrier: 1
2020/11/02 23:25:30.186 1176 ********* S Estimated RTT to **Please do not post TeamViewer IDs**: 18 ms, Reliability: 3, Carrier: 1
2020/11/02 23:25:54.793 1176 ********* S CMachineStatus::PerformBasicChecks(): No changes in local monitor status to send to provider
2020/11/02 23:26:54.793 1176 ********* S CMachineStatus::PerformBasicChecks(): No changes in local monitor status to send to provider
2020/11/02 23:27:45.981 1176 ********* S Estimated Bandwidth Capacity to **Please do not post TeamViewer IDs**: 87117 kbit/s, Reliability: 3, Carrier: 1
2020/11/02 23:27:52.797 1176 ********* S Estimated Bandwidth Capacity to ********: 57997 kbit/s, Reliability: 3, Carrier: 1
2020/11/02 23:30:11.152 1176 ********* S Carrier[2]::CmdEndSession(): Received CMD_ENDSESSION with reason: AuthenticationTimeout
2020/11/02 23:30:11.171 1176 ********* S ConnectionGuard: no restrictions

olympus593

I have the same issue.

What's even weirder is that I got 2 different IDs, one for console, other for the teamviewer host GUI application. Neither works, even though both show as online.