Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
The operating system my web server runs on is (include version): Unsure
My hosting provider, if applicable, is: Mochahost
I can login to a root shell on my machine (yes or no, or I don't know): Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): 102.0 (build 26)
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): N/A
I've set up Ubuntu 22.04 Live Server VM on a bare metal server running Windows Server 2019. From there I installed Bitwarden in a docker container.
I'm a bit lost as to how to obtain a Let's Encrypt SSL Certificate. My understanding of the instructions is that Certbot has to run behind my domain. This is the step I'm not sure how to do. Some of the video's I've watched describe how to set it up in a docker container but that would put it on my home network along with Bitwarden, not "behind" my domain, right? Wouldn't Certbot have to run on my webhost somehow?
$ nmap homelab.glenspcservice.com
Starting Nmap 7.80 ( https://nmap.org ) at 2022-12-19 16:27 UTC
Nmap scan report for homelab.glenspcservice.com (97.88.217.20)
Host is up (0.088s latency).
rDNS record for 97.88.217.20: 097-088-217-020.res.spectrum.com
Not shown: 997 filtered ports
PORT STATE SERVICE
443/tcp closed https
5001/tcp open commplex-link
5060/tcp open sip
Nmap done: 1 IP address (1 host up) scanned in 7.50 seconds
That depends entirely on the ACME client used [and how it was configured].
And, maybe more so, their amount of access to that system.
[which that may have]
I'm sorry. I'm new at this. I'm trying to learn. Maybe I'm doing it completely wrong.
The first question the installer asks is the domain name for my Bitwarden instance.
I'm self-hosting this install so it's installed in a docker container on a Ubuntu 22 Linux host.
I chose a subdomain I created on a domain I own. Maybe I did this wrong too but according to a couple of guides I read this is one way to do it.
The very next question concerns Let's Encrypt. The documentation for Let's Encrypt seems to indicate at least part of it needs to reside "behind" your domain.
If I'm not doing this right could you please add an answer to your question?
My advice is to have a clear picture of what you are doing/intend to do.
Like an actual schematic diagram would be the most excellent "picture".
And you should understand what each piece of that puzzle is doing, how it does it, and how all the pieces work together to accomplish your "plan".
Did I mention that you need "a plan"?
This is not the right place to discuss such plans/designing - but maybe someone will be willing to review your situation and point you in the right direction [or at least point out any flaws (if they find any)].
I don't have a bag of instructional links to rummage through.
I'm mostly self-taught, so I do know what you might be going through.
But, since I've been doing this for so long, I really don't know how anyone is learning anything these days - LOL
As for "you tube", is it full of everything [good and bad].
We mostly run across the things that fail [the ones that worked don't need our help] and that may be skewing my perspective about it.
I think it just takes some researching/common sense [although it seems uncommon these days] to make sense of what they are showing/asking you to do BEFORE you do any of it; It needs to make sense. If it doesn't, then don't "just do it" OR get more information about it... until it does make sense [or you realize they are just as lost as you are and you need to look elsewhere].
Thanks for such a carefully written and well-thought-out response.
The truth is, I did a lot of research before beginning this project. When I hit a roadblock I did more research looking for answers before I came here asking questions.
Just to clear things up, in case someone is reading this later and finds themselves in the same place I was in, they will find the same answer I did.
It turns out that when I configured the domain that I intended to use with Bitwarden, I used my webhost to do this. My primary website has a certificate from Let's Encrypt and the domain I configured was automatically provided a certificate.
The certificate that Bruce showed me that was issued does not match the certificate my webhost issued, hence my confusion.
Thanks again rg305 and everyone else for your help.
Here is a list of issued certificate for crt.sh | glenspcservice.com it includes the domain and subdomains. Thus your server should be serving one of the certificates that will name match the domain name being served.
