Hello.
Set on NAS QNAP ts-131p QApache 2439.7218 and NextCloud 18.03
Access from the local network 192.168.14.2:45080 192.168.14.2:45083 - ok
Access from the Internet - the external static IP 178.124.179.179: 45080 and 178.124.179.179: 45083 (a router configured port forwarding) - ok.
Config.php
<? Php
$ CONFIG = array (
'Instanceid' => 'oc8flgtlszha',
'Passwordsalt' => 'xH27gL0dtbPTMQyslDXfXKk2o6nYfP',
'Secret' => '/ L1pskESYU + ORD51M7gVztjRJ6vW1RBtg2Tks32 + tBzZnufi',
'Trusted_domains' =>
array (
0 => '192.168.14.2:45080',
1 => 'localhost',
2 => '178.124.179.179',
3 => 'lan45.keenetic.pro',
)
'Datadirectory' => '/share/5000039FF4D1901E_DATA/.qpkg/NextCloud/nextcloud/data',
'Dbtype' => 'sqlite3',
'Version' => '18 .0.3.0 ',
'Overwrite.cli.url' => 'http://192.168.14.2:45080',
'Installed' => true,
);
Support router includes a third-level domain for the router - set up a kind
lan45.keenetic.pro domains and the ability to receive the 4-level LAN devices - for nextcloud configured nextcloud.lan45.keenetic.pro (To http port 45080)
"By default, remote access to the device on the domain level 4 through KeenDNS service works - you connect to the Internet using HTTPS-center, and then from the center goes online connection to the local device via the HTTP protocol. "
Connecting from the Internet at the following address nextcloud. lan45.keenetic.pro - I get a page
"Access through untrusted domain
Contact your administrator. If you are the administrator of this server, edit the parameter «trusted_domains» in the «config / config.php» file. An example can be found in the settings «config / config.sample.php» file "
What domain add to the 'trusted_domains'? I tried and nextcloud.lan45.keenetic.pro and
*. lan45.keenetic.pro - all equal "access through untrusted domain» ☹You have to fill in, the domain what you are using. No need to use a port or something.
Perhaps it is also an error to insert port like
:45080
in this config
array (
0 => ‘192.168.14.2’,
1 => ‘178.124.179.170’,
2 => ‘nextcloud.lan45.keenetic.pro’,
)
by nextcloud.lan45.keenetic.pro link goes to
http://192.168.14.2/index.php/login (it is not clear why the address of the local network, and not specified port 45080)
This router error (but all other domains 4th level work as needed) or still nextcloud incorrectly processes incoming hhtp request?
Is it possible to specify that all domains “trusted” for the experiment?
I think there is no problem with the trusted domains.
There is a redirect from
nextcloud.lan45.keenetic.pro to 192.168.14.2
perhaps in Nginx
That is a problem in the router? I will ask for routers support team…
But can log in something to help …
http://178.124.179.170:44444/index.php/s/fftYAkGtbQz6kG2
???
Yes you must pehaps redirect
nextcloud.lan45.keenetic.pro to 192.168.14.2
But not in this way.
From the internet you never can access the internal ip 192.168.14.2 .
The ip is not routed in the internet.
mediatomb.lan45.keenetic.pro at 192.168.14.2 on port 51500 (Mediatomb DLNA server) redirects, everything is fine
nas45.lan45.keenetic.pro at 192.168.14.2 on port 8080 forwards, everything is fine
nextcloud.lan45.keenetic.pro redirect 192.168.14.2 but without port 45080 …
If I delete from a trusted domain ‘nextcloud.lan45.keenetic.pro’ - the page will be opened (with an error Access through untrusted domain)
If you are in the internet and look in the browser network analysis (F12) you can see that “nextcloud.lan45.keenetic.pro” (Internet) goes to “192.168.14.2” (internal). That is not possible. You must a real port-forwarding (80 and 443).
If you use dyndns you can CNAME nextcloud.lan45.keenetic.pro to the dyndns-ip/name, on the router forward tcp/443 to 192.168.14.2:443 ant then you can create on the server a Lets Encrypt certificate.
If not too much trouble …
and repeat, sorry - If I delete from a trusted domain ‘nextcloud.lan45.keenetic.pro’ - the page will be opened (with an error Access through untrusted domain). UUPSSS… Now redirect on again to 192.168.14.2… Tired … 
I will ask the customer support router Thank U!
Read:
Everything works except nextcloud
An example that works
nas45.lan45.keenetic.pro
giga2.lan45.keenetic.pro
print.lan45.keenetic.pro
mediatomb.lan45.keenetic.pro
If you connect
https://nas45.lan45.keenetic.pro/cgi-bin
you only contact this server (klick F12 in Firefox or Chrome)
https://nextcloud.lan45.keenetic.pro
Nextcloud is redircted to an internal server. And that is the error.
(klick F12 in Firefox or Chrome)
There is no port forwarding for Nextcloud.
There is a url redirect to the internal ip and that could not work.
From the internet you can not access internal ips without port-forwarding like NAS.
Post the configuration.
http://178.124.179.170:44444/index.php/s/s3BLYDsenMcA5dK
That’s all that is available to me in the settings of the router
Ok.
nas45.lan45.keenetic.pro has got a world wide ip address
your nas has got a private ip. Where is the setting to match it?
nextcloud.lan45.keenetic.pro has got a world wide ip address
your nextcloud has got a private ip. Where is the setting to match it?
Post both.
world wide ip address - paid and issued by provider
http://178.124.179.170:44444/index.php/s/GRiZprryQT5Pbkd
By default, remote access to the device on the domain level 4 through KeenDNS service works - you connect to the router using HTTPS, and then from the router goes online connection to the local device via the HTTP protocol.
For all subnames you use the ip address 178.124.179.170 .
You can use Nextcloud with only HTTP, the name and the port 44444:
http://nextcloud.lan45.keenetic.pro:44444/index.php/login
(if you add it in the trusted domains in config/config.,php)
I think your matching on Nginx is wrong.
Check the setting for your named subdomain nextcloud.lan45.keenetic.pro and port 443.
It should correct forwared like the examples nas, …
Please use https, nextcloud… and port 443 for nextcloud.
I’ll try, thank U
It works. What have you changed?