I’ve set up Taiga via Docker Compose on my NAS following this guide. All containers are running. I’ve waited for the initial migration scripts to finish, created a superuser and logging in works. I have mounted the volumes to local folders (db, events, gateway, media, rabbitmq and static) on my NAS, and after the initialization phase, most of them are not empty any longer (i.e. they have been populated with data by the scripts).
However, I cannot change my profile picture, create projects etc.! At first I thought that no data would be saved, but that’s not true: When I change my profule picture, for example, it does get saved in the mounted media folder (I can find it there) - but the browser console shows that Taiga cannot find the file, although it is physically there:
There is a file in said location with that exact file name, and it is the thumbnail of the profile picture I had selected earlier.
The same goes for projects: If I try to create one, the “saving process” never ends (the spinning write indicator keeps spinning forever, and if I reload the page, no project is shown.)
It seems that Taiga cannot access the data, although it has written it to disk itself. I’ve tested this with Firefox and Edge, both locally (h t t p://192.168.xxx.xxx:9005) and remotely (h t t p s://pm.xxxxxxxxx.com). [ ← As a new user, I’m not allowed to have more than two links in here, so I had to write http and https with spaces here] The docker containers are exposed via subdomain (pm.xxxxxxx.com) behind a reverse proxy (NGINX) with websockets enabled. Since it also doesn’t work locally, I think websockets / reverse proxy is not the issue here. (Besides, just to rule this out, I have set the permissions for the mounted folders to read and write for everyone.)
What might be wrong here? How can I approach a solution?
Thanks in advance to anybody taking the time to reply!