Title: SSL Certificate Problem
Last modified: November 19, 2023

---

# SSL Certificate Problem

 *  Resolved [lksecl](https://wordpress.org/support/users/lksecl/)
 * (@lksecl)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/ssl-certificate-problem-22/)
 * Dear Daniel,
 * we’ve an issue that when we implement the plugin that ithe site is shown as “
   unsecure”. It seems that there isn’t a problem with the ssl certicate, but the
   at the lock at the search bar appears a warn sign.
   Do you have any idea what 
   it coulde be?Best regards,Lukas
    -  This topic was modified 2 years, 10 months ago by [lksecl](https://wordpress.org/support/users/lksecl/).
    -  This topic was modified 2 years, 10 months ago by [lksecl](https://wordpress.org/support/users/lksecl/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fssl-certificate-problem-22%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [100plugins](https://wordpress.org/support/users/100plugins/)
 * (@100plugins)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/ssl-certificate-problem-22/#post-17213651)
 * Hi [@lksecl](https://wordpress.org/support/users/lksecl/),
 * I just checked your site and everything looks fine. The SSL is valid without 
   errors or warnings. Can you please confirm if the problem is still there?
 * Best regards,
   Daniel
 *  Thread Starter [lksecl](https://wordpress.org/support/users/lksecl/)
 * (@lksecl)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/ssl-certificate-problem-22/#post-17214783)
 * Hi Daniel,
 * the problem is still there. The problem is that a geolocation error occurs as
   soon as a user presses the “Show me where I am” button on a mobile device. I 
   suspect that this has to do with the fact that the page with the map is classified
   as unsafe.
 * Here you find a screenshot from the error message:
   [https://we.tl/t-M9ufYTBwHU](https://we.tl/t-M9ufYTBwHU)
 * Best regards,
   Lukas
 *  Plugin Author [100plugins](https://wordpress.org/support/users/100plugins/)
 * (@100plugins)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/ssl-certificate-problem-22/#post-17222171)
 * Hi Lukas,
 * **Problem:**
   This error happens because Safari is very strict with pages loading
   non-https content. Your page still loads some [http://&#8230](http://&#8230);
   content (see developer console in Chrome) and this makes it “unsecure” for geolocating
   in the Safari Browser. **Solution:**You need to make sure _everything_ on your
   page is loaded through your SSL certificate. Every http:// in the database must
   be replaced by https:// You can use [a plugin](https://themeisle.com/blog/add-wordpress-https/#install-and-configure-the-really-simple-ssl-plugin)
   to do this.
 * Best regards,
   Daniel
 *  [lillyscoot](https://wordpress.org/support/users/lillyscoot/)
 * (@lillyscoot)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/ssl-certificate-problem-22/#post-17235038)
 * file not available, please share file again i can help you in this

Viewing 4 replies - 1 through 4 (of 4 total)

 The topic ‘SSL Certificate Problem’ is closed to new replies.

 * ![](https://ps.w.org/open-user-map/assets/icon-256x256.gif?rev=3723910)
 * [Open User Map – Interactive Leaflet Maps](https://wordpress.org/plugins/open-user-map/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/open-user-map/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/open-user-map/)
 * [Active Topics](https://wordpress.org/support/plugin/open-user-map/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/open-user-map/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/open-user-map/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [lillyscoot](https://wordpress.org/support/users/lillyscoot/)
 * Last activity: [2 years, 10 months ago](https://wordpress.org/support/topic/ssl-certificate-problem-22/#post-17235038)
 * Status: resolved