Quantcast
Channel: Seth Guthrie's Communities Activities
Viewing all articles
Browse latest Browse all 6718

Bentley Cloud Services Portal and CONNECTION Client FAQ

$
0
0

 Product(s):Portal & CONNECTION Client
 Version(s):All
 Environment:N\A
 Area:Access
 Subarea:N\A

Question:

How can I find the Bentley.Connect.Client.exe.log?

You can retrieve the log file from C:\Users\User Name\AppData\Local\Bentley\Logs or use this shortcut in the browser address bar %localappdata%\bentley\logs\

Question:
What Bentley (DNS) domains does the CONNECTION Client  and Bentley Cloud Service portal need to have access to?  

Recommendation: whitelist *.Bentley.com
Or:
buddi.bentley.com
ims.bentley.com
waz-search.bentley.com
connect-agreement.bentley.com
connect-wsg20.bentley.com
connect-recommendation.bentley.com
connect-updatev1.bentley.com

(Optional) depending on how your system is managed you may need to add additional URLs:
services.bentley.com
www.google-analytics.com
bentleysystems.122.2o7.net

Question:
Is there a specific Port that needs to be open?

The above URL are accessed via Port 443

Question:
If I have a proxy server where do I enter the server name, user name, and password in the CONNECTION Client?

You can enter proxy information in the License Management Tool. To locate the License Management Tool go to  C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation and double click the LicenseTool.exe, or File tab > Tools > License Management. In the License Management Tool go to Tools > Options > Proxy Configuration tab > Enter the information > Click Apply > OK.

***Please note that this option only works if you're using the online SELECTserver. If you're using an in-house SELECTserver you'll need to create an exception on the proxy server for traffic originating from the CONNECTION Client.***

For Bentley Navigator CONNECT Edition version 05.04.02.14 you have to create an environment variable with the proxy information. 

https_proxy=username:password@machine-name:port  -for authenticating proxies 
https_proxy=machine-name:port -for non-authenticating proxies

Example of non-authenticating: https_proxy=127.0.0.1:8888

Newer version 05.05.01.35 works like the CONNECTION client and uses the proxy settings from the License Management Tool. 

See Also

CONNECTION Client Support Solutions


Viewing all articles
Browse latest Browse all 6718

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>