Headless is experiencing issues mounting a new filesystem for uploads in their Discourse instance, resulting in missing profile pictures and dashboard errors. After mistakenly mounting onto /var/discourse/shared, they unmounted it and tried reverting to the original setup — but the problem persisted. neounix guided them through diagnostics, including checking directory contents and permissions. Headless moved uploads to a new volume at /mnt/volume-fsn1-1/uploads and attempted to use a symbolic link from /var/discourse/shared/standalone/uploads to the new location as suggested. While the symlink appeared to work at the filesystem level, it ultimately failed to resolve the Discourse upload issues. neounix concluded the symlink approach was a “wild goose chase” and advised reverting to direct mounting. As of post 22, Headless reports the dashboard error is resolved but avatar loading issues remain, and they plan to run a rake task to fix avatars. The discussion continued externally due to posting limits for new users.
I am having an issue mounting a new space for uploads. I am getting this when I look at the dashboard and a lot of the profile pictures arent showing up when you access someones profile.
Ive tried everything I could think of, I believe what happened is I did something stupid and tried MOUNTING ONTO the the /var/discourse/shared and it may of caused problems… I keep getting
Yes correct, I did that and it works fine. However, I even tried not using the new volume and tried going back to the way things originally were. But I still get that error, while also having issues with loading profile pictures. I believe I may have really screwed up something and not entirely sure what I ended up doing.
As you can see below is what happens to profile pictures.
So that uploads folder in /var/discourse/shared/standalone is always empty because it gets created upon build the app. Nevertheless ill do exactly that.