> 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/password-manager/knowledge-base/browser-extension-knowledge-base/issue-using-the-devolutions-password-manager-browser-extension-with-localhost-with-https.md).

# Issue using the Devolutions Password Manager browser extension with localhost with HTTPS

Fix Devolutions Password Manager browser extension connection failures to localhost over HTTPS caused by HSTS preload, using native messaging or list removal.

The Devolutions Password Manager browser extension does not support connecting to Remote Desktop Manager over HTTPS. You may experience connection issues in Devolutions Password Manager if your system's HSTS-preload configuration contains localhost.

To check if Devolutions Password Manager is attempting to connect over HTTPS, [inspect your browser's network tab](/password-manager/knowledge-base/browser-extension-knowledge-base/devolutions-password-manager-browser-extension-troubleshooting-connection-logs.md). The failed request to HTTPS should show in red.

### Solution

Either [use Devolutions Password Manager browser extension via native messaging](/password-manager/knowledge-base/browser-extension-knowledge-base/devolutions-password-manager-browser-extension-via-native-messaging.md) or remove localhost from your HSTS list.

{% hint style="info" %}
Since localhost is not part of the HSTS list by default, it must have been manually added or pre-loaded by a system or network administrator for a specific purpose. Removing it might lead to some unforeseen consequences.
{% endhint %}


---

# 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/password-manager/knowledge-base/browser-extension-knowledge-base/issue-using-the-devolutions-password-manager-browser-extension-with-localhost-with-https.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.