Images not loading

[ray73864]

Astro Info

Astro                    v5.14.5
Vite                     v6.4.0
Node                     v24.10.0
System                   Linux (x64)
Package Manager          npm
Output                   server
Adapter                  @astrojs/node (v9.5.0)
Integrations             none

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

Since updating to the latest Astro version, images now come back as 'Internal Server Error'.

I'm using Astro in SSR mode with NodeJS.

Not using SVGs, images are under src/assets.

What's the expected result?

Images should display.

Link to Minimal Reproducible Example

.

Participation

• I am willing to submit a pull request for this issue.

[lcapka]

Hi, we are experiencing the same error; we are using .svg files under src/assets. Otherwise the configuration is the same - SRR with NodeJS.

[matthewp]

@lcapka what version of Astro was it working?

@ray73864 please provide a reproduction, thank you.

[github-actions]

Hello @ray73864. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with needs repro will be closed if they have no activity within 3 days.

[lcapka]

Hi @matthewp, I have one update - we are using two-stage build (Dockerfile) and in our case it NOT related to the updated Astro but we found that problem was in difference between built and final folder. To be specific:

It worked (and work also with latest version) when npm build docker-image stage saves data into /app/dist and that's copied to the release docker-image stage which uses the same path /app/dist/....

Simplified working:

FROM node:24-alpine3.22 AS builder
WORKDIR /app
COPY . .
RUN npm ci
RUN npm run build

FROM node:24-alpine3.22 AS final
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
CMD [ "node", "./dist/server/entry.mjs" ]

The image serving stopped working when we changed folder in the build stage to be /build/dist and then the dist folder was copied to the /app/dist in the final docker-image. In this case 'Internal Server Error' has appeared. Original thought was that the problem relates to the Astro update but no in our case. It means that the dist folder location must not be changed.

Simplified erroneous:

FROM --platform=$BUILDPLATFORM node:24-alpine3.22 AS builder
WORKDIR /build
COPY . .
RUN npm ci
RUN npm run build

FROM --platform=$TARGETPLATFORM node:24-alpine3.22 AS final
WORKDIR /app
COPY --from=builder /build/dist ./dist
COPY --from=builder /build/node_modules ./node_modules
CMD [ "node", "./dist/server/entry.mjs" ]

[ray73864]

@lcapka what version of Astro was it working?

@ray73864 please provide a reproduction, thank you.

I'm not entirely sure a reproduction is going to be possible with this one. Looking at the support chat dohickey on Discord, it suggests something changed around 5.13.2 which broke things and it's possibly related to how users run it in a nodejs standalone SSR environment when copying the 'dist/*' content from development/staging to production.

In our case, the app might live in say '/home/www/app', then when I run npm run build, I copy the contents of 'dist/*' over to the production server using SCP where the app lives in '/opt/www' where the subdirectories are '/opt/www/client' and '/opt/www/server'.

This was all working fine prior to the 5.13.2 update, so I have no idea how I would recreate this kind of setup in stackblitz, etc...

[ematipico]

In our case, the app might live in say '/home/www/app', then when I run npm run build, I copy the contents of 'dist/*' over to the production server using SCP where the app lives in '/opt/www' where the subdirectories are '/opt/www/client' and '/opt/www/server'.

You shouldn't do that, especially if you use SSR. After the build, we create a manifest, which is used to render the SSR pages. Some information inside the manifest are file paths. If you change the location of the by-product, those paths won't match anymore, and the app might not work as expected

[ray73864]

In our case, the app might live in say '/home/www/app', then when I run npm run build, I copy the contents of 'dist/*' over to the production server using SCP where the app lives in '/opt/www' where the subdirectories are '/opt/www/client' and '/opt/www/server'.

You shouldn't do that, especially if you use SSR. After the build, we create a manifest, which is used to render the SSR pages. Some information inside the manifest are file paths. If you change the location of the by-product, those paths won't match anymore, and the app might not work as expected

I've yet to have any issues and the website has been up and running for around 6 months.

IMHO a lot of that stuff should be relative not absolute paths.

Either way, this one patch to images has completely broken locally hosted images.