Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bitwardenrs docker continues to run for a while, then refuse connections

Featured Replies

Been running the Bitwarden Docker for sometime now. Usually it works like a charm, but then, seems like after about 4-7 days of running, I start getting errors when I connect to my https://bitwarden.mydomain.com

 

Followed the directions from Spaceinvader on youtube

I have a reverse proxy setup correctly, also following Spaceinvader on youtube.

I also run Nextcloud through the reverse proxy, and have never had any issues with access via the same means as bitwarden.

 

With Wireguard VPN, I can access bitwarden via the local IP http://192.168.11.53:8086

 

There aren't any meaningful error messages in the docker logs for Letsencrypt or Bitwarden.

 

On the letsencrypt docker setup page, I swapped the Subdomain variables: bitwarden,nextcloud

to: nextcloud,bitwarden

Here's the log (I swapped out the actual domain with 'mydomain')

https://hastebin.com/erikuhevon.sql

That fixed the problem for the moment, but I'd still like to get to the bottom of this.

 

The setup:

1. created account at Duckdns, installed Duckdns docker to continually update local ip

2. I own my own domain, I created CNAME subdomains for nextcloud and bitwarden.

     nextcloud.mydomain.com CNAME to username.duckdns.org

     bitwarden.mydomain.com CNAME to username.duckdns.org

3. letsencrypt docker has settings

    "Domain name:" as mydomain.com

    Subdomain(s): bitwarden,nextcloud

    http: 180

    https: 1443

4. home router forwards

    port 80 to port 180 on unRaid server

    port 443 to port 1443 on unRaid server

 

 

 

Firefox

Quote

 

The page isn’t redirecting properly

An error occurred during a connection to bitwarden.kerlee.com.

    This problem can sometimes be caused by disabling or refusing to accept cookies.

 

 

Chrome

Quote

 

This page isn’t working

bitwarden.kerlee.com redirected you too many times.

Try clearing your cookies.

ERR_TOO_MANY_REDIRECTS

 

 

Internet Explorer 11

Quote

 

Can’t reach this page

Make sure the web address https://bitwarden.kerlee.com is correct

Search for this site on Bing

Refresh the page

Check that all network cables are plugged in.

Verify that airplane mode is turned off.

Make sure your wireless switch is turned on.

See if you can connect to mobile broadband.

Restart your router.

More information<id id="moreInformation">More information</id>

There were too many redirections.

Error Code: INET_E_REDIRECT_FAILED

 

 

rubble-diagnostics-20200604-1058.zip

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.