Info Lastpass to Bitwarden

Currently reading
Info Lastpass to Bitwarden

Is that (the self hosted version 1.19) far behind the 1.40 release, or do both version numbers not correlate with each other.
1.19 is the bitwardenrs one not the official one. These 2 version have nothing in common apart that they can use the same client version apps.
 
Upvote 0
Hi Rusty
An idle question, but can you set watchtower to simply inform you of new versions? Or is it purely to silently update?
You can use the --monitor-only flag. Initially, WT didn't have this option but about a year or two ago it was implemented.

As an alternative, you can use Duin as well
 
Upvote 0
Could you share an image of your volume bind/map and the port configuration as well? You can do it in private if you want
Rusty:

Sorry for the long delay; life got in the way. Is this the correct information?

1617563434114.png

1617563457642.png
 
Upvote 0
Upvote 0
Rusty:

Thank you. That fixed it right up. However, now, when I try to create an account, I get an error that I must do so through an https site. While this is all a bit over my head, I suspect I'm running into the SMTP issue described on page 1 of this thread. Is there a walkthrough for that portion?

CheapDad
 
Upvote 0
Rusty:

Thank you. That fixed it right up. However, now, when I try to create an account, I get an error that I must do so through an https site. While this is all a bit over my head, I suspect I'm running into the SMTP issue described on page 1 of this thread. Is there a walkthrough for that portion?

CheapDad
Yes, bw needs to run on https. best to run it like that. Look into reverse proxy resource on the forum and configure it that way, then try and create an account
 
Upvote 0
Yes, bw needs to run on https. best to run it like that. Look into reverse proxy resource on the forum and configure it that way, then try and create an account

Rusty:

I read through the reverse proxy information and I'm a bit confused. First, for me, the Certificate folder is under the Security icon in Control Panel. That might help other novices like me.

The only certificate I have is the synology.com certificate that I created when I enabled DDNS to utilize OpenVPN to access my NAS from outside the network. My access to the NAS through DDNS is NAMEOFNAS.synology.com.

Is this the certificate that I want to use to set up the reverse proxy? If not, wouldn't I want to set up both OpenVPN and Bitwarden to use the same reverse proxy to further protect the system?

CheapDad
 
Upvote 0
Is this the certificate that I want to use to set up the reverse proxy?
That certificate would not work because it has no coverage for the custom bitwarden.nameofnas.synolog.me domain name.

The reverse proxy will ask for a unique name (such as the above one for example), and if the certificate is not covered by it you will still get an SSL error when accessing that BW instance.

What would be good is to make a new certificate for your existing DDNS name but issue it as a wild card certificate. This will allow you to get a *.nameofyournas.synology.me certificate, and as a return, you will be able to use any subdomain name without the need or problem passing the SSL check.

Check here: Let's Encrypt + Docker = wildcard certs under the "Step 05 - issue a LE cert using DSM Security UI" heading for more details. Write back if you have any questions.
 
Upvote 0

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top