Skip to content

Several security and compatibility issues #635

Closed

Description

@bf8392
  1. 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
  2. Nextcloud reports that the webserver isn't correctly configured to resolve
    /.well-known/caldav
    /.well-known/carddav
    (using this Image with traefik reverse proxy)

Activity

  1. J0WI commented on Feb 1, 2019

    @J0WI
    Contributor

    Duplicate of #632?

  2. bf8392 commented on Feb 1, 2019

    @bf8392
    Author

    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

  3. J0WI commented on Feb 1, 2019

    @J0WI
    Contributor

    This seems to be an issue with your traefik configuration. The latest default image passes all checks.

  4. marceljd commented on Feb 2, 2019

    @marceljd
    Contributor

    See #527 for the .well-known issue, you have to change the .htaccess file.

  5. marceljd commented on Feb 9, 2019

    @marceljd
    Contributor

    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.

  6. mherzhoff commented on Apr 24, 2019

    @mherzhoff

    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

    Have to admit you're right :-)
    But adding only overwriteprotocol and overwritehost did the thing for me!

  7. SnowMB commented on May 28, 2019

    @SnowMB
    Contributor

    @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:

    traefik.frontend.redirect.permanent: 'true'
    traefik.frontend.redirect.regex: https://(.*)/.well-known/(card|cal)dav
    traefik.frontend.redirect.replacement: https://$$1/remote.php/dav/
    
  8. bf8392 commented on May 28, 2019

    @bf8392
    Author

    Thanks that did the trick :-) the issue is resolved :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions