Op zondag 29 december 2019 20:56:29 CET schreef Carlos E. R.:
On Sunday, 2019-12-29 at 14:50 -0500, David T-G wrote:
Carlos, et al --
...and then Carlos E. R. said...
% % On 28/12/2019 21.03, Knurpht-openSUSE wrote: % ... % > Carlos, all the (sub)domains from my config run on 80/443. Their % > webroot is different though. Do you already have 80/443 forwarded ... % % What I have tried is the port based system. What is the difference in ... % % When I browse to this server using my android phone inside the house, % I can not use the server name, as the phone does not use the LAN DNS, % but the outside DNS server via the router. So the apache will not see % the name in the http request and will fail. [snip]
I thought that you were having name challenges, but now it sounds like you're having port challenges. I'm a big fan of names, personally. I was going to suggest that you have
carlos.dyn.dns # existing public name carlos.no-ip.com # new name for friends
No way.
I repeat:
I already have "carlos.dyn.dns".
The other name is "carlos.valinor", which is a fake domain only known inside my LAN. Problem is, my phones and tablets do not know that name, only the computers: they connect by IP number. Thus, it can not work "by names", they don't know the LAN name. They don't connect to the DNS that knows the LAN names.
and use name-based vhost config to separate your content. That should work whether you're at home or away since it's a real name.
I do not want a real name inside my LAN.
Why not? Look at this: knurpht@Knurpht-HP:~> ping pihole.knurpht.nl -c1 #from my laptop inside LAN PING pihole.knurpht.nl (192.168.2.7) 56(84) bytes of data. 64 bytes from pihole (192.168.2.7): icmp_seq=1 ttl=64 time=1.31 ms --- pihole.knurpht.nl ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.309/1.309/1.309/0.000 ms knurpht@Knurpht-HP:~> knurpht.nl.ssh Last login: Sat Dec 28 22:03:51 2019 from 82.73.235.190 Have a lot of fun... knurpht@salt:~> ping pihole.knurpht.nl -c1 #from my VPS in the cloud PING pihole.knurpht.nl (149.210.217.201) 56(84) bytes of data. 64 bytes from salt.knurpht.nl (149.210.217.201): icmp_seq=1 ttl=64 time=0.064 ms --- pihole.knurpht.nl ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.064/0.064/0.064/0.000 ms The apache server on my cloud proxies the vhost to my home ip:port, where on my router the port is forwarded to the RPi's IP. Adding 192.168.2.7 to the /etc/hosts on the RPi is enough to make this work on the LAN. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org