Hi,

Thank you for contacting us with this information.

Currently, this is necessary to set up proxy setting for the IDE manually in the config file and I will provide you with a solution for this case.

In the attachments, you can find the necessary config file - please download it, unzip, and paste to the folder where you are going to install the IDE. After this, please launch TWS installation again.

Please let me know if this helps to solve the issue you are faced with.

As for the unaccessible checkboxes, the reason for this is that we couldn't load the License Agreement information - this is why there is no ability to accept license conditions.

Thank you,

Kate

Thank you for looking into this.

I tried to follow the instructions and add the file "TheWelkinSuiteSetup-Bloom-Sep20.exe.config" to the location of TheWelkinSuiteSetup-Bloom-Sep20.exe as well as the future installation directory (which I think is irrelevant at that point, since there isn't any selection to be made before the error occurs).

I observed the following:

• Application starts
• It creates 2 random directories in the user's temp directory
• One contains a copy of the installer
• System indicates "downloading TheWelkinSuite.msi"
• The second random directory contains TheWelkinSuite.msi and WelkinSuite.Bootstrapper.Managed.exe (and a bunch of other files)
• Error is displayed - when I click on refresh in the error page the error changes to "Can't securly connect"
• Clicking on cancel removes both temp directories and their content

Investigating more...

Partial success ;-)

I copied the file TheWelkinSuite.msi from the temp directory before it was deleted by canceling the installation. When I ran that one, it updated the existing R9 installation to R10 - so far it seems to be complete.

However when starting the IDE (I did set homepage as default), it fails to connect to https://www.thewelkinsuite.com with "Navigation cancelled" and when I click on "What you can try" - Refresh page. It says: "Can't securly connect to this page" complaining about insecure TLS. I can navigate to other websites and it looks like using the proxy properly.
It does load the license information properly and I can open my project from Salesforce.

When I close the suite I get another message:

The Welkin Suite has detected that an operation is blocking user input. This can be caused by an active modal dialog or a task that needs to block user interaction. Would you like to shut down anyway?

What doesn't seem to work is OAuth. When I add an organisation the browser redirects to localhost:1717 and errors with a "empty reponse received" and an error "Connection Reset" on the WelkinSuite side.

Hi Stephan,

Thank you for your response, updates, and all the investigations!

Now, this is necessary to add the proxy settings to an existing TWS config file to allow the proper connection directly from the IDE.

Please follow the next steps for this:

     1) please open the 'C:\Program Files (x86)\The Welkin Suite\The Welkin Suite' folder (if you used it for TWS installation);

     2) find the 'TheWelkinSuite.exe.config' file and open it using any text editor;

     3) add the next line within the <system.net> tag: <defaultProxy useDefaultCredentials="true" />.

Please let me know if this helps you to get all the IDE's functionality available on your current environment.

As a side note, we are going to add this setting to the IDE by default in one of the nearest TWS versions.

Thank you,

Kate

I started over with a new install. The process of "capturing" (a.k.a copy away) the temp files and add the config for the proxy works for a clean install too. However... next challenge. I tried to add an Org with oAuth and it fails at the localhost:1717 part. (I added a firewall rule on Windows to open it up).

The browser first says: "empty response" and then "refused to connect"

The error on the Welkin site was:

Failed to perform operation
unable to verify the first certificate

I've encountered such an error before with nodejs and npm. The solution there was to add to the .npmrc:

• npm config set strict-ssl false
• npm config set sslVerify false

I suspect there's something similar in the config for Welkin?

Next insight...

SFDX uses port 1717 as default for oAuth. Unfortunately the security package in use here does use that port too.

Looking into reconfiguring that.

Hi Stephan,

Thank you for your posts.

May I please ask you if you have changed 'TheWelkinSuite.exe.config' file with the additional setting for proxy after the repeated installation?

Also may I please ask you a couple more questions:

     1) Can you please tell me if you are creating a regular Salesforce project or SFDX project?

     2) If you are trying to create the SFDX project, can you please open your command line and execute, for example, the "sfdx force:org:list" command? Would it complain about the 1717 port being used?

     3) Is it possible for you to change the configuration of the security software/hardware used in the network to not use & allow usage of the 1717 port?

In the case if SFDX CLI would return an error about the 1717 port and if there is no possibility to change the security software configuration - the only solution we can provide in this case is to contact the support of the Salesforce DX CLI, as we are not able to do any changes in it.

Thank you,

Kate

What worked

I got it to work (finally). The firewall is quite a headache. This is the documentation what finally worked - as reference for others.

The problem was mainly "other" moving parts

Actors

There are quite some moving parts involved that need attention:

• Windows firewall: make sure port 1717 is open (and not used by something else)
• NodeJS, NPM and yarn (yarn is used for plugin installation in sfdx)
• The SFDX executable
• (optional) SFDX plugins
• The Welking Suite

What worked is to test "bottom up": Node/NPM, SFDX and finally the Welkin Suite

For the sake of this documentation we presume the proxy is http://192.168.44.44:4444 (Chinese will understand the joke with 44.44)

Steps

Set environment variables

• HTTP_PROXY=http://192.168.44.44:4444
• NODE_TLS_REJECT_UNAUTHORIZED=0
  (Replace that with proper pointing to the Firewalls PEM file please!!)

Stuff to install

• nodeJS: download binaries from https://nodejs.org/en/
• sfdx: download binaries from https://developer.salesforce.com/tools/sfdxcli
• (later after npm config) Yarn: npm install -g yarn

Commands to configure

<configuration>
	<system.net>
		<defaultProxy useDefaultCredentials="true" enabled="true" >
		</defaultProxy>
	</system.net>
</configuration>

1. Run the installer. It will fail at the point where the licence agreement would be displayed. Don't click on cancel yet
2. Search for the temp directory that contains the file TheWelkinSuite.msi -> Copy the entire directory somewhere else
3. Click on cancel in the failed dialogue. The temp directory will disappear
4. Create the file TheWelkinSuite.msi.config as above in the same directory as TheWelkinSuite.msi
5. Run the TheWelkinSuite.msi (double click) in the saved directory -> this will install the application.
6. Look for the file 'TheWelkinSuite.exe.config' file and open it using any text editor
7. Search for the tag <system.net> and add <defaultProxy useDefaultCredentials="true" enabled="true" />
8. Run the WelkinSuite -> should work

I realized that on failing authentication the nodeJS task handling oAuth on port 1717 didn't shut down correctly (might be the machine) - so if you failed once with login, you might need to shut down the nodeJS taks in task manager.

Caveat!

This setup switches off https certificate checking. You should replace it with proper chain of SSL/TLS certificates on your Windows configuration and potentially use the NodeJS parameter "NODE_EXTRA_CA_CERTS"

Thx to Kate for the pointers, appreciate the help rendered. Happy camper here

Hi Stephan,

This is great!

First of all, I'm glad that now you have a full access to all The WelkinSuite functionality, and I hope there won't be a necessity to go through all the steps again.

The next one - thank you for your investigation and for the detailed instructions how to handle the issue.

Please let us know if you would have any other questions. We will be happy to assist.

Best Regards,

Kate