If you are getting browser warnings about your certificate with a web browser, you should first check if it is a problem with the code on your page or the certificate itself.
The first step is to check if the certificate is working properly. The simplest way is to load a simple file, for example, an image, to check if the browser recognizes the certificate correctly. Assuming we have uploaded an image to our web server called logo.jpg, in our test domain abc-0123.com, we just type the full URL for that file in our web browser like the following example:
https://abc-0123.com/logo.jpg
If you obtain the green padlock without warnings, then the certificate is working properly and the problem is on your web page. Specifically, in the code in your page which is trying to load insecure elements. You cannot use insecure elements in a secure HTTPS connection since this invalidates the security while opening non-secure connections. So for web pages that will load under the secure HTTPS protocol, all the elements on that page, including links should necessarily use the same HTTPS protocol.
If you get warnings, it is because the HTML code in your webpage is trying to load resources or is linking to other elements in other pages using HTTP. By default, web browsers consider a secure page insecure if it contains even one single insecure element.
For example, if in our test page abc-0123.com we are loading the logo in the code like this http://abc-0123.com/logo.jpg, then when we access https://abc-0123.com, the web browser will show a warning or error. In this case, the logo will probably be blocked, not load or display warnings that insecure elements were found on the current page. The type of message and errors varies from web browser to web browser.
This is normal and the way web browsers work with secure connections today. It has no relationship to your SSL certificate. To avoid the errors with a secure page, you should use HTTPS in all the code and elements. You have to contact the webmaster or web designer to make the proper changes in your website code or web application. Once all the elements load under HTTPS in that page, you will not see any errors.
Unfortunately, there is no easy way to fix this without modifying the code in your web page. You should rewrite it to use HTTPS instead of HTTP.
You can check which elements are insecure or are causing browser warnings by checking the source code of that web page and looking for elements that contain HTTP instead of HTTPS.