Fresh install - no themes working

[MrAliKorn]

i did a fresh install of v 156a to prep for php 7.3 upgrade. here www.miyshops.com and no theme will show, the structure seems to be broke, how can i fix this?

[mc12345678]

Largely because of the protocol mismatch. It appears that a SSL certificate is supposedly installed; however, it is for a different domain name for one. When viewing the source code it appears that even when loading the page with http:// that the base href tag shows that have loaded the page with https:. When follow that link am told that the certificate is for a different domain: *.bravehost and that it should not be trusted.

To me it looks like a server misconfiguration for the following reasons:
Accessing the site using http:, the links within the page are generated with http: links suggesting that HTTP_SERVER still has http: in it. The base href tag is showing https: which suggests that one or more of the server settings identifying that the current page was reached using https: is falsely reporting that the page was loaded with https:. As a result proper browsers ignore the css code because of the mismatch between the address in the browser (http:) and the protocol to present the css (https: by way of the base href tag).

[MrAliKorn]

no SSL certificate was installed or defined during setup. how do i fix the "mismatch" problem?

[mc12345678]

no SSL certificate was installed or defined during setup. how do i fix the "mismatch" problem?

I would suspect that in includes/configure.php that ENABLE_SSL may be set to true:

define('ENABLE_SSL', 'true');

If it is, then suggest modifying the file (may require changing the permission level of the file and that it supports editing before saving the change(s).

I would also recommend that at least until a certificate is installed, to modify HTTPS_SERVER to begin with http: instead of https:

If when a certificate is installed, likely would want the entire site to be https: which would mean to change HTTPS_SERVER to begin with https:, HTTP_SERVER to begin with https:, and ENABLE_SSL to be 'true' instead of 'false'.

That should resolve the issue locally to not have that specific mixed content.

[MrAliKorn]

Thanks so much i knew it was something simple. that did the trick