when manually re-entering new server URL, it reverts back to the old one

[bluebubbles-copilot]

when firebase is enabled. This happens when firebase's server URL does not match the server. Which likely means there was an issue setting the URL

Issue Metadata

• User: @zach.shames#0
• Context: https://discord.com/channels/640229510662455326/746560644995612752/1262110317035524251

[zlshames]

This issue is linked to this comment: #2773 (comment)

[Raptor-TK]

I also get this unwanted replacement of the url to the old one when i try to connect from a remote linux to localhost using ssh port forwarding to the bluebubbles server (forwarding from my localhost port to the remote server) while the firebase is set to a different url.

I dont want to remove the url from firebase because other clients that don't need port forwarding are using it.

Setup:
Firebase URL: "http://192.168.x.x:1234"
Remote Linux client using url "http://localhost:1234" → localhost → port forwarding → bluebubbles server
Phone client using url "http://192.168.x.x:1234"→ private vpn → local ip of bluebubbles server

Can we have a setting to ignore replacing the server url with the firebase url once we connect to the server?

[zlshames]

I also get this unwanted replacement of the url to the old one when i try to connect from a remote linux to localhost using ssh port forwarding to the bluebubbles server (forwarding from my localhost port to the remote server) while the firebase is set to a different url.

I dont want to remove the url from firebase because other clients that don't need port forwarding are using it.

Setup: Firebase URL: "http://192.168.x.x:1234" Remote Linux client using url "http://localhost:1234" → localhost → port forwarding → bluebubbles server Phone client using url "http://192.168.x.x:1234"→ private vpn → local ip of bluebubbles server

Can we have a setting to ignore replacing the server url with the firebase url once we connect to the server?

So all the clients use the 192.x.x.x LAN IP, except for one client, that uses localhost. I'm not exactly following how a localhost connection is going through port forwarding? Wouldn't you be connecting over a public IP if you're using port forwarding? Or a dynamic DNS

[Raptor-TK]

It's tunneling the bluebubbles http traffic in an encrypted ssh connection.

The openssh port forwarding is connecting to a public dynamic dns to a server in my home network via ssh. I also specify the port mapping as part of the connection parameters. In my case I map it so that openssl listens locally on the client side on localhost:1234 then forwards the traffic through the encrypted tunnel to the 192.168.x.x:1234 inside that remote server's private network.

To bluebubbles client, it just connects to http://localhost:1234 and all traffic is then forwarded to and from the bluebubbles server that is on the remote server's network at 192.168.x.x:1234.

I hope this use case makes sense.

[bronson]

I'm getting bit by this too. Other clients are happy, except Android keeps insisting on using the wrong URL and breaking.

I don't undersand why the Android client would even accept the URL from FireBase? I'm giving it the correct URL to use, so use that. Why second-guess me?

[zlshames]

I'm getting bit by this too. Other clients are happy, except Android keeps insisting on using the wrong URL and breaking.

I don't undersand why the Android client would even accept the URL from FireBase? I'm giving it the correct URL to use, so use that. Why second-guess me?

It just means that your server URL stored in firebase doesn't match what you entered. Essentially, your server failed to update the server URL in firebase. Check your server notifications/alerts. Otherwise restart your server and see if that may fix your issue.

[bronson]

I now understand why BlueBubbles wants to download the URL from FireBase... Sometimes the server needs to update the URL, and this is the way it pushes the new URL out to the clients.

In my case, restarting a few times and waiting for a day seemed to restore my working system for almost a month.

[zlshames]

I now understand why BlueBubbles wants to download the URL from FireBase... Sometimes the server needs to update the URL, and this is the way it pushes the new URL out to the clients.

In my case, restarting a few times and waiting for a day seemed to restore my working system for almost a month.

This is correct, however, you shouldnt need to wait a day. The only reason that a custom URL will revert to the old one is if the Firebase database doesn't have the new address in it. Which means that the server was unable to update it in the DB. That may be due to a DNS/networking issue on your server, or another reason (maybe a bug?). Restarting the server will give you a new URL, but may not solve the issue of updating the URL in the Firebase database.

It definitely shouldn't take a day to update the firestore DB. When you get a new URL, it should update nearly immediately.