Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Trusted Contributor.. lashari1 Trusted Contributor..
Trusted Contributor..
1575 views

Visual Studio plugin not connects to SSC

Dears,

The Visual Studio plugin cannot connect to the SSC. AWD connects perfectly from the same computer.

SSC, SCA 18.20

Visual Studio 2017

VS-15.0-18.10 log file:

2018-12-12 15:53:29.619 [ERROR] RemediationCommon.Commands.ConnectToSscCommand.CheckPermissionOnSSC - Exception during authenticating with SSC
2018-12-12 15:53:29.619 [ERROR] RemediationCommon.Commands.ConnectToSscCommand.CheckPermissionOnSSC - Unable to connect to the remote server
at Fortify.WebServices.Client.ProjectClient.getProjects()
at RemediationCommon.Commands.ConnectToSscCommand.CheckPermissionOnSSC()
2018-12-12 15:53:29.619 [ERROR] RemediationCommon.Commands.ConnectToSscCommand.CheckPermissionOnSSC - No connection could be made because the target machine actively refused it 127.0.0.1:8180
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

server.property file:

rp.update.from.manager=false
uploadclient.proxy.pass=
install.auto.upgrade=false
uploadclient.proxy.user=
uploadclient.proxy.server=
rulepackupdate.proxy.server=
oneproxy.https.proxy.port=
oneproxy.http.proxy.user=
rulepackupdate.proxy.port=
rulepackupdate.server=https\://update.fortify.com
oneproxy.https.proxy.pass=
uploadclient.server=http\://xxx-fortify.xxxxxxxxxxx.local\:8080/ssc
rulepack.days=15
rulepack.auto.update=false
rulepackupdate.proxy.pass=
uploadclient.proxy.port=
oneproxy.http.proxy.server=
fpr.upload.to.manager=true
oneproxy.https.proxy.user=
oneproxy.http.proxy.pass=
oneproxy.http.proxy.port=
oneproxy.https.proxy.server=
rulepackupdate.proxy.user=
autoupgrade.server=http\://localhost\:8180/ssc/update-site/installers

Where does "127.0.0.1:8180" come from?

Could you give me some advise?

Thanks

 

Labels (2)
0 Likes
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: Visual Studio plugin not connects to SSC

Port 8180 seems like an artifact put into the defaults, since our SSC Demo Suite uses that port for our demo systems.

It was unclear if your screen shot was from the VS settings or Fortify, or if it was the similar settings for your AWB tool.  The connection error seems like a network or proxy server complaint.  Do the SSC URLs match in both settings screens, for VS and for AWB?  Does either tol have a Proxy configuration that the other one needs?  The entry for "autoupgrade.server" is likely related to the feature in AWB where it can auto-check for installation updates from a local SSC Server, if the admins have staged installers and configured that separate function in-house.


-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.