cheesemarathon

Site is back up, try the link again!

Thanks for spotting that. I'm at work right now, but I'll either send you the instructions or fix the link as soon as I get back home in a few hours.

Hi Alphahelix Take a look at LinuxServer's reverse proxy docker container. It is how I have my Bitwarden setup and it works perfect in every browser I have tried. Shout if you need further help setting it up and ill share my config with you.

This shouldn't be an issue with this docker image but may be an issue with unRAID. Perhaps ask for some help in the networking forum. I'm not an expert on vlan's

Apologies for this. I'm moving house at the moment and the server hosting the instructions currently doesn't have an internet connection. Should be backup sometime this weekend fingers crossed!

I had to take my server down for several hours the other day. It's back up and running now. Sorry for the inconvenience.

In theory, yes, we can add webmin, but it would require completely rebuilding the container. What I'm confused about is why you want to edit the BIND instance inside steamcache. BIND is used to redirect specific domains to the cache server. If you start redirecting other domains there could be unexpected and unpredictable results. Also if you make changes to BIND and we then update the container, there could be conflicts that break things. When we are not in control of everything inside the container, we can't guarantee it will work. I'd recommend setting up your own system for anything custom, that way you are in control of your side of things and we control the steamcache side of things.

Just let the internet handle it all. I don't notice any issues with speed or responsiveness and I wanted remote access. Plus one of my machines is a laptop which may not always be at home local to my bitwarden instance so it's easier to set it up to just use the public URL. If you want to handle it locally, you can look to see if your router is able to do DNS redirects.

@FireFtw When signups are disabled, the Create Account button will still appear and you can click on it and fill out the form. However, when you click the submit button to create a new account, it should say "Registration not allowed" If your still having issues, make sure the container is up to date. Also, try recreating the container. I had an issue where I had changed SIGNUPS_ALLOWED to false but not saved it properly so it didn't recreate the container and a restart didn't apply the change. So you can just remove the "e" in false and retype it, thus making a change so the Apply button is enabled but keeping the settings the same. Then click Apply to recreate the container with the new settings. I hope that makes sense. Let me know if you're still having issues.

Hmmm, not sure at the moment. I'm looking in to this!

The current caching system has a few bugs with the way it is set up, especially when it comes to windows updates. We are working on a completely new system that should fix this. However, in the meantime, you should be able to just disable windows updates from caching. I don't understand why this doesn't work. @mlebjerg are you able to shed any light on this? Also, sorry for taking ages to reply 😝

I'm a little bit confused as to what it is exactly you want to do. You can't really setup webmin inside the container. What is it exactly your trying to achieve? What do you mean by "set up domains on my local network such as example.lab"? Also, sorry for taking ages to reply 😝

See here:

All info for the bitwarden is stored in your appdata folder. All I am doing is backing up my entire appdata folder every day using duplicati. However, you could use this image to create incremental backups of the sqlite database. In theory if you backup the app data folder whilst data is being written to the database you could create a corrupted backup, hence the need for the additional container to run the sqlite backup command. However, im the only user on my instance and I run my backups late at night so it's not been an issue for me. Yet...

Yeh, sorry about that. I think it's due to the fact that the image is not hosted on docker hub. When the check for update script runs, I would image it only compares the current image to whatever is on docker hub. As those don't match it says that an update exists even though it doesn't. As I don't maintain the image, there is nothing I can do about this. All I can suggest is turning it off automatic updates, so it doesn't attempt an update all the time. And just updating it manually periodically. You can check for updates by seeing when the latest tag was last updated here However, updating it every night shouldn't cause any issues apart from a few mins of downtime. It's a little annoying but it won't break anything