search

BlueBubblesApp / bluebubbles-server

Server for forwarding iMessages to clients within the BlueBubbles App ecosystem
https://bluebubbles.app
Apache License 2.0
557 stars 47 forks source link

Zrok implementation not working #678

Open drsourcat opened 3 months ago

drsourcat commented 3 months ago

I don't know if it is me. but when adding Zrok as a proxy the server address stays locked on the default cloudflare address. The server then reports the following error: [ZrokService] Failed to restart Zrok! Error: [ERROR]: unable to create share (unable to create share: [POST /share][401] shareUnauthorized) I tried the pre-release version and the latest stable, uninstall/reinstall/reboot/reconnect. Thanks!

cameronaaron commented 3 months ago

Hey I have a fix for this that I might just pr in just do zrok enable plus your key and it will work

drsourcat commented 3 months ago

I have already tried to enter "zrok enable + token" in the CLI. it executes the command but the issue persists. Also tried to disable and re-enable.

ydanote commented 2 months ago

Hey I have a fix for this that I might just pr in just do zrok enable plus your key and it will work

Took a while to figure out, but I actually had to manually run a zrok disable and then again could successfully enable via the BlueBubbles GUI.

zlshames commented 2 months ago

Hey I have a fix for this that I might just pr in just do zrok enable plus your key and it will work

Took a while to figure out, but I actually had to manually run a zrok disable and then again could successfully enable via the BlueBubbles GUI.

Oh interesting. Good to know. Maybe I check for that error and run disable first? Or if I get that error, run disable then try again. I'll look into it

cameronaaron commented 2 months ago

Hey I have a fix for this that I might just pr in just do zrok enable plus your key and it will work

Took a while to figure out, but I actually had to manually run a zrok disable and then again could successfully enable via the BlueBubbles GUI.

Oh interesting. Good to know. Maybe I check for that error and run disable first? Or if I get that error, run disable then try again. I'll look into it

I think that is what fixed it for me as well