Update the SSL from Let's Encrypt to not be wildcard so HTTP challenge will work instead of DNS challenge

[moraitis]

I am running a Wordpress Multi-site install using --mu=subdom but instead of using true subdomains, I use two different domains. But ee seems to always force Let's Encrypt wildcard SSL with the DNS challenge during the site create, clone, or sync.

I would like to remove the Let's Encrypt wildcard SSL and replace with normal SSL. My goal is to use HTTP challenge that can work with an automated cron job, instead of the DNS challenge that requires manual intervention. Since I am not using Cloudflare, the wildcard SSL renewal is manual.

I tried this command:

sudo ee site update examplesite.com --ssl=inherit

Then the error message is:

Error: Update from wildcard SSL to normal SSL is not supported yet.

While the feature is currently not supported via the ee cli, is there anything else I can do to switch away from wildcard DNS challenge to a normal HTTP challenge?

Here are the outputs for the various support requests:

# lsb_release -a

Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

# ee cli version

EE 4.6.4

# ee cli info

+-------------------+----------------------------------------------------------+
| OS                | Linux 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54: |
|                   | 14 UTC 2022 x86_64                                       |
| Shell             | /bin/bash                                                |
| PHP binary        | /usr/bin/php8.0                                          |
| PHP version       | 8.0.26                                                   |
| php.ini used      | /etc/php/8.0/cli/php.ini                                 |
| EE root dir       | phar://ee.phar                                           |
| EE vendor dir     | phar://ee.phar/vendor                                    |
| EE phar path      | /home/timandjen                                          |
| EE packages dir   |                                                          |
| EE global config  | /opt/easyengine/config/config.yml                        |
| EE project config |                                                          |
| EE version        | 4.6.4                                                    |
+-------------------+----------------------------------------------------------+

# wp --allow-root --info

OS:	Linux 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64
Shell:	
PHP binary:	/usr/local/bin/php
PHP version:	7.4.33
php.ini used:	/usr/local/etc/php/php.ini
MySQL binary:	/usr/bin/mysql
MySQL version:	mysql  Ver 15.1 Distrib 10.5.18-MariaDB, for debian-linux-gnu (x86_64) using  EditLine wrapper
SQL modes:	
WP-CLI root dir:	phar://wp-cli.phar/vendor/wp-cli/wp-cli
WP-CLI vendor dir:	phar://wp-cli.phar/vendor
WP_CLI phar path:	/var/www/htdocs
WP-CLI packages dir:	
WP-CLI cache dir:	/var/www/.wp-cli/cache
WP-CLI global config:	
WP-CLI project config:	
WP-CLI version:	2.7.1

[brinehart]

I too could really use this. As it stands right now my only real option is to make a backup of the site, destroy the ee instance, build a new one with "regular let's encrypt" turned on. That's a huge hassle.