|License Type||SaaS & On-Premise|
|Agent Mode||Assess & Protect|
|Main Product Category||.NET Agent|
You're experiencing one or more of the following symptoms:
- The .NET agent doesn't start successfully.
The Contrast Tray and/or .NET agent logs report errors when connecting to the Contrast application:
> Contrast .NET service failed to start. Contrast .NET cannot connect
to TeamServer at: https://app.contrastsecurity.com. The remote name
could not be resolved: app.contrastsecurity.com
Data from a server with the installed agent doesn't appear in the Contrast interface.
Open the .NET agent's configuration file, contrast_security.yaml, which is located in the agent's working directory (i.e., %ProgramData%\Contrast\dotnet\). Then:
- Verify that the URL value is correct. It should look similar to the following, although will vary if you have an on-premise Contrast UI install:
api:Check the URL can be reached from a normal web browser on the server. If it can't be reached, you should review the network path and related settings between the server and the Contrast application.
- Verify proxy settings. If a normal web browser can connect to Contrast but the agent can't, the agent might be missing the proxy settings required by your network environment. You can configure a proxy using the following settings:
url: <proxy url with port and scheme>
user: <proxy user if required>
pass: <proxy password if required>
auth_type: <proxy auth type>
Verify that the API key is correct. If the above settings are correct, the API key used by your organization might have changed. Follow these directions to view your current API Key.
More information on the .NET's configuration can be found here. All properties can also be set as environment variables - this is especially useful if it's not possible to store the proxy password in a configuration file.