# Uploads broken with subfolder installation **URL:** \ **Category:** Bug\ **Tags:** subfolder\ **Created:** [September 1, 2022, 8:01pm UTC](https://meta.discourse.org/t/uploads-broken-with-subfolder-installation/237867 "2022-09-01T20:01:49Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![insou](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/insou/32/272730_2.png) [@insou](https://meta.discourse.org/u/insou)\ **Post date:** [September 1, 2022, 8:01pm UTC](https://meta.discourse.org/t/uploads-broken-with-subfolder-installation/237867/1 "2022-09-01T20:01:49Z")
Similar to [Uploaded avatars and Gravatar not working with subfolder installation](https://meta.discourse.org/t/uploaded-avatars-and-gravatar-not-working-with-subfolder-installation/38114)… All uploads are broken on my subfolder install. The uploads make it into the actual uploads directory, but when rendering the posts, all images get `src=""`. Making a post… `https://i.imgur.com/ofOUY4e.png` After posting… `https://i.imgur.com/EBmnD6e.png` Somewhat amazingly, if I then move to a different browser (chrome now), pull up the topic (where the image is still broken), but then click _edit_, the image renders in the edit preview once again! `https://i.imgur.com/3rQirhc.png` This confirms it’s successfully uploading to the server, which I’ve verified: ```plaintext root@cs6991:/var/discourse# ./launcher enter app x86_64 arch detected. root@cs6991-app:/var/www/discourse# ls 'public/~cs6991/forum' backups uploads root@cs6991-app:/var/www/discourse# ls 'public/~cs6991/forum/uploads' default root@cs6991-app:/var/www/discourse# ls 'public/~cs6991/forum/uploads/default/original/1X/' 08335563eac3a393e60a902d4d38cffdfa6d967d.png 3eee67e6460792667bab4f2248ad4643be4feae3.png 29e403dabcfee32379629fb6d844354193e278ba.png 42ecfcb27b534acc9f3436fa7d291c2fca106e57.png ``` But it just doesn’t seem to be rendering on the actual page. Same issue occurs with other uploads, such as avatars. Some info: Subfolder: `/~cs6991/forum` app.yml ```plaintext ## this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild app ## ## BE *VERY* CAREFUL WHEN EDITING! ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT! ## visit http://www.yamllint.com/ to validate this file as needed templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) #- "templates/web.ssl.template.yml" #- "templates/web.letsencrypt.ssl.template.yml" ## which TCP/IP ports should this container expose? ## If you want Discourse to share a port with another webserver like Apache or nginx, ## see https://meta.discourse.org/t/17247 for details expose: - "80:80" # http - "443:443" # https params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## will be set automatically by bootstrap based on detected RAM, or you can override db_shared_buffers: "128MB" ## can improve sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LC_ALL: en_US.UTF-8 LANG: en_US.UTF-8 LANGUAGE: en_US.UTF-8 # DISCOURSE_DEFAULT_LOCALE: en ## How many concurrent web requests are supported? Depends on memory and CPU cores. ## will be set automatically by bootstrap based on detected CPUs, or you can override UNICORN_WORKERS: 2 ## TODO: The domain name this Discourse instance will respond to ## Required. Discourse will not work with a bare IP number. DISCOURSE_HOSTNAME: 'cgi.cse.unsw.edu.au' ## Uncomment if you want the container to be started with the same ## hostname (-h option) as specified above (default "$hostname-$config") #DOCKER_USE_HOSTNAME: true ## TODO: List of comma delimited emails that will be made admin and developer ## on initial signup example 'user1@example.com,user2@example.com' DISCOURSE_DEVELOPER_EMAILS: '<>' ## TODO: The SMTP mail server used to validate new accounts and send notifications # SMTP ADDRESS, username, and password are required # WARNING the char '#' in SMTP password can cause problems! DISCOURSE_SMTP_ADDRESS: email-smtp.ap-southeast-2.amazonaws.com DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: <> DISCOURSE_SMTP_PASSWORD: <> #DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true) #DISCOURSE_SMTP_DOMAIN: discourse.example.com # (required by some providers) DISCOURSE_NOTIFICATION_EMAIL: discourse@cs6991.email # (address to send notifications from) ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate #LETSENCRYPT_ACCOUNT_EMAIL: me@example.com ## The http or https CDN address for this Discourse instance (configured to pull) ## see https://meta.discourse.org/t/14857 for details #DISCOURSE_CDN_URL: https://discourse-cdn.example.com ## The maxmind geolocation IP address key for IP address lookup ## see https://meta.discourse.org/t/-/137387/23 for details #DISCOURSE_MAXMIND_LICENSE_KEY: 1234567890123456 DISCOURSE_RELATIVE_URL_ROOT: '/~cs6991/forum' ## The Docker container is stateless; all data is stored in /shared volumes: - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log ## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git ## Any custom commands to run after building run: - exec: echo "Beginning of custom commands" ## If you want to set the 'From' email address for your first registration, uncomment and change: ## After getting the first signup email, re-comment the line. It only needs to run once. #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'" - exec: cd: $home cmd: - mkdir -p public/~cs6991/forum - cd public/~cs6991/forum && ln -s ../../uploads && ln -s ../../backups - replace: global: true filename: /etc/nginx/conf.d/discourse.conf from: proxy_pass http://discourse; to: | rewrite ^/(.*)$ /~cs6991/forum/$1 break; proxy_pass http://discourse; - replace: filename: /etc/nginx/conf.d/discourse.conf from: etag off; to: | etag off; location /~cs6991/forum { rewrite ^/~cs6991/forum/?(.*)$ /$1; } - replace: filename: /etc/nginx/conf.d/discourse.conf from: $proxy_add_x_forwarded_for to: $http_your_original_ip_header global: true - exec: echo "End of custom commands" ``` Everything else, as far as I can tell, appears to be working correctly – just upload rendering that’s acting rather peculiar. I’ve verified this behaviour on a completely fresh build – that is, `rm -rf /var/discourse`, completely nuking `docker`, and following cloud install + subfolder instructions. If there’s further investigation I can pursue, I’m happy to take those steps. (sorry for imgur links – I’m not allowed 2+ image embeds here yet!) Cheers! --- _[View the full topic](https://meta.discourse.org/t/uploads-broken-with-subfolder-installation/237867)._