-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Issue - "Failed To Connect" and Socket Connection error #687
Comments
Exactly the same issue need help. Since yesterday so annoying. |
I was having the same issue, and I think it's related to Cloudflare. I also deleted the app and was getting the same connection error when trying to set it back up. I took a few minutes and set the server up using port forwarding and the dynamic DNS option just for trial purposes, and I seem to be back up and running as usual again. |
Also started happening to me in the last day. But it still actually works. It just annoyingly keeps giving this notification. |
I wish I hadn’t deleted the app 😅 Interesting to see I’m not the only one having this issue. I can collect logs if it’s helpful. |
Everyone, please switch your server proxy to Zrok or set up a self-hosted solution like Tailscale. Zrok setup is extremely easy:
Your server should now show a zrok URL and your client should pick that up. |
@tneotia I had recommended to Zach that we switch to Zrok by default. Cloudflare tunnels by default both changes a lot and also can be easily deprioritized not to mention that you cannot send large videos. What are your thoughts on making that change |
I first witnessed this happening today. Server has been running fine for a few weeks now.
First, there was an issue sending a message, and I got the notification on my Android device "Could not connect - Your server may be offline!". In the settings panel of the BlueBubbles app on Android I see a socket connection error:
. Strange, so I went to manually reboot my Mac and see if that helped.
When I did the reboot, I noticed that the message that I was trying to send earlier actually did go through (it showed in the Mac Messages app). After reboot, I got the same "Could not connect" notification and socket connection error.
While this was all happening, I could actually continue to send and receive messages as if nothing was wrong. Thought the error message would fix itself and go away after a few hours but it didn't so I:
Any ideas what might be going on? Could my ISP be messing things up with the server? Thanks, all help is much appreciated.
The text was updated successfully, but these errors were encountered: