In some rare cases CURL is compiled with OpenSSL instead of SecureTransport, which causes some issues, in this particular case with the maps not being displayed in the frontend. (more infos in this can be found here
A user reported that he could fix this issue by changing sslverfiy => true in class-wpsight-geocode.php:216
Since this change could potentially cause an issue for others, best solution at the moment is probably to apply an additional filter on that part, so affected users can simply change this without changing anything on the core.
In some rare cases CURL is compiled with OpenSSL instead of SecureTransport, which causes some issues, in this particular case with the maps not being displayed in the frontend. (more infos in this can be found here
A user reported that he could fix this issue by changing sslverfiy => true in class-wpsight-geocode.php:216
Since this change could potentially cause an issue for others, best solution at the moment is probably to apply an additional filter on that part, so affected users can simply change this without changing anything on the core.
Only for @wpsight/developers: More infos