mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #995] Proxy nextcloud http to https will lose the port when using a custom port #833
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#833
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @YorhaL on GitHub (Apr 3, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/995
Environment: Use npm for proxy nextcloud http to https
Example: When using https://customnextcloud.com:2222, nextcloud will redirect it to https://customnextcloud.com
Modifying /etc/nginx/conf.d/include/proxy.conf can solve this problem
proxy_set_header Host $host; -> proxy_set_header Host $http_host;
@beermedlar commented on GitHub (Apr 18, 2021):
You also can fix this use
'overwritehost' => 'customnextcloud.com:2222',in config.php@github-actions[bot] commented on GitHub (Mar 15, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 26, 2025):
Issue was closed due to inactivity.