On Tuesday June 30th, we released some backend changes to the way Shotgun Desktop downloads updates from the Toolkit App Store. These changes were transparent to the majority of users, but caused problems for some studios. We rolled back those changes yesterday, reverting
v1.3.10 back to
v1.3.9, but we’re ready to release them again. We want to make sure you have the information you need to understand what’s going on and prevent disruption in your studio with the release.
Historically, when your Toolkit site configuration auto-updates, it downloads its components from the Toolkit App Store site,
tank.shotgunstudio.com. On Monday, we switched to uploading directly to AWS S3 cloud storage. We set up a proxy on our end,
s3-proxy.shotgunstudio.com, so that clients would not be accessing S3 directly to download updates. Nevertheless, the change required studios with a firewall or proxy to modify their filters to allow downloads from
s3-proxy.shotgunstudio.com or the IP addresses behind it.
A few studios with proxies were still getting download errors when Desktop tried to update their site config, even when they added
s3-proxy.shotgunstudio.com to their allow list.
On Wednesday July 1rst we rolled back from
v1.3.9. It was the safest way to go, but it prevents us from understanding how many people are really affected negatively by the changes we made.
We’re in communication with the studios that reported problems, and are locking them off on
v1.3.9 in anticipation of rereleasing
v1.3.10. We’ll work with these studios individually to make sure they’re configured properly to prevent future errors before bringing them back to
Next steps for you:
As we release
v1.3.10, in most cases, this should have no effect on your studio.
If you do get errors in Desktop like
Failed to download Toolkit App Store Config tk-config-basic v1.3.10. Error: Failed to download from 'https://tank.shotgunstudio.com' after 5 retries. See error log for details.
do the following:
- If your studio is filtering which sites can be accessed based on IP addresses, make sure the entire range of IPs required to download from the Tank AppStore is allowed.
- If you are filtering which sites can be accessed based on FQDNs (for example tank.shotgunstudio.com), you need to add
s3-proxy.shotgunstudio.comto your allow list.
If you make one of the above changes and still encounter issues, lock your site config off on v1.3.9 of
tk-config-basic, and contact email@example.com.
Locking off your site config:
To lock off your site config, go to a Pipeline Configuration entity page in Shotgun.
If you already have an entity with an empty “Project” field, this is your site config. If not, create one, with the following fields populated:
Project: Leave empty
Once you’re locked off, please contact us at firstname.lastname@example.org so we can help get you up and running with the
When you’re ready to go back to auto-updating, you can just clear the Descriptor field on the pipeline configuration.
We won’t be releasing We’ve released
v1.3.10 this week, but barring any blockers, we do plan to release on Monday. Let us know if you have any questions.
v1.3.10 Monday 10:30pm Eastern time.
Note that you’ll need to have this setup working by August 3. Please let us know if you have any issues.