October 8, 2018 at 7:35 am #223595
I'm converting my site to HTTPS and am running into a slew of issues with the CSS.
There are a number of instances where certain files are pulling http instead of https but when I look at the file there are no instances of http.
For example, "jquery-migrate.min.js?ver=1.4.1" is pulling an http instance but when checking the file it's not there.
I've deleted all plugins that are causing issues and ran the really simply ssl plugin to no avail.
Does anyone know how to fix? Have you ran across similar errors?https://www.accurateleads.com/October 8, 2018 at 8:26 am #223596Victor FontModerator
HTTP may be embedded throughout your database. Also, caching may be in play as well. If you accessed a file as http before, the browser or caching plugin may be remembering it that way.
On the page you asked us to look at, you have the following warning:
Your webserver is not forcing the use of SSL.
You may want to add a redirect to ensure a secure connection is used.
Contact your host to find out how to force HTTPS through htaccess.
October 8, 2018 at 8:32 am #223597
I actually previously forced HTTPS in the htaccess with a redirect and it broke the site. The CSS was not rendering correctly and it looked like a plain text site so I switched back.
After reaching out to Bluehost they said that it needed to be fixed on the web development end then when I forced the htaccess to push the https version the css would not break.October 9, 2018 at 7:08 am #223616Victor FontModerator
By switching from http to https, you are essentially changing the site URL. See this, https://codex.wordpress.org/Changing_The_Site_URL
If these steps don't work, then you need to use a plugin like better search and replace pro to scan through all of your database tables to find hard coded instances of http pertinent to your site and replace them with https:.
As an FYI, I've switched about 40 sites from http to https without ever experiencing the issues you describe. It's usually a seamless transition.
October 9, 2018 at 10:11 am #223618
I really appreciate the help here but am still perplexed as to what is going on.
If you run whynopadlock on the site it lists a slew of errors.
After running Search and Replace on all databases and there are no more instances of HTTP.
The htaccess has not been 301'ed to the https version and I've used really simple SSL to force js redirection to ssl.
I'm exhausting every possible cause here. If there is anything that you may believe could possibly work please let me know.October 9, 2018 at 1:24 pm #223621
For those reading this chain I wanted to point out a solution.
W3TC had been previously implemented and was removed but it still remained in htaccess and had to be removed.
Same scenario for cloudflare. These two were causing multiple issues.
Cloudflare is SSL compatible but bluehost does not allow you to utilized their shared ssl so you would have to use a paid version.
Basically check any CDNs, remove any caching plugins, implement really simple ssl and search and replace plugins, and make sure you htaccess is clean.
- The topic ‘Executive Pro Transition to HTTPS’ is closed to new replies.