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.
The operating system my web server runs on is (include version): N/A
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): No
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
N/A
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
N/A
If you intend for this to be hosted by Wix, perhaps you could follow the instructions that appear there in order to connect the domain to Wix. At that point, Wix should be able to obtain a new certificate for you automatically.
If you intend for it to be hosted by a different hosting provider, perhaps you could figure out who that provider is and let us know the identity of the provider and the nature of the hosting environment that it uses.
It’s possible that you’re seeing this problem because www.midwestlp.com and midwestlp.com are currently being hosted on totally different infrastructure.
schoen@demorgan:~$ host www.midwestlp.com
www.midwestlp.com is an alias for www215.wixdns.net.
www215.wixdns.net is an alias for balancer.wixdns.net.
balancer.wixdns.net has address 185.230.61.195
schoen@demorgan:~$ host midwestlp.com
midwestlp.com has address 23.236.62.147
midwestlp.com mail is handled by 1 midwestlp-com.mail.protection.outlook.com.
In order to proceed further, you’ll need to account for this discrepancy and figure out whether it’s intentional.
