Hello, I have this problem with the Nexcloud App:
I use Nextloud by Traefik.
The App is synchronizing the photos with my server at the address:
http: // my_ip_local: my_port
and it works fine.
But my server also works with Traefik at the address:
https: // my_domain_traefik
When I want to synchronize the App with Traefik, by means “add account”, I can advance until it asks me for my username and password, then ¡, when I give them the App stays “thinking”, it does not get to synchronize, but it does not give me an error.
Is it not possible to sync with the two addresses? Maybe I have to delete the first account, the one that is linked to http?
Thanks a lot!
Same problem here using nginx proxy. I cannot use the Android or Linux client with DNS address
Adding more details: same problem with Nextcloud docker 21-apache and 22-apache. The app IS added under settings/security/devices. I can connect the DAVx5 app. In the browser console I can see an error regarding “form-action”.
Did you check the documentation?
With the overwrite conditions set properly, it should work on the local network as well.
If you follow up the logs of your server and the proxy, it can help to find where the communitcation fails.
Hi Omega1902, You may be right, but I’m using docker, and all Traefik parameters are specified in the docker-compose.yml. In fact, traefik works without problem on the PC, by Firefox, it just doesn’t work for me with the App.
I think it may be a solution to modify in config.php, but I see a risk in duplicating the information because in the future I may forget to change on both sides, of course it is not a practice to configure the same thing twice.
Is it possible that it could work for me just setting the docker-compose.yml.?
Same for me, the only difference is that I use nginx proxy with docker. How ever, reading through the documentation linked by tflidd I added the local IP address to both the config file and the proxy configuration. Now I can use the IP address to link the app in my local network. Via DNS it does still not work. How ever, both ways actually use my proxy! Locally not encrypted on port 80 and via DNS encrypted on port 443, but I can say for sure that both ways are with the proxy (the Nextcloud container port is only available to the proxy).
If I find a solution for my setup I will post it and you might be able to adapt for traefik, but currently I think about leaving it as it is…
I’ve looked into the browser console and found the following error code everytime I press the grant access button:
Content Security Policy: The page’s settings blocked the loading of a resource at http://my.dyndns.com/login/v2/grant (“form-action”).
I’ve noticed that it says http, while having an https connection. I’ve manually changed it on the PC, which solved the problem! How ever, this workaround is probably only suitable on PC, since I cannot edit the HTML on Android as on PC. I’ll test the overwriteprotocol parameter
I’ve set the
overwritehost to my dyndns and ‘overwriteprotocol’ to https in config/config.php. Now the app can connect to Nextcloud via URL, but I have to remove the connection with IP address (which I do not see as a downside)
Opening the browser in the IP address results in being forwarded to the URL, which is also appreciated.
So the proxy configured itself was ok, but I failed to configure Nextcloud properly behind the proxy.
Thanks for the help!
I think the problem with not being able to use the IP is that if there is no internet (for example, a service drop), then it will not work even with your local network. You will also not be able to close the external ports on the router (if necessary for security).
That’s why you want a proper DNS setup in your local network. Because even if you can connect to your Nextcloud local IP address and everything works, you would have to change that every time the client device leaves the local network. While this doesn’t matter much on a stationary computer, it’s a pain on a mobile device.
There are several ways to use the same DNS name on the internal network as on the external one.
local host overrides directly in the hosts file of the respective device. Of course this is only useful for stationary devices.
NAT Loopback. (Must be supported by the router and explicitly enabled in certain models)
host overrides in your router (must be supported by your router obviously, most consumer / ISP routers do not support it)
a separate DNS server on e.g. a Raspberry Pi. The easiest way to set this up is with Pi-hole. As a nice side effect you also get a network wide ad blocker with it.