Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cryptpad cannot be upgraded to 5.1.0 #30

Open
EnigmaCurry opened this issue Feb 13, 2023 · 0 comments · May be fixed by #31
Open

Cryptpad cannot be upgraded to 5.1.0 #30

EnigmaCurry opened this issue Feb 13, 2023 · 0 comments · May be fixed by #31
Labels
bug Something isn't working

Comments

@EnigmaCurry
Copy link
Owner

EnigmaCurry commented Feb 13, 2023

The cryptpad-nginx image is not designed for use with a proxy, it expects to be on public port 443, and this is a problem when I attempted to upgrade to 5.1.0. We should stop using the cryptpad-nginx image and use the cryptpad image instead.

https://github.com/xwiki-labs/cryptpad-docker#standalone-cryptpad

To do this securely, Traefik must set the same CSP headers in the same way that nginx is.

@EnigmaCurry EnigmaCurry changed the title Cryptpad should set Traefik CSP headers itself Cryptpad cannot be upgraded to 5.1.0 Feb 13, 2023
@EnigmaCurry EnigmaCurry linked a pull request Feb 13, 2023 that will close this issue
@EnigmaCurry EnigmaCurry added the bug Something isn't working label Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant