This isn’t a question, it’s more for search engines to pick up.
When I did pretty much anything with the Bitwarden CLI on Linux, I was getting the following error:
Unable to fetch ServerConfig from https://api.bitwarden.com FetchError: request to https://api.bitwarden.com/config failed, reason:
at ClientRequest.<anonymous> (/snapshot/clients/node_modules/node-fetch/lib/index.js:1505:11)
at ClientRequest.emit (node:events:518:28)
at emitErrorEvent (node:_http_client:104:11)
at TLSSocket.socketErrorListener (node:_http_client:518:5)
at TLSSocket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT'
}`
The error was popping up instantly, not after a timeout.
Eventually I tried running bw config server. This gave the output https://bitwarden.com (and then the same ETIMEDOUT error).
This appears to be the URL used by an old version of the client that was persisting in the config. I ran bw config server https://vault.bitwarden.com/ and now the error message no longer comes up.