Anubis with nextcloud AIO and vaultvarden

[alainq79]

Hello,

I tried Anubis and it works well with Jellyfin and Jellyseerr. However, the Bitwarden Firefox add-on can no longer communicate with Vaultwarden when Anubis is enabled. Similarly, smartphone apps can no longer update calendars and contacts when Anubis is providing security for Nextcloud AIO.

Is there a setting to adjust on Anubis for Vaultwarden and Nextcloud AIO ?
Or is Anubis not designed to protect this type of application?

[Zoey2936]

you need to adjust the anubis bot policy file for this, but please understand that I will not help you with that, you better ask this in a anubis forum or similiar

[alainq79]

I will follow your advice. Thank you for your patience.

[Beckid]

Hello,

I tried Anubis and it works well with Jellyfin and Jellyseerr. However, the Bitwarden Firefox add-on can no longer communicate with Vaultwarden when Anubis is enabled. Similarly, smartphone apps can no longer update calendars and contacts when Anubis is providing security for Nextcloud AIO.

Is there a setting to adjust on Anubis for Vaultwarden and Nextcloud AIO ? Or is Anubis not designed to protect this type of application?

Did you ever figure this out @alainq79 ? I am working on the same thing right now. I can turn Anubis off and Vaultwarden works, but I would like to know how to edit the bot policy correctly to allow the browser plugin to work.

[Beckid]

Ok, I will let you know. I did my research today for a bit. It’s something in the BotPolicy.yaml file we need to add. I’ll poke around some more tonight.

[Beckid]

I got it @alainq79 !! I spent HOURS on this today. I tried so many Google searches, and came up with nothing. I've read people resorting to Claude's AI to do the "heavy lifting." If I would have just started there, it would have saved me so much time today.

To get the Bitwarden browser extension to work with your main Vaultwarden sits behind Anubis, here is one way to fix it (the easiest, in my opinion.)

The Fix: Use Custom Locations to Bypass API Paths

In NPMplus, go to your Vaultwarden proxy host → Custom Locations tab and add separate locations for the API paths that don't have Anubis selected.

Add these locations, each pointing to your Vaultwarden upstream, with Auth Request set to "None":

Location Path	Forward to	Auth Request
/api/	http://vaultwarden:8080	None
/identity/	http://vaultwarden:8080	None
/icons/	http://vaultwarden:8080	None
/notifications/	http://vaultwarden:8080	None

Of course, set the "Forward To" that matches your setup. Vaultwarden is installed on my NAS, along with all my other Docker containers. So, my Forward To is set to http://192.168.1.3:8000 (port 8000 is what my Vaultwarden install is set to.)

Everything worked after that! celebrate🥳

[alainq79]

Thank you for your work.

If I understand correctly, you've created a bypass for /api, /identity, /icons, and /notifications in custom Locations.
Are these four paths essential for the Bitwarden plugin to function?
Couldn't we just leave the forwarding for /api?

[Beckid]

Thank you for your work.

If I understand correctly, you've created a bypass for /api, /identity, /icons, and /notifications in custom Locations. Are these four paths essential for the Bitwarden plugin to function? Couldn't we just leave the forwarding for /api?

Correct.

That I’m not sure, but give it a try on just the /api path and share your results! 😊

[alainq79]

It seems to work with just the /api path.

I'll let it sit for a bit while I go to work. I'll let you know if the plugin stops working on either my computer or my smartphone.