Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this community
I was happily using Workbench as usual then after dinner I started receiving error message "UNKNOWN ERROR: read error on connection to ec2-34-194-152-137.compute-1.amazonaws.com:6379" for any Query. I tried different api versions and different browsers to not avail. Anyone having this error?
Edit: It works properly if you choose to use Bulk CSV or Bulk XML and download file to see results.
For doing SOQL queries an alternative tool to use is Salesforce Inspector (a Chrome extension). It is very easy to use.
26/06/2023 This solution did not work for me when I faced these issues again. So it may or may not work for you.
22/06/2023 I was facing a similar issue, I was able to resolve this issue by going to my User Settings and Revoking Workbench OAuth Apps setting.
Attaching a screenshot here -- >
28/06/2023 As a workaround you can use Bulk CSV options. I hope this helps
Looking at the closed pull requests on the project's Github, the issue appears to be fixed now. Using the "List" option for "View As" appears to be working in my limited, independent testing (tested using API v57.0 and v58.0).
workbench.developerforce.com is hosted on Heroku (the "developerforce" instance from here on), which in turn uses Amazon's AWS (hence "amazonaws" appearing in the error message).
According to the pull requests, the issue was related to Redis v6 (developerforce appears to use a Heroku add-on, "Heroku Data for Redis", as a session store for operation across multiple compute resources, or "Dynos" in Heroku parlance) and making a TLS connection.
Heroku started requiring TLS for connections to its Redis add-on for all but the "mini" instance (where TLS is supposedly only suggested rather than required) when using Heroku Data for Redis v6. URLs and port numbers may have changed, and this add-on uses a self-signed cert (which required some additional changes in setting up the TLS connection from PHP, namely disabling peer verification).
There was also apparently some work that needed to be done because the session save handler (in the Redis driver that PHP provides?) isn't able to handle TLS connections yet.
Shoutout to Ryan Brainard for putting in the work on this.
If you are having problems with Workbench connection to a specific org where you can successfully login to that org directly, you might want to ask your admin (if you don't have permissions) to go to Setup > Apps > Connected Apps > Connected Apps OAuth Usage:
Click the "User Count" link against Workbench, find your username and hit the "Revoke" action.
This will then require you to re-authenticate against Workbench with your credentials, potentially fixing your problem.
