@NotLikely38 This works for me. I disabled that DST Root CA X3 and icons immediately came back!
Thank you!
Glad to hear you finally got it working, @Collence. This sounds like it was related to certs installed by your self-hosted instance, and not the Bitwarden client after all. Was that server instance a Vaultwarden or Bitwarden, out of curiosity?
I have 2 bitwarden accounts, one self hosted and another on bitwarden cloud hosted. The icon issue was persistent on both accounts.
The issue started with the expire of the LE root cert back on Oct 5th.
That cert would have been installed to access your self-hosted instance, though. Not the BItwarden servers since they donât use Letâs Encrypt. Thatâs why I asked.
So you havenât installed Vaultwarden then? Curious what the chain of events was.
I self host vaultwarden, but also have regular bitwarden account and the icons were not working with either.
Yeah, seems to be a common pattern. Thanks!
@NotLikely38 â disabling this cert worked for me as well, however my phone shows that as a âSYSTEMâ cert and not a user cert.
What effect would disabling this have on other apps/services/etc?
@NotLikely38 Great point! Itâs a system cert for me also.
To be on the safe side, I switched from LetsEncrypt to ZeroSSL for my certs. I then re-enabled DST Root CA X3 on my android devices. Tested and I see all icons fine.
Use another CA such as ZeroSSL, which uses a root which is trusted back to Android 2.2, and which wonât expire until 2038.
@CorneliousJD, @Collence - Given that the DST Root CA X3 certificate has already expired, I donât think there is any harm in disabling it. In my case, the current LetsEncrypt root certificate (ISRG Root X1) is also installed as a System certificate on my phone and will not expire until 2035.
Thanks for this, Iâve disabled the DST root CA x3 and so far eveything is still working, since itâs expired already I donât anticipate any other issues.
My question (which may not be well suited for this specific forum) would be why my cert, issued just a few months ago, why itâs being looking at the old DST Root instead of the ISRG root cert? Is this an Android bug or a LetsEncrypt/cert bug, or just a BitWarden app bug thatâs looking at that first when it should be just checking ISRG?
I already have a fully automated process setup for my LE certs for all my selfhosted apps, and would like to keep that running how it is, but would like to avoid this issue on other android devices, etc in the future, as I do host a few accounts for other family members and this is also affecting them.
They wont understand my instruction to go disable DST root CA 
The cert chain would have been installed when you setup your server, and the client apps download the CA cert and the root cert. The LE root cert expired in September (this happens), but was not replaced by the updated root cert on your device. This had nothing to do with the Bitwarden app, as far as I can tell.
Did you also install Vaultwarden to host a BW vault? If so, that seems to be the common thread here.
@CorneliousJD On the server, you may want to consider swapping out LE cert for ZeroSSL. This way your family members would not have to worry about tweaking their android devices to make it work. It will just work as expected.
Coming in late to the party, but my Pixel 3 with BitWarden installed (not self hosted) does not show icons either. I disabled the certificate, but no joy.
Pixel 4a Android 12 same issue, not self hosted.
Bitwarden icons on Android seem to be working for most people, so this is likely a client-side issue. Try all the steps below to see if this solves it:
- On your Android device, stop the Bitwarden app.
- Under Other Security Settings in Android, go to View Security Certificates and disable the expired Letâs Encrypt root certificate called Digital Signature Trust (or DST) Root CA X3.
- Ensure that you have the Internet Security Research Group (or ISRG) Root X1 certificate on your device (same menu). If not, you may need to download and install the root and intermediate certificates (see: Chains of Trust - Let's Encrypt)
- Reboot your device and open Bitwarden again to see if they icons re-appear.
If you are still having problems, use the Chrome browser in Android and to go to: https://icons.bitwarden.net/google.com/icon.png and then check the security connection (click on the padlock near the URL in Chrome - you should be able to view the status of the certificates in the chain, which may provide some clues about any issues encountered).
I think I completed the steps outlined correctly. I did a force stop on BitWarden for #1.
For #2, I found the certificates and disabled DST cert (it was expired in September). I confirmed I had the Root X1 cert (valid until 2035 I think). I then rebooted, and now I have the icons in BitWarden on Android.
Thank you for those instructions!
I was having the same issue with favicons not displaying and after googling found this topic.
After following the steps outlined the icons are now displaying correctly. Strange thing is the icons disappearing only recently happened (possibly since the last play store update 
).
Everythingâs working now though so thanks 
Will disabling the certificate have any adverse effects on anything else though?
Glad to hear you got it fixed. And since the certificate has already expired, disabling it should have no negative effects.