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
Copy the .env.example to .env and add some values for the variables.
Change the image tag of the app container to the latest
Run docker-compose up -d, followed by docker exec $(docker ps -qf "name=app") sh -c 'chown www-data:root custom_apps'.
Navigate to localhost:8000 and try to activate any apps
At this point, I believe this is an issue with the configuration in this image, but it may also just be my proxy configuration that is messing with things. Apologies, if it's user error, but this config has been working for a long time.
I think it unlikely that it's a core server issue, because then it would likely have been caught in RC, this is why I open the issue here.
Background: I use this as my dev and testing setup and I can see some people on Reddit having the same issue, though they don't specify if they're using this container.
The text was updated successfully, but these errors were encountered:
see nextcloud/server#44685 (comment) . Works on my end, but keep in mind it's working on my setup, and mine is a bit weird one (two host acting as proxy for a bunch of other stuff).
Image tag
nextcloud:28.0.4-fpm-alpine
Problem
When trying to activate any app on Nextcloud's apps page, the following error appears:
A Content Security Policy error is logged in the console of the browser.
Reproduction steps / Setup
tests
folder.https://github.com/te-online/timemanager/tree/main/tests
.env.example
to.env
and add some values for the variables.app
container to the latestdocker-compose up -d
, followed bydocker exec $(docker ps -qf "name=app") sh -c 'chown www-data:root custom_apps'
.At this point, I believe this is an issue with the configuration in this image, but it may also just be my proxy configuration that is messing with things. Apologies, if it's user error, but this config has been working for a long time.
I think it unlikely that it's a core server issue, because then it would likely have been caught in RC, this is why I open the issue here.
Background: I use this as my dev and testing setup and I can see some people on Reddit having the same issue, though they don't specify if they're using this container.
The text was updated successfully, but these errors were encountered: