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
The __Host Prefix of the cookies isn't set properly -> leads to bad rating in security scan -> cant't influence this as the setting comes from the container
Nextcloud reports that the webserver isn't correctly configured to resolve
/.well-known/caldav
/.well-known/carddav
(using this Image with traefik reverse proxy)
See #644 for Apache, the .well-known and HSTS errors will be gone. When you run Nextcloud behind a proxy you also need a trusted proxy entry in the config.php, I will create a PR for this next week. Both can be added with environment variables.
Activity
J0WI commentedon Feb 1, 2019
Duplicate of #632?
bf8392 commentedon Feb 1, 2019
I was able to resolve the __Host prefix issue with this guide: https://docs.nextcloud.com/server/13/admin_manual/configuration_server/reverse_proxy_configuration.html
but the resolve issue still persits
J0WI commentedon Feb 1, 2019
This seems to be an issue with your traefik configuration. The latest default image passes all checks.
marceljd commentedon Feb 2, 2019
See #527 for the .well-known issue, you have to change the .htaccess file.
marceljd commentedon Feb 9, 2019
See #644 for Apache, the .well-known and HSTS errors will be gone. When you run Nextcloud behind a proxy you also need a trusted proxy entry in the config.php, I will create a PR for this next week. Both can be added with environment variables.
mherzhoff commentedon Apr 24, 2019
Have to admit you're right :-)
But adding only
overwriteprotocolandoverwritehostdid the thing for me!SnowMB commentedon May 28, 2019
@bd8392 The Nextcloud 16 documentation includes a solution for the resolve issue without touching the .htaccess file: click
Add the following labels to your nextcloud container:
bf8392 commentedon May 28, 2019
Thanks that did the trick :-) the issue is resolved :-)