In other words you want two different servers have to be able to be accessed via the same public IP and port only selected by the used FQDN. The solution is to use "virtual hosts" (as apache calls this method), see e.g. https://httpd.apache.org/docs/2.4/vhosts/examples.html
In other words you want two different servers have to be able to be accessed via the same public IP and port only selected by the used FQDN. The solution is to use "virtual hosts" (as apache calls this method), see e.g. https://httpd.apache.org/docs/2.4/vhosts/examples.html
Sorry for my english but I will try to explain.
I have VM with nginx proxy in LAN segment where Jira located. From WAN ip of proxmox - port 443 redirected to LAN ip of proxy where nginx proxy forward requests to jira LAN ip port 8080. For example WAN ip (proxmox) 22.22.22.22:443 -> (nginx proxy) 192.168.1.10:443 and routing by domain name to -> (jira server) 192.168.1.200:8080. For example. Jira have address jira.example.com (22.22.22.22) and another server confluence.example.com (22.22.22.22) both in same LAN segment on same Proxmox host. For application linking they must resolve each other domain and access ports 8080 (for jira) and 8090 (confluence). I solve this with internal DNS that redefine DNS records for jira and confluence with LAN ips. Application linking working. But for corrects work of gardets URL in Jira base url (https://jira.example.com) port 443 must be accessible from jira server itself but it can't because it has LAN sergment IP in DNS and jira server don't have 443 port configured on jira LAN ip. It configured on nginx proxy.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.