First I tried to run Discourse with semi-default settings and it worked quite fine, I was able to upload files as well as do other stuff. Then I realized the path in app.yml was /var/discourse and I updated it to /var/www/discourse, stopped and destroyed the container, removed the previous folder completely. And I have it up and running again… but I noticed now I cannot upload files any more. What kind of permissions does uploads folder need? I can do some changes manually, but I’d like to know what exactly and whether it’s fine in general (shouldn’t the launcher take care of setting right permissions, especially when launched from scratch?) IN the logs I have nginx errors like 2024/07/12 19:11:23 [crit] 76#76: *160552 stat() “/var/www/discourse/public/uploads/default/original/1X/971c712ff3f1758abc63ac777ad708042cc41ddf.png” failed (13: Permission denied), client: 172.17.0.1, server: _, request: “GET /phorum/uploads/default/original/1X/971c712ff3f1758abc63ac777ad708042cc41ddf.png HTTP/1.0”, host: “myhost.com”, referrer: “https://myhost.com/phorum/admin/site_settings/category/branding” Permissions on uploads are like: drwxr--r--+ 3 discourse www-data 21 Jul 12 11:47 uploads

Okay, nothing worked, so I ended up changing permissions for uploads folder to 755 and it’s fine now. After rebuild it seems the uploads themselves were okay (from the engine side), however nginx was not able to read those.

[image] lega4: Then I realized the path in app.yml was /var/discourse That’s whats recommended. The /var/www/discourse path is the path to discourse inside the container. /var/discourse is the normal path for Discourse_docker outside the container. Since you just started, I would likely recommend that you just start over and don’t rename anything this time. My guess is that you didn’t update the path in your app.yml and so it’s trying to access something that doesn’t exist.

[image] Jay Pfaffman: The /var/www/discourse path is the path to discourse inside the container. /var/discourse is the normal path for Discourse_docker outside the container. I have many other projects on this server and they’re all are nicely located in my /var/www folder, so I prefer to keep it like this :slight_smile: And I don’t care how it is inside the container. [image] Jay Pfaffman: My guess is that you didn’t update the path in your app.yml and so it’s trying to access something that doesn’t exist. But I did update it? In mounts, or where else should it go?

[image] lega4: they’re all are nicely located in my /var/www folder Sorry, can’t help. But I’m totally sure you don’t have Nginx there :wink: Situation is same with docker container.

[image] Jakke Flemming: Sorry, can’t help. But I’m totally sure you don’t have Nginx there :wink: Situation is same with docker container. Sorry, I’m not getting, which nginx? The logs are from Discourse nginx, my SSL-terminating nginx is above it.

Exacly my point. Because your reverse proxy nginx isn’t in that path why should docker container be. But a container lives its own life and path to container should not affect what its Nginx does. Did you change something else too?

I checked what I have: lrwxrwxrwx 1 root root 15 Jul 12 10:10 uploads -> /shared/uploads And as an example one image on /var/www/discourse/public/uploads/default/original/1X looks like that: -rw-r--r-- 1 discourse www-data 7100 May 19 2022 08335563eac3a393e60a902d4d38cffdfa6d967d That much I know. Because otherwise Docker is one very huge mystery for me :rofl:

[image] Jakke Flemming: lrwxrwxrwx 1 root root 15 Jul 12 10:10 uploads -> /shared/uploads So basically world-writable? Isn’t it considered bad for security?

[image] lega4: have many other projects on this server and they’re all are nicely located in my /var/www folder You really don’t want to run the risk of serving your secrets in your app.yml to the world.

Inside docker? I don’t think so. And… I don’t care because all of that is planned and made by CDCK and I trust they know what they do :smirking_face:

[image] Jay Pfaffman: You really don’t want to run the risk of serving your secrets in your app.yml to the world. Sure, but I’m not serving anything :slight_smile: [image] Jakke Flemming: Inside docker? I don’t think so. Permissions are the same regardless whether inside/outside. And uploads folder is mounted.

Permissions for uploads folder?

Product Support Self-hosting

pfaffman (Jay Pfaffman) July 13, 2024, 11:36am 15

If you want you can upload a file and see what it’s permissions are and copy that.

Maybe upload a few and then do

 find uploads -ls |less

Topic		Replies	Views
Uploaded figures dont show Self-hosting	5	1338	July 22, 2015
Moving Discourse to subdirectory caused all uploads to break Product Support	9	3549	August 27, 2015
Error trying to edit a post with an image in (NginX Proxy Manager?) Self-hosting	43	4636	May 7, 2022
Serve Discourse from a subfolder (path prefix) instead of a subdomain Self-Hosting docker , subfolder , how-to , advanced-setup	30	44936	April 14, 2026
Blank Page After installing Discourse on Subfolder Self-hosting	8	1701	August 31, 2018

Permissions for uploads folder?

Related topics