# Change validation method **URL:** \ **Category:** Help\ **Created:** [December 5, 2023, 10:14pm UTC](https://community.letsencrypt.org/t/change-validation-method/209583 "2023-12-05T22:14:30Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Draega](https://avatars.discourse-cdn.com/v4/letter/d/eb9ed0/32.png) [@Draega](https://community.letsencrypt.org/u/Draega)\ **Post date:** [December 5, 2023, 10:14pm UTC](https://community.letsencrypt.org/t/change-validation-method/209583/1 "2023-12-05T22:14:31Z")
My domain is: [draega.net](http://draega.net) The operating system my web server runs on is (include version): Ubuntu 22.04 I can login to a root shell on my machine Yes I'm using a control panel to manage my site (no, or provide the name and version of the control panel):Virtualmin I have a fully functioning Certificate. I was using the Acme Bot that was provided with Abyss Web Server and using DNS challenge to authenticate. I have since switched to a VPS running Ubuntu 22.04 and Virtualmin. I was able to export and import my ssl certs to the new site and everything is working fine. Issue is I would like to change to HTTP authentication when the certificate expires in 77 days. I tried a test renewal on the new system and it complained that there was no acme challenge in the DNS records. That was on me. I deleted the txt record when I was changing my DNS entries. Is there a way to change the challenge type to HTTP going forward? I still have access to the old web server and I guess I could just renew there and export and import the crt and key again. But I would much prefer to automate it on the new server. Thank You. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [December 5, 2023, 10:26pm UTC](https://community.letsencrypt.org/t/change-validation-method/209583/2 "2023-12-05T22:26:56Z")
> [@Draega](#): > > I tried a test renewal on the new system and it complained that there was no acme challenge in the DNS records. That was on me. I deleted the txt record when I was changing my DNS entries. How did you do a "test renewal". Was that through VirtualMin or some other ACME client? I see you are using Apache so it should not be difficult to setup HTTP challenge. I don't know much about VirtualMin but your hosting service should be able to help you. That said, in the past you got wildcard certs which require the DNS Challenge. Also, a DNS Challenge will require a different TXT value for each renewed cert. So, no worries that you deleted the old TXT record. It would not be used anymore anyway. ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [December 5, 2023, 10:30pm UTC](https://community.letsencrypt.org/t/change-validation-method/209583/3 "2023-12-05T22:30:19Z")
Hello @Draega, welcome to the Let's Encrypt community. 🙂 Side notes: - The issued certificate [https://crt.sh/?id=11321628560](https://crt.sh/?id=11321628560) - [SSL Checker](https://decoder.link/sslchecker/draega.net/443) doesn't like it. - nor does [SSL Server Test: draega.net (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html?d=draega.net) - or [Hardenize Report: draega.net](https://www.hardenize.com/report/draega.net/1701814927#www_certs) The issue with the certificate is it is a wildcard certificate containing only `*.draega.net`; it should also contain `draega.net`. ---
**Author:** ![Draega](https://avatars.discourse-cdn.com/v4/letter/d/eb9ed0/32.png) [@Draega](https://community.letsencrypt.org/u/Draega)\ **Post date:** [December 5, 2023, 10:36pm UTC](https://community.letsencrypt.org/t/change-validation-method/209583/4 "2023-12-05T22:36:12Z")
Hi. Yes it was through Virtualmin. Yes I was planning on changing from a wildcard when it was time to renew. I was assuming as there is a certificate all ready for the domain using the wildcard I would not be able to issue a new certificate using [draega.net](http://draega.net) and [www.draega.net](http://www.draega.net). ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [December 5, 2023, 10:44pm UTC](https://community.letsencrypt.org/t/change-validation-method/209583/5 "2023-12-05T22:44:02Z")
> [@Draega](#): > > I was assuming as there is a certificate all ready for the domain using the wildcard I would not be able to issue a new certificate using [draega.net](http://draega.net) and [www.draega.net](http://www.draega.net). Let's Encrypt will not prevent that. You could even have both at the same time although this is rarely useful 🙂 I don't know what VirtualMin requires to switch methods. ---
**Author:** ![Draega](https://avatars.discourse-cdn.com/v4/letter/d/eb9ed0/32.png) [@Draega](https://community.letsencrypt.org/u/Draega)\ **Post date:** [December 5, 2023, 10:59pm UTC](https://community.letsencrypt.org/t/change-validation-method/209583/6 "2023-12-05T22:59:32Z")
Hmmm. Interesting. I just assumed it wouldn't let me. I will attempt to create a new certificate for [draega.net](http://draega.net) and [www.draega.net](http://www.draega.net) when I get home later tonight. And just let the wildcard certificate expire. Thanks! ---
**Author:** ![Draega](https://avatars.discourse-cdn.com/v4/letter/d/eb9ed0/32.png) [@Draega](https://community.letsencrypt.org/u/Draega)\ **Post date:** [December 6, 2023, 2:49am UTC](https://community.letsencrypt.org/t/change-validation-method/209583/7 "2023-12-06T02:49:45Z")
Well that worked. 🙂 Thanks a lot for your help! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [January 5, 2024, 2:50am UTC](https://community.letsencrypt.org/t/change-validation-method/209583/8 "2024-01-05T02:50:18Z")
Closed on January 5, 2024, 2:50am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.