I have a running BBB (audio,video, everything works) but I can access it only from outside of my network. The HTTP/HTTPS ports are accessible from the outside only after the BBB installation. Why?
I've installed a fresh Ubuntu 16.04 server
Its "A record" is pointing to the ext IP of my Router(NAT), e.g.: 84.85.86.87
Internal IP is something like: 192.168.10.10
Firewall of the router allows port forwarding for 80,443, 22 and the needed UDP ports
*Before* I installed BBB I checked with netcat that the server gets the requests on all open ports from within my home network and from the outside. When calling from the outside the netcat test works with the external IP and the FQDN (but not with the internal IP, of course), when tested from within my network it works with external, internal IP and the FQDN as expected.
But after the installation of BBB with the installer script, it is not possible to reach the server from *within*my network with the FQDN or external IP (of my router) anymore. even when BBB and nginx is not running and ufw disabled a test with netcat does still work from outside of my network (so firewall and port forwarding still works) but not from within. Even nmap does not show the ports 80 and 443 from within, only from outside ma network.
I started on the BBB server:
> netcat -l 443
Check with Mac from outside my network:
netcat 84.85.86.87 443 -> ok
netcat 192.168.10.10 443 -> fails as expected
nmap -PN bbb.dirksdomain.de
PORT STATE SERVICE
80/tcp filtered http
443/tcp filtered https
5060/tcp open sip
...
Check with Mac from inside my network:
netcat 84.85.86.87 443 -> fails
netcat 192.168.10.10 443 -> ok
Therefore if BBB runs, users from outside can work, including screen sharing, video and audio, but I can't even reach the server (time out in chrome) from within the network where the server runs. Is this intended? And how can I enable it?
I can still reach the server with the internal IP address, so an entry in /etc/hosts on every client Mac at home is a work around, but a rather dirty one. Which setting forbids the access from within my network over the FQDN? (It's not the router. Another machine I've set up for tests with apache works with the same FQDN over the same router).
regards,
Dirk