![]() This DNS server then could provide the internal IP of your home server. You might try to run your own DNS server and tell the clients via DHCP to use this DNS server. There is no way around because connection with the external IP address will go through the router. If you insist of using the external IP address from inside then you have to replace the router against a model which supports NAT Loopback (NAT hairpinning or NAT reflection or whatever you call it). flags: qr aa rd ra ad QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 >HEADER<<- opcode: QUERY, status: NOERROR, id: 29482 Header always set Strict-Transport-Security "max-age=15768000 includeSubDomains preload" SSLCertificateKeyFile /etc/apache2/ssl/apache.key SSLCertificateFile /etc/apache2/ssl/apache.crt Options Indexes FollowSymLinks MultiViews No changes in sites-available, no linking. ![]() ![]() In /etc/apache2/nf everything is pretty standard. var/www/owncloud/config/config.php 'trusted_domains' => # The following lines are desirable for IPv6 capable hosts etc/dnsmasq.d/ (read somewhere to create this) address=//192.168.2.200 In /etc/nf this is the only thing I added: listen-address=127.0.0.1 # DO NOT EDIT THIS FILE BY HAND - YOUR CHANGES WILL BE OVERWRITTEN etc/nf # Dynamic nf(5) file for glibc resolver(3) generated by resolvconf(8) etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) In the following you can see all the files I fiddled around with and which I think might be relevant. Is it possible to not configure the clients at all? Meaning no entering the servers DNS or changing hosts in the clients for it to work properly. What would I have to change to access my owncloud from the internal network over the external IP? Not a solution would be to change the hosts files of all the clients (on unrooted androids this isn't even possible). In Mint I disabled network manager (in fact I removed it) and I am now using interfaces. On my Windows 7 machine (which I'm trying to access the server from) I entered 192.168.2.200 (the servers internal IP) as DNS. Ports 80 and 443 are forwarded and for dynamic DNS I have an account on which I entered in the router settings. The server is connected to a Speedport 723v which doesn't support NAT Loopback. But I can access it from inside the network over its internal IP (192.168.2.200) and from outside the network over .Ī home server running Linux Mint 17.2 Cinnamon which is supposed to be for media and to run owncloud. First I want to say that I probably read everything that there is on the internet regarding the problem.Īnd the problem is that I can not access my owncloud over if I am in the same network.
0 Comments
Leave a Reply. |