[GH-ISSUE #1879] 400 Bad Request The plain HTTP request was sent to HTTPS port #1374

Open
opened 2026-02-26 07:30:43 +03:00 by kerem · 5 comments
Owner

Originally created by @Tarekdu13 on GitHub (Feb 22, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1879

Hello,
Started Nginx proxy manager with the same .yml file in the Documentation and when i go to :443 i get:
400 Bad Request
The plain HTTP request was sent to HTTPS port
openresty
i don't know what to do, any help would be great, thank you

Originally created by @Tarekdu13 on GitHub (Feb 22, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1879 Hello, Started Nginx proxy manager with the same .yml file in the Documentation and when i go to :443 i get: 400 Bad Request The plain HTTP request was sent to HTTPS port openresty i don't know what to do, any help would be great, thank you
Author
Owner

@trentwiles commented on GitHub (Feb 22, 2022):

The error is stating that you visited your website over HTTP, but on the HTTPS port. Can you visit https://yoursite:443?

<!-- gh-comment-id:1048013505 --> @trentwiles commented on GitHub (Feb 22, 2022): The error is stating that you visited your website over HTTP, but on the HTTPS port. Can you visit https://yoursite:443?
Author
Owner

@github-actions[bot] commented on GitHub (Feb 23, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1960626263 --> @github-actions[bot] commented on GitHub (Feb 23, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@Neustradamus commented on GitHub (Jan 18, 2025):

@trentwiles: It is linked to:

Have you solved this problem?

<!-- gh-comment-id:2599554529 --> @Neustradamus commented on GitHub (Jan 18, 2025): @trentwiles: It is linked to: - https://www.google.com/search?q=400+Bad+Request+The+plain+HTTP+request+was+sent+to+HTTPS+port+nginx Have you solved this problem?
Author
Owner

@ghost commented on GitHub (Mar 23, 2025):

had the same issue, followed this tutorial and did set this up via a project.

the port was the issue (810 as shown in the vid, did work), so prob. it was already taken or there were some other issues with it.

<!-- gh-comment-id:2746548817 --> @ghost commented on GitHub (Mar 23, 2025): had the same issue, followed this [tutorial](https://www.youtube.com/watch?v=S7p3_7YRaN4) and did set this up via a project. the port was the issue (810 as shown in the vid, did work), so prob. it was already taken or there were some other issues with it.
Author
Owner

@github-actions[bot] commented on GitHub (Oct 13, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:3395648400 --> @github-actions[bot] commented on GitHub (Oct 13, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1374
No description provided.