How change bitwarden server

[Lozbik]

I am using a self-hosted Bitwarden server. I have configured the CLI locally using bw config server https://my-server, and it works correctly in my terminal.
However, when I select Bitwarden in XPipe settings and press "Sync", it does not work. XPipe opens a new terminal window and asks for credentials to connect to vault.bitwarden.com (the cloud version), ignoring my self-hosted configuration.
I tried to find a solution in the documentation but couldn't find anything. I also attempted to set the environment variable export BW_URL="https://my-server", but that did not help either.
Could you please advise on how to force XPipe to use my custom server URL?

[crschnick]

I am confused, this should already work.

XPipe copies the bw config file to its cache to prevent concurrent modifications. Can you check whether the file ~/.xpipe/cache/data.json contains the selfhosted data for your server like this?

[Lozbik]

I have something like it in this file:

And compare this file with ~/.config/Bitwarden\ CLI/data.json there are different. In ~/.config/Bitwarden\ CLI/data.json i also have a section [global_config_byServer][https://api.bitwarden.com] but below there is another section [global_config_byServer]["https://my-server/"]. Maybe Xpipe starts with some another user?

[crschnick]

XPipe should automatically replace the cache data.json by the Bitwarden .config one if the file modified timestamp is newer. Can you check whether that works? If it does do that, the behaviour in the terminal and xpipe should be identical

[Lozbik]

I checked, and the timestamps are different. ~/.xpipe/cache/data.json is 2 minutes newer than ~/.config/Bitwarden CLI/data.json. Here are the steps I took yesterday:

1. Set up the bw server
2. Ran bw login
3. Started xpipe
4. Pressed sync
   I think this 2-minute difference occurred between the bw login and press sync steps.

[crschnick]

Can you try deleting the cache data.json file and try again?

[Lozbik]

Okay, I attempted the steps, but received a "No such file" error. After clicking OK, the terminal opens and initiates authentication with the Bitwarden servers, behaving exactly as before.
I also inspected the file contents. It appears that ~/.xpipe/cache/data.json does not reflect the data from ~/.config/Bitwarden CLI/data.json.

This might be helpful: when connecting to a remote host, if I get the "Remote host identification has changed" error, I cannot resolve it through the application. I have to manually run a command in the terminal to fix it. If I just retry in the app, the error simply reappears.

[crschnick]

Can you copy the stack trace for the nosuchfile exception? That is probably causing this issue

[crschnick]

Ahh wait, I think I found it

[crschnick]

Give it 30mins, then you can try a PTB build that should fix it

[crschnick]

Alright, can you try whether https://github.com/xpipe-io/xpipe-ptb now copies the data file correctly?

Note that for the PTB, the directory is ~/.xpipe-ptb

[Lozbik]

Sorry for the delay. I checked the PTB version — Bitwarden works perfectly!