# Page Not Found

The URL `2.33-lts/faqs/troubleshooting/access-and-authentication/client-sent-an-http-request-to-an-https-server` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Client sent an HTTP request to an HTTPS server](https://docs.portainer.io/faqs/troubleshooting/access-and-authentication/client-sent-an-http-request-to-an-https-server.md)
- [Unable to Login via LDAP in Portainer](https://docs.portainer.io/faqs/troubleshooting/access-and-authentication/unable-to-login-via-ldap-in-portainer.md)
- [Unable to Authenticate After Portainer Update](https://docs.portainer.io/faqs/troubleshooting/access-and-authentication/unable-to-authenticate-after-portainer-update.md)
- [How can I switch back to internal authentication?](https://docs.portainer.io/faqs/troubleshooting/access-and-authentication/how-can-i-switch-back-to-internal-authentication.md)
- [How do I reset my Portainer password?](https://docs.portainer.io/faqs/troubleshooting/access-and-authentication/how-do-i-reset-my-portainer-password.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.portainer.io/faqs/troubleshooting/access-and-authentication/client-sent-an-http-request-to-an-https-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.portainer.io/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.portainer.io/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/faqs/troubleshooting/access-and-authentication/client-sent-an-http-request-to-an-https-server.md`).

You may also use `Accept: text/markdown` header for content negotiation.