Hi everyone! I just wanted to inform SNOs of an in-progress update to the hosting of trusted satellite files (e.g. https://www.storj.io/dcs-satellites and https://www.storj.io/unpaid-community-satellites).
We are now hosting all of these files at the static.storj.io subdomain (e.g. https://static.storj.io/dcs-satellites and https://static.storj.io/unpaid-community-satellites).
Eventually, we will stop hosting these files directly at www.storj.io, and these URLs on www.storj.io will redirect to static.storj.io. Storage nodes will continue to function properly with the www.storj.io subdomain, but it is preferable to switch over to static.storj.io in your config in order to avoid an unnecessary redirect.
The default config for the trusted satellites URL has been updated to use static.storj.io as of v1.114, but this only affects storage nodes who have not overridden this configuration. If you have overridden this “sources” configuration, I suggest replacing www with static in your config.
If I may ask, why the change over to subdomain.domain.tld from the previous URL ?
Also currently static.storj.io leads to 
If I may suggest, this path could have both the dcs and community satellite urls as
If I may ask, why the change over to subdomain.domain.tld from the previous URL ?
The main reason is that we (eventually) would like to have a simpler/more straightforward infrastructure for www.storj.io.
Currently, the www subdomain points to a server that we operate (the very same server used for the static subdomain). If the request is for a static file hosted on the server (like dcs-satellites), that file is served directly. If not, the server acts as a reverse-proxy to our website. Our current website hosting provider does not provide the capability of directly hosting static files (among other features), so we ended up relying on this reverse-proxy infrastructure to support additional features on the www subdomain.
There are features on our website hosting provider which we can only use if we point DNS directly to the hosting provider, rather than going through a proxy. This is not urgent, but eventually it would be nice to bypass our proxy for www.storj.io, which requires hosting static files elsewhere.
If I may suggest, this path could have both the dcs and community satellite urls as
Thanks for the suggestion, I will have to think about this. Trusted satellite files are not the only thing served on this server - we also have the whitepaper, marketing assets, and other files (like the Tardigrade game!) there. A complete directory of files served at static.storj.io would probably be a little messy. A partial directory like what you’ve suggested might be good, but I’d want to discuss it more before deciding how to move forward.
Thank you for the explanation. I learned something new today 
Right now the nodes on 1.114 cannot work:
Good to know. We are not planning to make any DNS/infrastructure changes to www.storj.io for now. I plan to wait for most storagenodes to be using the new config before that.