I've cloned and run the web repo and can access the vault in my browser fine. But, I'm trying two things. 1. Connecting the frontend to the production Bitwarden servers. 2. Connecting the frontend to my own vaultwarden instance (behind a reverse-proxy). In either case, changing the ENV variable (when running npm) does not change the baseURL that requests are made from. Thus I'm getting these errors in the browser terminal (see image).
Yes. I've tried
ENV=production npm run build:oss:watch as per the docs as well.
when you first run the npm script, you should see a printout of the loaded config, can you confirm it's loading your proxy settings correctly?
But if we ignore my vaultwarden setup (since that might come with other issues), just connecting to bitwarden cloud is not working.
As per the Github README
our devops team didn't like
production since that's ambiguous between cloud and self-hosted users
The baseURL for all requests are still
localhost:8080
@MGibson1 I think we forgot to setup the proper proxies in production after https://github.com/bitwarden/web/pull/1151/files
@fredrikburmester I think if you add the following to .config/local.json thing should start working
This is now my envConfig that I get in the terminal:
envConfig
{
"urls": {
"icons": "https://icons.bitwarden.net",
"notifications": "https://notifications.bitwarden.com",
"enterprise": "https://portal.bitwarden.com"
},
"stripeKey": "pk_live_bpN0P37nMxrMQkcaHXtAybJk",
"braintreeKey": "production_qfbsv8kc_njj2zjtyngtjmbjd",
"paypal": {
"businessId": "4ZDA7DLUUJGMN",
"buttonAction": "https://www.paypal.com/cgi-bin/webscr"
},
"proxyApi": "https://api.bitwarden.com",
"proxyIdentity": "https://identity.bitwarden.com",
"proxyEvents": "https://events.bitwarden.com",
"proxyNotifications": "https://notifications.bitwarden.com",
"proxyPortal": "https://portal.bitwarden.com"
}
But I still get the same error in the browser console
ah, the proxies don't start unless
ENV == development I think we've made a catch-22 here
try just copying that envConfig to
local.js and running with ENV=development
that way we force all the config we want but still start up the devServer
that works for me :fingers crossed:, how about you?
:D
I don't know much here so please correct me if i'm wrong... But the cloud config should include those proxyApi's right, or is it used for something else? And we should change to the correct ENV variable. If the config looked like that when i cloned the repo then it would have worked.
hello.. has there been a change to accessing the API for the official instance? noticed that ofr the last few days I am unable to log into my account via a cli application that I use (rbw).. getting a request returned error 400. Is this related? [bitwarden/server#1626]
since it was recently merged, guessing it will take a little while for it to go live
Hi there, our mobile app is written in C# using Xamarin Forms. The source code and documentation is available here: https://github.com/bitwarden/mobile.
2 replies
I want to search on the value of the password, rather than the site name or whatever.