mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #111] n00b quiestion: Use proxy host on LAN #98
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#98
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 @Kitser on GitHub (Mar 26, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/111
I'm a total Nginx / reverse proxy n00b.
But I was able to install this and create a proxy host. So now my internal application (Home Assistant) running on HTTP and port 8123 is reachable from the WAN on my HTTPS DuckDNS domain name without adding port 8123. Great!
On my Android phone, I created a shortcut for accessing Home Assistant using my HTTPS DuckDNS address. On 4g this works great. But when I'm on my own LAN it doesn't.
Is there I way to let Nginx "redirect" the clients to my local HTTP address they try to accessing my HTTPS DuckDNS address when they are on the same LAN?
@Kitser commented on GitHub (Mar 26, 2019):
Apparently, I did make a DNS entry in my router in the past. I deleted it and now I can just browse to my DuckDNS HTTPS domain to access my local HTTP Home Assistant instance.