Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: namkee.hk
I ran this command: N/A
It produced this output: N/A
My web server is (include version): Using Wix Site
The operating system my web server runs on is (include version): I can’t find
My hosting provider, if applicable, is: domain hosting on speedhosting.net web site hosted by WIX Site
I can login to a root shell on my machine (yes or no, or I don’t know): I don’t know
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): I don’t know
Curiously, both certs have both names “namkee.hk, www.namkee.hk”.
Which implies, to me, that at least one of the two systems is using DNS authentication.
And since both names resolve to separate IPs, I would assume that both may be using DNS auth.
If that is the case, then, perhaps DNS API credentials have been changed and now only one site is being allowed.
Some other DNS change has occurred (in the last 94 days) that has now crippled the WIX authentication.
Like: Maybe both names resolved to the WIX IP and WIX was able to use HTTP(S) auth 94 days ago. But now no longer can as one name uses a foreign IP and will fail to pass WIX HTTP auth requests.