This is where certbot-auto would put them, yes … but I do not believe that is how the integration with MiaB is set up …dunno. See my last post for the location within MiaB installs.
I found the correct .pem file, and I used a pem+ sslkey converter to convert it to pfx file and upload the .pfx to my windows webserver, and added it, but it doesn’t work. maybe this is where I need help, how do I convert the .pem and sslkey file into an usable .pfx file for windows
sort off, I still need help but here is what I did
so I added my ddns name to my MIB pern.duckdns.org and I went to duckdns control panel, and I pointed pern.duckdns.org to my MIB ip address.
once DNS updated, MIB was able to provision a certificate to pern.duckdns.org using the cert tool within it
so I went into my MIB, downloaded the newest cert on there, went to the website https://www.sslshopper.com/ssl-converter.html and used the cert I just downloaded and the SSL key and got my .pfx file. I uploaded .pfx file to webserver and added to my site.
so my site, https://troll-ed.com works now but some parts of the site do not show up, it says some parts are not secure
okay so I fixed the issue. My site https://troll-ed.com had other links which were not https, therefore since my browser is setup to not display mixed content
so my sites are now HTTPS and resolving correctly using a DDNS redirect
so to recap, I installed MIB, uploaded a redirect to the default directory in MIB for troll-ed.com
that redirect pointed to my DDNS domain pern.duckdns.org:8083
@pern seems you didn’t tock into account what will happens at let’s Encrypt certificate renewal time …
Your box.yourdomain.com will get automatically renewed at <14 days to due date
Your BOX will not renew your main yourdomain.com and subdomain.yourdomain.com because they are pointing to an external server IP then your manually copied certificate for them will expire and will not be renewed.
The way you need to go is:
Create your MIAB as new.
Before to ask for the let’s Encrypt certificate through your MiaB admin panel add the needed custom DNS A records, for your main & yourdomain.com and other subdomain(s), normally www.yourdomain.com, pointing them to the ‘other’ server IP address.
Now is the moment to call for the certificate through MiaB… And only a certificate for box.yourdomain.com will be issued.
In your other server, where you plan to host your wordpress, install Let’s Encrypt/ Cerbot and ask for the needed certificates for your main yourdomain.com and subdomain.mydomain.com from the real server where your Wordpress web app. will be served.
Just google about Let’s encrypt for Winndos IIS or search at let’s Encrypt documentation section for the right/ available client(s).
BTW to start-up you may wish to watch this youtube about, too. Hope this helps.