# Need a Developer to Clean Up (and fix) Roots Install **URL:** https://discourse.roots.io/t/need-a-developer-to-clean-up-and-fix-roots-install/11095 **Category:** jobs **Created:** 2017-12-08T22:05:24Z **Posts:** 24 ## Post 1 by @Chris_Palmer — 2017-12-08T22:05:24Z Hey all, If you look at [my website](http://flyaoamedia.com) you can see that the theme is no longer working. This happened just a few days ago, and I haven’t been able to pinpoint the issue, even with restoring backups. I’m in urgent need of a developer to have a look at this. Please email me or text me at 907 .299.7359 Thanks --- ## Post 2 by @alwaysblank — 2017-12-08T22:10:07Z Looks like at least part of your issue is that you’re serving the site on `https` but your certificate’s bad: ![image](https://discourse.roots.io/uploads/default/original/2X/b/b245831782ed11a04c708774925794ae5f492ddb.png) ![image](https://discourse.roots.io/uploads/default/original/2X/0/054ec36747080c367f4f22cd258866e114b8f17f.png) …and that’s causing most of your assets (CSS, JS, images, etc) to not load: ![image](https://discourse.roots.io/uploads/default/original/2X/c/c1b44844f82697d2675f1b68ad7b6b738a529530.png) Looks like it’s a Let’s Encrypt cert, so if you’re managing the site yourself, you can probably renew/regenerate it. Otherwise you should talk to your host and get them to do that. (For reference, a functioning Let’s Encrypt certificate would look more like this: ![image](https://discourse.roots.io/uploads/default/original/2X/1/1e2037b8cf2dfe2ee3b0aaaedef30bd578f78f0b.png) --- ## Post 3 by @MWDelaney — 2017-12-08T22:28:15Z If it’s a Trellis site, [this issue](https://github.com/roots/trellis/pull/921) (resolved in that PR) could explain the expired cert. it’s neen about enough time for non-updated sites to be expiring. --- ## Post 4 by @Chris_Palmer — 2017-12-08T22:36:20Z Cool. I’ll start to talk to them. --- ## Post 5 by @MWDelaney — 2017-12-08T22:40:18Z I’m also happy to take a look this weekend if you can’t get it resolved. --- ## Post 6 by @Chris_Palmer — 2017-12-08T22:52:06Z This website is my livelihood, so I’d rather get it resolved sooner than later. Tech support is looking again. I was on with them earlier and all they did was try to search/replace anything from http to https for mixed content, and also tried to do a restore. I just don’t understand the issue. --- ## Post 7 by @MWDelaney — 2017-12-08T22:54:14Z > [@Chris_Palmer](#): > > I was on with them earlier and all they did was try to search/replace anything from http to https for mixed content Well that’s troubling. The solution to a once-working site with an expired certificate isn’t to remove the certificate, it’s to renew it. Can you tell us who your hosting is with? --- ## Post 8 by @Chris_Palmer — 2017-12-08T23:54:16Z The certificate is brand new. And they didn’t even try renewing it. Didn’t cross their minds, I guess. Hosting with WPEngine. They’re usually pretty awesome and I’ve never felt there’s been a safer place for my website. But, you know how it is sometimes dealing with entry level IT support. Again, they’re usually good. --- ## Post 9 by @alwaysblank — 2017-12-09T00:22:46Z Yeah, it’s 100% a certificate issue. If I tell Firefox to ignore its concerns about the validity of the cert, the site loads fine: ![](https://screenshots.firefoxusercontent.com/images/2519a080-c25b-49ee-ac89-12b3a58c316f.png) This is definitely an issue WPEngine can and should be fixing for you. --- ## Post 10 by @Chris_Palmer — 2017-12-09T00:46:23Z Frustrating. Just want it fixed. I’ll get on their case again here soon. --- ## Post 11 by @Chris_Palmer — 2017-12-09T02:02:34Z Was just on the phone with WPEngine and they said they couldn’t do anything to help. They said that the http calls were deep in the theme files and it kept trying to force those calls. So, perhaps that’s true. If there’s something forcing it to do the http vs https, then I can imagine it would throw up all those warnings. And if the SSL is also trying to force all the URLs to https, then it would just go in circles. My understanding is limited. Can someone help out here? Really, I need to hire someone to dive in and take a look at this. @alwaysblank @MWDelaney --- ## Post 12 by @alwaysblank — 2017-12-09T02:16:33Z I won’t be near a computer for a couple hours, but if @MWDelaney hasn’t shown up I can probably hop in and take a look. --- ## Post 13 by @MWDelaney — 2017-12-09T03:41:30Z I’m not available until tomorrow, so it’s all you if you’re around. --- ## Post 14 by @MWDelaney — 2017-12-09T04:12:02Z @Chris_Palmer, for whomever is able to help first, here are some questions we’ll need the answers to: Who created the theme and site and why are they not involved at this point? Who set up the SSL certificate? Why can’t we renew the certificate? Do you have access to the source files for the theme, or is what’s on the site the only thing available? --- ## Post 15 by @alwaysblank — 2017-12-09T05:29:53Z I’m back home, and I’ll be around all weekend. Send me a PM if you want me to take a look. --- ## Post 16 by @Chris_Palmer — 2017-12-09T05:35:56Z I’m not sure I have the rights to PM. Don’t see where I can do that. Shoot me a text at nine oh seven 299-7359 and we’ll find a way to message each other. @alwaysblank --- ## Post 17 by @alwaysblank — 2017-12-09T06:12:34Z Just sent you a PM. You should be able to find it at [https://discourse.roots.io/u/Chris\_Palmer/messages](https://discourse.roots.io/u/Chris_Palmer/messages) --- ## Post 18 by @MWDelaney — 2017-12-09T15:17:43Z I also sent a PM just now, @Chris_Palmer. If @alwaysblank got to you first then definitely work with him! He’s halfway decent at this stuff I guess :wink: --- ## Post 19 by @fullyint — 2017-12-09T18:15:08Z At first glance, the cert seems fine, not expired, at least now, a day later than OP. Seems like just a mixed content issue. > [@Chris_Palmer](#): > > Was just on the phone with WPEngine and they said they couldn’t do anything to help. They said that the http calls were deep in the theme files and it kept trying to force those calls. Any chance this is a bedrock-based site with a `.env` file that was recently mistakenly updated to have `http` in [`WP_HOME` and/or `WP_SITEURL`](https://github.com/roots/bedrock/blob/9a266d86c38772ddf67b27a070f79aa835adc854/.env.example#L10-L11) (e.g., during a recent WP update)? If you have an `.env` file, you could double-check that `WP_HOME` and `WP_SITEURL` have `https`. --- ## Post 20 by @Chris_Palmer — 2017-12-09T18:54:50Z @alwaysblank Thoughts on this? --- ## Post 21 by @alwaysblank — 2017-12-09T19:25:01Z @Chris_Palmer I agree w/ @fullyint that it’s probably a mixed content issue. I don’t believe your site is a Bedrock site. The site/home urls in your database have the correct protocol. Your `wp-config.php` did statically define those URLs (to the wrong protocol) at one point, but they were commented out before I started looking at it. I went back and took another look at the theme files, and while there were a number of non-https hard-coded URLs, there are a number that _are_ using what should be the correct functions to get URLs, so it seems like there’s _something_ in there telling WordPress it’s on a non-SSL site. --- ## Post 22 by @MWDelaney — 2017-12-09T19:28:28Z Isn’t there a setting in WordPress to set your URL? --- ## Post 23 by @Webstractions — 2017-12-09T21:59:26Z Maybe force all requests to Https in .htacess? --- ## Post 24 by @Chris_Palmer — 2017-12-10T00:41:45Z @MWDelaney What’s your email? It’s limited the messages I can send on here. Would like to have you jump in and give this a shot.