Most of the company websites I handle are hosted on shared servers, and with typical shared servers, it’s not possible to extract the certificates.
Additionally, proxy settings cannot be added to the web server on a shared hosting environment.
While it might be possible to configure a proxy using an .htaccess file on an Apache server, there are limitations—such as the need to have mod_rewrite and mod_proxy enabled.
Furthermore, obtaining FTP access permissions to a web space contracted by another party is often difficult, so this option also seems quite challenging.
I don’t think any of that has anything to do with the original question, though? I mean, DNS-01 validation doesn’t solve any of those problems.
DNS-01 can resolve this.
Some shared servers allow DNS-01 authentication by having users add a TXT record to their DNS before modifying the www A record. Is this difficult to implement with Virtualmin?
Sorry for the Japanese.
https://www.xserver.ne.jp/manual/man_server_ssl.php#link-b02
If you’re doing everything manually, just use certbot.
I’m sorry, but I don’t quite understand what you’re saying.
I never said I was doing everything manually, and I don’t want to run Certbot via command line either, which is why I’m posting this on the Virtualmin forum.
How do you expect to install an SSL certificate on a virtual host that hasn’t been created yet?
What specific problem are you solving?
What do you mean by “the virtual host hasn’t been created”?
Do you mean that it doesn’t exist on the public internet, or that it hasn’t been configured in Virtualmin yet?
In our case, the domain already exists on the internet (but it’s not managed by us). It already has an SSL certificate installed and is accessible via HTTPS.
We are planning to add a virtual host in Virtualmin as the migration target.
Specifically, we will add the destination virtual host in Virtualmin and pre-install the SSL certificate using DNS-01 authentication on that Virtualmin host, which is not yet active on the internet.
The problems this setup is intended to solve are described below the section you quoted.
It’s not a problem at all. Just create or move your domain to the Virtualmin server and do all the necessary configurations before changing the DNS.
You can install an existing SSL certificate on the Virtualmin virtual server using the “Manage Virtual Server ⇾ Setup SSL Certificate: SSL Certificate / Update Certificate and Key” page.
I have already responded to that point.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.