mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2341] Route to external host without port? #1655
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#1655
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 @popfendi on GitHub (Oct 23, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2341
I love the simplicity of this tool, and am currently using it to route requests to my static site and api hosted on the same server.
However i'd like to also route traffic to a Object storage bucket which has the url pattern https://eu2.contabostorage.com/access-key:bucket-name/filename.jpg
I'm having trouble routing from mysite.com/images/filename.jpg as the NPM dashboard wont allow for a hostname with no port.
When I add port 443 for example the url is https://eu2.contabostorage.com/access-key:bucket-name/:443
Is there any solution for routing to an external domain like this? I need to be able to pass the filename as a path variable too.
Many Thanks.
@the1ts commented on GitHub (Nov 2, 2022):
Perhaps some pictures may be helpful. I'm not able to understand what you are putting where in the UI and what you expect to happen from those fields.
Since for example, https:// is always used as :443 in browsers unless stated otherwise in the address bar.
@github-actions[bot] commented on GitHub (Feb 7, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 23, 2025):
Issue was closed due to inactivity.