Cloud Sync [Bug]

[Chammar37]

📦 Environment

• Official
• Official Preview
• Vercel / Zeabur / Sealos
• Docker
• Other

📌 Version

v0.162.21

💻 Operating System

• Windows
• macOS
• Ubuntu
• Other Linux
• iOS
• Android
• Other

🌐 Browser

• Chrome
• Edge
• Safari
• Firefox
• Other

🐛 Bug Description

The cloud sync was working for a while, syncing with multiple computers and then all of sudden it stopped working and i lost my lists/topics/chats on other computers, saying 'Cloud Sync Failed'.

I've tried to re-create another channel with a different name, the sync says 'Connected' although I don't see topics/chats from my other computer.

Is there a better way of making the 'shared chats' use case more reliable with WebRTC Sync? Is there coming releases to fix these issues?

Thank you!

📷 Recurrence Steps

Adding 'Sync Channel Name' and 'Sync Channel Password', clicking Enable Sync.

Connecting other computers with same name/password

🚦 Expected Behavior

To see all the same Lists, Topics and Chats from my other computer on the lobechat UI

📝 Additional Information

No response

[lobehubbot]

👀 @Chammar37

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[cogscides]

Same for me. Sync functionality disappeared and then I enabled it via flags. Now it's not syncing. It displays "Connection Failed" and here is the console log outputs:

WebSocket connection to 'wss://y-webrtc-signaling.lobehub.com/' failed: 
o @ 70065.4eb3154cdab79e5d.js:1
---
70065.4eb3154cdab79e5d.js:1 WebSocket connection to 'wss://y-webrtc-signaling.lobehub.com/' failed: WebSocket is closed before the connection is established. 
disconnect @ 70065.4eb3154cdab79e5d.js:1

[9Somboon]

I think the feature might be discontinued in the community version. To be an important feature for subscription users on the lobehub website.

[cogscides]

To be an important feature for subscription users on the lobehub website.

Very sad to hear that as at the moment community self-hosted version lack any options to sync except Vercel stack.

[arvinxx]

@cogscides @9Somboon we don't remove it. You still can enable it with Feature Flag https://lobehub.com/docs/self-hosting/advanced/feature-flags

[cogscides]

@cogscides @9Somboon we don't remove it. You still can enable it with Feature Flag https://lobehub.com/docs/self-hosting/advanced/feature-flags

I enabled it, and I see it in UI. But I got errors in the console:

#2842 (comment)

[cogscides]

Can we have a WEB_RTC_SIGNALING_URL specified in the environment so we can host the signaling container?

[cogscides]

Are there any updates on this? It makes the self-hosted version useless as we haven't any other convenient sync options. As far as I know, server db isn't yet implemented for self-hosted option.

[lobehubbot]

✅ @Chammar37

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题，可以留言并回复。

[lobehubbot]

🎉 This issue has been resolved in version 1.3.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[cogscides]

Discussion on how to setup WebRTC sync for lobe-chat: #3192