I recently moved my NextCloudPi instance behind a Nginx Proxy Manager, so that I could run other services on port 80 and 443. After I did this my friends who use iOS and macOS where unable to access my NC instance.
The issue is clearly with the Proxy Manager and so with a quick Brave Search i found the solution.
Here is what you have to do to solve the issue
Login to your Nginx Proxy Manager.
Open the [3 dots] settings menu of the NextCloud(Pi) host and select āEditā
In the tab menu at the top of the window that has just opened select āAdvancedā and insert the following in the āCustom Nginx Configurationā box:
I have similar setup, NextCloud (Snap installation on 80/443) running behind Nginx Proxy manager.
I beg to differ.
My setup is accessible from iOS / MacOS via Safari without any extra config argument in the advance settings.
My setup has itās own issue (specifically speaking upload speed) but thatās a genera one and present on every platform. Regarding this, I just checked again, its working fine with latest Safari iOS / MacOS and iPadOS
I can also confirm that the custom nginx configuration is needed for iOS access with HTTP2 enabled. I found this out some time back. My other services donāt need it.
Log: GET /login?redirect_url=/apps/dashboard/ HTTP/1.1" 200 5719 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 16_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/107.0.5304.101 Mobile/15E148 Safari/604.1"
I do have access through the IOS app and Chrome on macOS Ventura, I wonder if its related to 2FA.
Two-Factor TOTP Provider by Christoph Wurst AGPL-licensed v7
as I donāt have any iOS 16 devices in house I can not test this. But thanks for the post, I will ask friends to test my setup to see if I have the same issue.
I donāt know if this is still an interesting point for someone, but I want to share it anyway
I had a similar issue with iOS 16 Safari and the login page at my Nextcloud (26) instance behind a NGinx reverse proxy. No login was possible. After I had inserted the credentials I was redirected to the login page. Sometimes the login worked for a few minutes and then I have to log in again. Nothing from the written extra configs could solve the issue.
After a long time of trial and error I found the config that I added to the reverse proxy setting and could solve my problems:
My conclusion is that Safari on iOS have maybe some problems to deal with cookies for the session lifetime behind a reverse proxy, but this is just a guessā¦
I donāt know your setup of Nextcloud (docker or bare metal installation or something else) but your npm setting looks little bit confusing to me.
Why do you forward with https scheme to port 443 and use a custom location with http scheme and port 80? Have you tried to delete your custom location and forward directly with http scheme to port 80?
Here are my complete advanced settings you can also try:
Yes tried but site not reachable
but what I did is delete custom location HTTP to port 80
still working!
I also put in your advanced settings
I now see the site - no login, but a link to the URL to Nextcloud.URL and slogan is shown.
When I click the link
same site loads again.
I got to the Same issue,than everybody else Here. So after checking www and searching myself.for a solution with npm and nextcloud, i found a pretty easy solution.
First i thought, If i hide the Upgrade via advance Config in npm it should Work. But Here comes the Twist, the header was redirected to my nextcloud Webserver (apache2) which tried to answer.
So after a few Tests, i also Neef to ad unset header for Upgrade.
After an restart of my nextcloud Webserver ā tada it works! A friend of my ist now able to Access the Web Page and also nextcloud App ist now working again.
When i go to Nextcloud.URL on my iPhone (Local Wi-Fi & also External)
I see the color of my login page.
BUT - no login ,
A link to the Nextcloud.URL is shown and the slogan as I put into the Nextcloud
When I click the link
same site loads again.
You need to add a Line in the Config of the Webserver you direct to, in your Case 192.168.178.105 - System.
I donāt know what Webserver ist working there Apache / nginx (???), but there you need to unset the Upgrade, See comments above