Hi there @matam,

It does not look like a server configuration problem, it sounds like that you might have mixed content on the page which could be causing the not secure message in your browser.

Mixed content basically means that you have some resources like images, CSS, js files, or external resources loading from HTTP rather than HTTPS.

You can use this site here to show you which resources are not loading via https:

https://www.whynopadlock.com/

Just put the full URL that you would like to check this for and the site would give you a list of the resources which are loading via HTTP and you would need to update the references for them to HTTPS.

Another way to check that is via your web browser console, there you would also see a mix content warning for the specific resources.

Hope that this helps!
Regards,
Bobby