Chrome devtools errors in production

Question

I have two errors with my rails application being deployed by heroku. The site: https://powerful-atoll-73299.herokuapp.com/. The first error is as follows:

Mixed Content: The page at 'https://powerful-atoll-73299.herokuapp.com/' was loaded over HTTPS, but requested an insecure image 'http://www.zastavki.com/pictures/1366x768/2008/Drawn_wallpapers_Family_tree_007294_.jpg'. This content should also be served over HTTPS.

I understand this error as it is pretty straight forward. So what I decided to do is to save the image onto my local machine and then put it into my project. So it was no longer trying to pull it's insecure link address. So now I refer to the image as: background: url("/family-tree.jpg") no-repeat center center scroll;. This works and has no underlying issues. What happens though, is when I push to heroku from my master branch that has the updated change... heroku version still keeps the insecure address link to the image. When I inspect the item you can even see that its using http://www.zastavki.com/pictures/1366x768/2008/Drawn_wallpapers_Family_tree_007294_.jpg instead of using /family-tree.jpg. The picture still shows when I replace the address with the photo location, but the error stays. Any idea to why this is occurring? Why does heroku have the address link of the picture when I push the actually local copy up?

Second error is as follows:

'//@ sourceURL' and '//@ sourceMappingURL' are deprecated, please use '//# sourceURL=' and '//# sourceMappingURL=' instead. codeschool devtools.js:1

I understand that this error is looking for me to replace @ with #. I am not sure where or how to do this. Any advice would be greatly appreciated. Again, all these errors are currently presenting themselves in production not development.

Answer 1

Possible Issues you might be facing, the assets aren't loaded after the deploy. Maybe a restart could do the trick heroku restart

EDIT

I went through your css code and it seems you still have that url set as background for your signup-section class in your css file.

ref:

.signup-section {
    width: 100%;
    padding: 50px 0;
    color: #fff;
    background: url(http://www.zastavki.com/pictures/1366x768/2008/Drawn_wallpapers_Family_tree_007294_.jpg) no-repeat center center scroll;
    background-color: #000;
    -webkit-background-size: cover;
    -moz-background-size: cover;
    background-size: cover;
    -o-background-size: cover
}

Update that and do a deploy, and you should be good to go.