siteRoot declaration causes asstes url corruption on deploy to HTTPS netlify
See original GitHub issueI’ve set my siteRoot to https://www.taximow.com
in static.config.js
After deploy, I navigated to http://www.taximow.com
and my site loaded correctly.
I’ve enforced SSL, and navigated to https://www.taximow.com
and I get network errors on each asset. - js, css, webp. - all of them.
I checked network tab and I found that links to assets has been changed

I commented out siteRoot in static.config.js
, redeployed, and things get back to normal. Except I do not have sitemap.xml
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
File-based configuration - Netlify Docs
Use a netlify.toml configuration file to specify how the platform builds and deploys your project.
Read more >HTTPS (SSL) - Netlify Docs
When you create a new site on Netlify, it's instantly secured at the Netlify-generated URL (for example, https://brave-curie-12345.netlify.app ). If you add a ......
Read more >Download build assets from any of your deploys - Netlify
We'll package up all of the assets from that deploy into one handy zip file for you to download. More information. Netlify Build...
Read more >Publishing your site assets with the Netlify CLI
Learn how the Netlify command line interface (CLI) can publish your web site assets to the Netlify hosting infrastructure for you with a ......
Read more >Some images producing 'failed to load resource' error on ...
Interestingly, which images show up in the build differ from deploy to deploy. ... https://asdfasdfasdf.netlify.com/ - does not find assets - deployed ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Okay, I’ve published version
5.1.2
that should fix it. Looking for at least two confirmations. Go!Reopen if issues persist!