You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the following option to the nextcloud sample configs: proxy_hide_header Upgrade;
Reason for change
Safari browsers (both mobile and desktop) seem to encounter an issue accessing Nextcloud proxied instances. I have not seen this behavior exhibited for other proxied containers (mealie, emby, etc). The Nextcloud destination page/site fails to load and the client displays the following error: network connection is lost
I have only seen this with Safari browsers so far - Chrome and Firefox do not seem to need this option to function as expected, nor does it seem to affect Chrome or Firefox after being implemented.
Adding the config change to the nextcloud.subdomain.config resolved the issue.
Proposed code change
Add the following to the nextcloud.sub*.config.sample files: proxy_hide_header Upgrade;
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is this a new feature request?
Wanted change
Add the following option to the nextcloud sample configs:
proxy_hide_header Upgrade;
Reason for change
Safari browsers (both mobile and desktop) seem to encounter an issue accessing Nextcloud proxied instances. I have not seen this behavior exhibited for other proxied containers (mealie, emby, etc). The Nextcloud destination page/site fails to load and the client displays the following error:
network connection is lost
I have only seen this with Safari browsers so far - Chrome and Firefox do not seem to need this option to function as expected, nor does it seem to affect Chrome or Firefox after being implemented.
Adding the config change to the nextcloud.subdomain.config resolved the issue.
Proposed code change
Add the following to the nextcloud.sub*.config.sample files:
proxy_hide_header Upgrade;
The text was updated successfully, but these errors were encountered: