I've already launched IIS while conducting experiments.
Now I'll turn it off. Currently, I'll try the Webprofusion path.
Then we are all agreed 
Hello friends. Should I run certbot.exe on the server or locally on my computer? My site became visible as his-name.com.
OPS!!!!
Successfully received certificate.
Certificate is saved at: C:\Certbot\live\his-name.com\fullchain.pem
Key is saved at: C:\Certbot\live\his-name.com\privkey.pem
This certificate expires on 2024-05-28.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.
If you like Certbot, please consider supporting our work by:
- Donating to ISRG / Let's Encrypt: Donate - Let's Encrypt
- Donating to EFF: Support EFF's Work on Let's Encrypt | Electronic Frontier Foundation
It seems I managed to do it!
Curious, are these certificates already in the right place, or do I need to move them somewhere and somehow so they work for HTTPS? (Windows Server 2019) (IIS)
Now that you have your certificate, deploying it involves telling anything that's going to use it that it exists and where to find it.
So for you the next step is to tell your node server where to pick up the files from (use the key file and the fullchain.pem file):
You may need to adjust the file permissions so your process can read the certificate files, or you may not.
If you did decide to use them with IIS (not your node server) that's a different process but from what I can tell you don't really want/need to use IIS at all.
Hello friends. Now there's another issue. The certificates state that they cannot be moved (WARNING: DO NOT MOVE OR RENAME THESE FILES!
Certbot expects these files to remain in this location in order
to function properly!) , but in order for IIS to recognize them, I need to install them through the IIS Manager, and they need to be in the form of a PFX file, which I don't have.
Wow! https://his-name.com/ EZ!
So, friends, everything is working as expected. Here's what was done: I used IIS to create a website, then obtained a certificate with Certbot. Using OpenSSL, I created a PFX file, which was uploaded to the IIS certificates. These same certificates were used in the JavaScript code for WSS connection. And the connection is established:
socket = new WebSocket("wss://his-name.com:3300");
Everything connects properly. Thanks to everyone for the help.
I substituted the same .crt and .key files in my JavaScript code that were used for importing into IIS.
LE certs last only 90 days.
Are you able to automate the renewals?
If not, then you may need to reconsider your solution.
Most likely, this will be done manually. But I think it's possible to pause for technical maintenance once every three months.
I think that Let's has a paid certificate for a year. So, after three months, I'll switch to the paid one. By the way, is there a free one for a year?
But you could better automate the process by using a Windows ACME client.
And already mentioned twice before:
OR you could place your app behind a proxy that was easier to integrate with automation.
Also mentioned before:
LE only provides FREE certs.
All LE certs last only 90 days [no longer, no shorter].
Note: There are plans of offering certs with much shorter life.
There are NO plans of offering a cert with longer life.
Why would you want to pay for something that you can get for FREE?
All you need to figure out is the automation.
I'm still familiarizing myself with this article (IIS As Reverse Proxy To WebSocket Server | by Adrian Jenkins | Medium).
If Certify The Web doesn't really appeal to you there is also win-acme or Posh-ACME which are both popular tools on Windows which produce PFX and/or PEM files.