Unable to Perform Force Deploy Due to Connection Error

[akippiko]

Until this morning, I was able to perform a Force Deploy after saving, but after turning off my computer and starting to use it this afternoon, I encountered the following error when attempting a Force Deploy, and now I can no longer deploy:

Connection Failed

ConnectException invoking https://xxxx/services/Soarp/m/62.0/xxxx: Connection refused
When I run a Connection Test for the project, I receive a "Connection Succeeded" message, but immediately afterward, it also displays "Connection Failed."

MacOS 13.7.2

WebStorm 2024.3.1.1

IC 2.3.4.1

[Scott]

“Connection refused” would indicate that either the server was (temporarily) unavailable, or some intermediate network device — router, proxy, firewall, etc. — is refusing the connection.

Has the issue persisted or is it now resolved? If it’s resolved, it was a temporary Salesforce server outage which, while rare, does occur. If it’s still present, does it happen with other orgs or just this one?

If you’d like get more details, you can add the following to Help | Diagnostic Tools | Debug Log Settings:

com.illuminatedcloud.intellij.client.ForceComApiClient com.illuminatedcloud.intellij.client.ForceComApiClient!trace

Then restart the IDE (required to reinitialize the SOAP client), and all SOAP and REST API calls will be logged in detail. Note that this can include private information such as passwords and security tokens, so if you share your idea.log file for review, please redact any private information before doing so. Feel free to send a log via email and I’ll be happy to take a look.

Once that logging is no longer needed, remove those entries and once again restart the IDE to ensure that SOAP and REST API calls are no longer being emitted into the log.

Regards,
Scott Wells

​

[Scott]

Closing the loop on this, after extensive troubleshooting, the issue was ultimately resolved by uninstalling and reinstalling WebStorm. Obviously something had ogtten into a weird/bad state in the existing install, and a reinstall put things right again.

Unfortunately this is not at all uncommon with both the host JetBrains IDE and the Salesforce CLI when the respective software is updated in-place repeatedly over time. All too often when one user is seeing odd behavior that's unreproducible locally by me and has not been reported by any other users, a clean uninstall (clean being very important for the Salesforce CLI) followed by an install of the latest version will resolve it. And both the IDE and the CLI can (generally) be reinstalled quickly without any loss of configuration.

I've reported these types of issues with repeated in-place updates to both JetBrains and Salesforce respectively, but needless to say, these aren't easy-to-reproduce problems, so there's generally not much that they can do to help.

Anyway, I'm just leaving this as a sort of public service announcement that sometimes if you're seeing something weird -- especially if it's reproducible outside of IC -- you might just try the proverbial "have you tried turning it off and back on again" appproach, as embarrassing as it may be to recommend.

Regards,

Scott Wells