> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/password-manager-pro-issues.md).

# Password Manager Pro issues

Fix Password Manager Pro integration errors in Remote Desktop Manager, such as protocol violations and token or host failures, by correcting the API user configuration.

### System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine

During the configuration of your Password Manager Pro credential entry, make sure that the URL of your server contains `https://` and not `http://`. You absolutely need an `https://` at the beginning of the address to communicate properly with the server.

### When you try to connect on a remote computer or get the credential list, a window appears with an empty token field and the username and workstation field greyed out

The host name configured in your API user in Password Manager Pro is not the same that you have configured in Remote Desktop Manager in ***File*** – ***My account settings*** – ***Password Manager Pro***. For more information on the configuration, see [Configure Password Manager Pro in Remote Desktop Manager macOS](/rdm/knowledge-base/how-to-articles/configure-password-manager-pro-in-remote-desktop-manager-macos.md).

### Api key received is not associated to any user. Authentication failed

Edit your API user in Password Manager Pro and generate a new ***Authentication Token***, save your API user and save this new token in Remote Desktop Manager in ***File*** – ***My account settings*** – ***Password Manager Pro***.

### User is not allowed to access from this host

During the creation of an API User in Password Manager Pro, a ***Host*** (Computer name) is necessary to create the user. In Password Manager Pro it may be registered using the ***Fully Qualified Domain Name (FQDN)*** of the computer. In Remote Desktop Manager on the other hand, you must set it exactly the same as the %COMPUTERNAME% environment variable.

Another reason for this error we have seen is that the DNS name of the server was specified, but it would work perfectly fine if you were using the IP address instead. Please test it with the procedure described below.

### Testing procedure with PowerShell

Here is a script that you can use to test your access from a client workstation. Save the following code in a file called PMPTest.ps1. The script calls the same REST API as Remote Desktop Manager, so it shows whether the workstation can reach the server and whether the token is accepted. Run it in Windows PowerShell 5.1, since the certificate bypass it uses is not supported in PowerShell 7.

```powershell
[CmdletBinding()]
Param(
[Parameter(Mandatory=$True,Position=1)]
[string]$PMPServer,

[Parameter(Mandatory=$True,Position=2)]
[string]$AuthToken
)

add-type @"
using System.Net;
using System.Security.Cryptography.X509Certificates;
public class TrustAllCertsPolicy: ICertificatePolicy {
public bool CheckValidationResult(
ServicePoint srvPoint, X509Certificate certificate,
WebRequest request, int certificateProblem) {
return true;
}
}
"@

[System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy
cls
$connect = "https://" + $PMPServer + ":7272/restapi/json/v1/resources?AUTHTOKEN=$AuthToken"
$result = Invoke-WebRequest -Uri $connect
$form = $result.Content
$content = ConvertFrom-Json $form

$status = $content.operation.result.status

if ($status -eq "Success") {
$content.operation.Details
}
if ($status -eq "Failed") {
$status
$content.operation.result.Message
}
Pause
```

{% hint style="info" %}
The port is hard-coded in the script to 7272, which is the default value for Password Manager Pro. Adapt it to your environment
{% endhint %}

From within Powershell, type the following:

`.\PMPTest.ps1 {YOUR_PMP_SERVER} {YOUR_PMP_TOKEN}`

Test with both the DNS name of the server and the IP address and observe the results.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/password-manager-pro-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.