# virtualmin check-connectivity --domain example.com
example.com
Status: 5 errors
Error1: dnsip : DNS resolution mismatch : example.com resolved to xxx.xxx.xxx.xxx instead of the expected xxx.xxx.xxx.xxx
Error2: web : Website request failed : 500 Can't connect to example.com:80 (SSL connect attempt failed error:0A0000C6:SSL routines::packet length too long error:0A000139:SSL routines::record layer failure)
Error3: ping : Failed to ping IP address : Ping of xxx.xxx.xxx.xxx did not response in 5 seconds
Error4: ping : Failed to ping IPv6 address : Ping of xxxx:xxxx:xxxx:xxxx:xxxx:xxxx did not response in 5 seconds
Error5: smtp : SMTP connection failed : Connection timed out
Oh! It’s only in Pro, for reasons I can’t figure. I’ll talk to Jamie and Ilia about that…probably ought to be in GPL. It certainly shouldn’t show up in the available commands on GPL if it’s not available.
We’ll either remove it from the help output and mark it as Pro-only in the docs, or we’ll move it to GPL (I prefer the latter, but Ilia and Jamie also have a say).
That’s unrelated to OPs question. Make a new topic. We probably need to see the actual name that has a problem, though, in order to check it from our end to see why it’s failing, so maybe make it a PM.
Yes, the connectivity check is available only as a Pro feature, as described here:
Yet, there are many other API commands listed in the documentation that are not available in the GPL version.
The right fix is to make Virtualmin GPL to be aware of those commands and show a clear message when a command isn’t available in the GPL version and only available in Pro.
I will looking into this and update this ticket with progress.
And, making this a GPL feature, however, is a separate and unrelated topic.
Alright, the issue has been resolved on both sides. When the Virtualmin helper command is called for the Virtualmin Pro API, it now displays a clear message:
root@alma9-gpl:~# virtualmin list-acme-providers
Command list-acme-providers is only available in Virtualmin Pro
Additionally, all Pro API commands are now marked on the documentation site: