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ā¦