is not a socket

[zhangwanlong]

PS C:\Users\030T0029> telepresence connect
Launching Telepresence User Daemon
Launching Telepresence Root Daemon
telepresence connect: error: connector.Connect: "C:\Users\030T0029\AppData\Local\telepresence\rootd.socket" is not a socket

[cindymullins-dw]

What version of Telepresence are you using? Could you please try ‘telepresence quit -s’ and then try to connect again with ‘telepresence connect’ and let us know if you get the same error.

[zhangwanlong]

抱歉还是无法访问

…

------------------ 原始邮件 ------------------ 发件人: "telepresenceio/telepresence" ***@***.***>; 发送时间: 2023年5月23日(星期二) 凌晨1:49 ***@***.***>; ***@***.******@***.***>; 主题: Re: [telepresenceio/telepresence] is not a socket (Issue #3191) What version of Telepresence are you using? Could you [lease try ‘telepresence quit -s’ and then try to connect again with ‘telepresence connect’ and let us know if you get the same error. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[lchkid]

Same problem

win10 1809 (17763.316)

telepresence.exe version
Client : v2.14.0
Root Daemon: not running
User Daemon: not running

telepresence connect
Launching Telepresence User Daemon
Launching Telepresence Root Daemon
telepresence connect: error: connector.Connect: "C:\Users\Administrator\AppData\Local\telepresence\rootd.socket" is not a socket

[cindymullins-dw]

If you could try removing the socket with sudo rm /var/run/telepresence-daemon.socket?

[lchkid]

If you could try removing the socket with sudo rm /var/run/telepresence-daemon.socket?

That was a windows device, so there was no such directory.

We finally switched to working on a mac device.

[cindymullins-dw]

@zhangwanlong , could you share your Telepresence logs so we can see where this error is originating?

[thallgren]

This is related to golang/go#33357. The fix (from July last year) has not been merged yet. We should add a workaround.

[ChrisWalkerNGC]

I'm seeing this issue too.

Env: Windows 10 Enterprise.

[thallgren]

@ChrisWalkerNGC I'm trying to reproduce this on a Windows 10 Enterprise without success. Perhaps Microsoft fixed this bug? What version are you on? I'm using version 22H2.

[thallgren]

@zhangwanlong @lchkid @ChrisWalkerNGC, I'm inclined to close this ticket as a won't-fix, because I think the root cause is a bug in older versions of Windows 10 Enterprise. Can you please try and upgrade your Windows and check if the problem persists?

[mattiasclaesson]

Same issue on...
Windows 10 Pro
Version: 1903
OS build 18362.900

using telepresence version
Client : v2.15.1
Root Daemon: not running
User Daemon: not running

Tried to remove the file with 0 size, but no difference.

[thallgren]

@mattiasclaesson can you please try and upgrade your Windows 10 Pro to a later version and see if the problem persists? I'm not able to reproduce with 22H2.

[mattiasclaesson]

@mattiasclaesson can you please try and upgrade your Windows 10 Pro to a later version and see if the problem persists? I'm not able to reproduce with 22H2.

I think this hardware will be replaced in a few months, will not upgrade as its running out of disk already.

[cindymullins-dw]

Closing as it appears this issue has already been addressed by Microsoft, in which case additional workarounds on the Telepresence side would quickly become out of date.