Hi,
I just installed BitSailor to my fresh Sailfish OS and went all fine.
I host my own server for Bitwarden and so i try to login with the custom url option.
When i use the API or Email & Password i get a an authentication error. I can login with my iphone and webbrowser just fine. How can i throubleshoot this?
Kind regrads,
Robin
PS, im kinda new to Sailfish OS.
Thatās a tough one.
Basically the app is a proxy for the official Bitwarden CLI, so you might try whether it works for you when you log in from CLI?
The command the app uses:
bw login [email] [password] --raw
or
BW_CLIENTID=[clientId] BW_CLIENTSECRET=[clientSecret] bw login --apikey
The bw (if you installed it through the app) is located at:
~/.local/share/harbour-bitsailor/harbour-bitsailor/bin/bw (Iām not 100% sure about the bin/bw part but if itās wrong, it should be easy to find it in the directory).
I got it to work, but it all feels very slow. I use. Xperia 10 lll, but compared to my iphone 14 its losing by a mile.
(I have this with most of Sailfish OS tbh)
Fresh install latest Sailfishos Jolla C2.When i try to log in, the API or Email & Password i get an authentication error.Did cleanup and reinstalled app.After reboot no success.Any advice?
Try switching to the experimental api in settings, that should help
See my previous message: BitSailor support thread - #64 by Rikudou_Sennin
Hi, first of all, thank you for your great contribution to both the Bitwarden and SailfishOS community.
I desperately need bitwarden to definitely switch to SailfishOS, but the latest version does not seem to work on SailfishOS 5.0.0.72 (on a Sony Xperia 10 V).
When using the file browser to install harbour-bitsailor-0.4.7-1.aarch64.rpm , an error shows up:
āProblem with installingā
without further explaination.
Could you please look into this, or help me understand if I did anything wrong?
Thank you for your help.
This is probably because youāre trying to install it using the file browser - it cannot pull some of its dependencies like that.
If you really want to install like that, you will need to install node.js first: node.js | OpenRepos.net ā Community Repository System (choose the newest file for aarch64).
Afterwards, installing BitSailor should work.
But the recommended way to install it is using Storeman: Storeman Installer | OpenRepos.net ā Community Repository System
Download the latest version of the installer and then you can install every app from OpenRepos through it.
Hi @Rikudou_Sennin , thank you so much for the App!
Iāve installed a fresh self-hosted Vaultwarden on my home NAS, which I can access from my local network using my browser. The idea is to only have local access.
Howeve, using BitSailor, I seem to have similar access issue than Mikkoj and Graxo using custom url. Iāve generated a self-signed certificate and used the bw cli youāve providedā¦seems that fetch error is related to that. Is Bitsailor not supporting self-signed certs?
FetchError: request to https://ā¦/identity/connect/token failed, reason: self-signed certificate
It doesnāt, I havenāt added support for that. Canāt you make your certificate trusted on the system level? That should probably make it trusted for BitSailor as well.
I can take a look into supporting self-signed certificates on the app level, but IMO it would be much faster if you trusted the certificate on the OS level.
I believe this is what Iāve already tried but it did not seem to be āacceptedā by NodeJS (??) since it is not using a trusted/known CA (added the cert under /etc/pki/ca-trust/source/anchors/ and launched update-ca-trust extract+ reboot).
I tested the bw cli after exporting NODE_TLS_REJECT_UNAUTHORIZED=0 , which allowed me to log in.
But itās a bit dirty hack ā¦
Well, added two options to solve it to the app:
Let me know whether it works.
Thanks for the effort. Really appreciated!
Unfortunately it did not solve my issue as the error remains the same (though, Iām not sure if I was supposed to see new options or if these are part of the logic and are invisible to users).
FYI, I updated the App and restarted my C2.
I guess I may have to get a āproperā cert to get it to work 
Well, in Settings you should now have an option to trust the system CA store instead. Additionally, when logging in, you can select to ignore certificate errors, that would require you to logout first, potentially clean up all data (available in settings at the very bottom using a pull up menu).
Iām at login page but cant see any pull up optionā¦there is only the pull down with clean up data option. I guess I would need to login to be able to see the settings option (but that is where Iām stuck atm)?
If the app has a certificate error it will offer you two options to solve it.
I tried with Bitwarden App (from Aurora) and Desktop App (on Fedora), and I get some fetch error related to certificate issue. No error from browser (direct url access, not tested with extension), but it might be using different cert rules than Apps (OS level) I believeā¦
I dont want to waste your time with this if Iām only one having issue ā I must fix the CA/cert thing from my end.
Well, I tried it locally with an untrusted cert and I could at least give an exception to not validate certificates (which si not ideal), though I did not test trusting the system CA store.
Fixed from my end with clean cert. Works like a charm 
Do I do something incorrectly, as I am following this MFA Applications for Sailfish - #11 by ninepine instruction how to get the API key and changed the server URL from the advanced to bitwarden.eu. But Bitsailor still says that credentials are incorrect while I copy past them straightly. Is there something else I need to do, before trying to login?