vmsman wrote: ↑
Fri Aug 21, 2020 1:08 am
On the LAN side, I get an "unable to connect". If I connect to my VPN provider which tunnels my client off network, I can login and use my PHPBB just fine.
The first hurdle you're jumping through there is name resolution, i.e. DNS. Meaning when _I_ try to get to your https://community.mydomain.com/
page (or when you do through a VPN so that you're hitting the public side just like I am), I'm going to the DNS server registered for your domain, and receiving the answer of what IP address to go to from that DNS server, and attempting to make the HTTP(S) connection to that IP address.
When you're inside on the LAN, you're probably talking to a DNS server defined by your local network setup. And if "mydomain.com" is "your company's domain", then you might be getting answers from a local DNS server for that same domain, rather than using the public DNS server we were discussing. If you "ping community.mydomain.com" while connected to the VPN, and then "ping community.mydomain.com" without the VPN, is the IP address you're attempting to ping in those two cases any different? Or maybe even IPv4 in the success case, and IPv6 in the failure case?
If you're getting the same IP address in both cases, then do you have a web site running at www.mydomain.com
or mydomain.com? If so, does pinging that
give the same IP address with VPN connected as when the VPN is not connected? And can you access that
site from inside on the LAN?
If this community.mydomain.com web server is completely separate from other web sites on mydomain.com that can be successfully reached from inside the LAN, then you could be looking at a configuration issue of the server itself (not the Apache service) such as having a IP default route that points to a public-side router which intentionally has no idea how to reach your internal LAN network addresses. But has a correct return route for any public-side request.