Cannot log into Bitwarden

It states that i am using the wrong username/password, but I am certain that I am using the correct info.

inxi
System:    Kernel: 5.13.9-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=d0708788-8b13-41c6-8a2b-f75619c87919  
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 resume=UUID=5a1a9a60-6d1c-4612-ab3a-fed623ace2a3 loglevel=3
Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM  
Distro: Garuda Linux base: Arch Linux  
Machine:   Type: Laptop System: Dell product: Inspiron 15 7000 Gaming v: N/A serial: <filter> Chassis:  
type: 10 serial: <filter>  
Mobo: Dell model: 0MK77P v: A00 serial: <filter> UEFI: Dell v: 1.11.0 date: 12/04/2019  
Battery:   ID-1: BAT0 charge: 55.0 Wh (100.0%) condition: 55.0/74.0 Wh (74.3%) volts: 12.5 min: 11.1  
model: Samsung SDI DELL 0GFJ675 type: Li-ion serial: <filter> status: Full  
CPU:       Info: Quad Core model: Intel Core i5-7300HQ bits: 64 type: MCP arch: Kaby Lake family: 6  
model-id: 9E (158) stepping: 9 microcode: EA cache: L2: 6 MiB  
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19999  
Speed: 3217 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 3217 2: 3255 3: 3243 4: 3356  
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled  
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled  
Type: mds mitigation: Clear CPU buffers; SMT disabled  
Type: meltdown mitigation: PTI  
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp  
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization  
Type: spectre_v2  
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling  
Type: srbds mitigation: Microcode  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0  
chip-ID: 8086:591b class-ID: 0300  
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: Dell driver: nvidia v: 470.57.02  
alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1c8c class-ID: 0300  
Device-3: Sunplus Innovation Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-12:4  
chip-ID: 1bcf:28c1 class-ID: 0e02  
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: modesetting,nvidia  
display-ID: :0 screens: 1  
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")  
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") diag: 395mm (15.5")  
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 21.1.6 direct render: Yes  
Audio:     Device-1: Intel CM238 HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3  
chip-ID: 8086:a171 class-ID: 0403  
Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 01:00.1
chip-ID: 10de:0fb9 class-ID: 0403
Sound Server-1: ALSA v: k5.13.9-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes
Sound Server-4: PipeWire v: 0.3.33 running: yes
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169
v: kernel port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel port: d000 bus-ID: 03:00.0
chip-ID: 8086:3165 class-ID: 0280
IF: wlp3s0 state: down mac: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-4:3
chip-ID: 8087:0a2a class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060
bus-ID: 00:17.0 chip-ID: 8086.282a rev: 31 class-ID: 0104
Drives:    Local Storage: total: 2.05 TiB used: 26.59 GiB (1.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Micron model: 1100 SATA 256GB size: 238.47 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: L003
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000LX001-1RG174 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: SDM1 scheme: GPT
Partition: ID-1: / raw-size: 221.16 GiB size: 221.16 GiB (100.00%) used: 26.59 GiB (12.0%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 562 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 221.16 GiB size: 221.16 GiB (100.00%) used: 26.59 GiB (12.0%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 221.16 GiB size: 221.16 GiB (100.00%) used: 26.59 GiB (12.0%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 221.16 GiB size: 221.16 GiB (100.00%) used: 26.59 GiB (12.0%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 17.05 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3
maj-min: 8:3
ID-2: swap-2 type: zram size: 15.5 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 59.0 C mobo: 43.0 C sodimm: SODIMM C
Fan Speeds (RPM): cpu: 0
Info:      Processes: 238 Uptime: 1h 11m wakeups: 13 Memory: 15.5 GiB used: 4.08 GiB (26.3%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1678 lib: 505
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06

Which Bitwarden service are you trying to use, and did you create an account on it?

(You can't use your local PC's username and password on a web service.)

1 Like

The one presented by Garuda Welcome. I am using my Bitwarden credentials.

Your credentials for bitwarden.com won't work on the Garuda instance.

1 Like

Then which credentials do I need to use to log into Bitwarden?

?  

1 Like

btw... can I kinda offtopic a little and ask if its ok to test drive these garuda services ( bitwarden and cloud ) ? Or is it something that if there is a lot of heavy usage, the garuda servers "suffer" ?

I wanted to try them, but don't want to be a burden to the servers.

The Garuda Cloud registrations are closed for now, we might open it up again in the future again if we have more ressources.
Bitwarden can be used without issues though :slight_smile:

2 Likes

sniff :frowning: I thank you for the help, but I won’t like the post !!! :stuck_out_tongue:

You are talking like I would need this one :eyes::wink::stuck_out_tongue_closed_eyes:

2 Likes

Sorry for the late reply. I had to switch back to Windows due to some other issues. I already have a Bitwarden account. Are you saying that I need to create a new one?

If you want to use the Garuda instance, then yes. Otherwise, you can log in to a global bitwarden account through the app, extension or any other way that's not through the Garuda link.

1 Like

We covered this already. Garuda runs an instance of the Bitwarden software, which is different to and separate from the bitwarden.com instance.

Just like you can have multiple email accounts on multiple providers with different usernames and passwords, or accounts on multiple NextCloud servers, or accounts on multiple Mastodon servers, you can have accounts on multiple Bitwarden servers.

If you do not have an account on the Garuda Bitwarden instance then you have to create one, and that account will only work on the Garuda instance. You can’t log into the Garuda instance using your bitwarden.com credentials, and you can’t log in to the bitwarden.com instance with the credentials for the Garuda instance.

If any of this is confusing then just continue to use the bitwarden.com instance as you normally would - it’s the default server for all Bitwarden clients.

3 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.