Tracking script /swetrix.js is not reliably available after frontend container recreate in self-hosted CE

[adrivecc]

Summary

In a self-hosted Community Edition deployment, the tracking script path /swetrix.js was not reliably available after recreating the frontend container.

This caused website-side tracking integration to fail until the file was restored.

Environment

Observed in self-hosted CE using official images in a Docker-based deployment.

Observed on:

• swetrix/swetrix-fe:v5.0.3
• swetrix/swetrix-api:v5.0.3

Actual behavior

After frontend container recreate / redeploy, requesting /swetrix.js was not reliably stable in the self-hosted setup.

In practice this broke website analytics initialization, because the tracking script URL was no longer consistently available as a valid JS asset.

Expected behavior

A self-hosted installation that expects users to load:

<script src="https://<self-hosted-domain>/swetrix.js" defer></script>

should ensure that /swetrix.js remains available across container recreates.

Reproduction outline

1. Run self-hosted CE with the frontend container serving the tracking script.
2. Recreate the frontend container.
3. Request /swetrix.js.
4. Observe that the asset may no longer be reliably available unless it is explicitly restored into the served public path.

Local workaround

A local workaround that fixed the issue was adding a startup copy step in the frontend container:

cp -f /app/node_modules/swetrix/dist/swetrix.js /app/public/swetrix.js

This made /swetrix.js available again on every container start.

Additional context

There is already some historical confusion around the self-hosted script path and where the file is expected to be served from. It would help if the official self-hosted setup either:

• guaranteed /swetrix.js as part of the frontend container lifecycle, or
• documented the intended serving strategy more explicitly.

This report refers only to self-hosted CE behavior and does not include any private deployment details.

[Blaumaus]

Hi, thank you for your report. swetrix.js is not supposed to be self-hosted and we intentionally do not include it in the releases so that we could push any patches to it if necessary.

Our recommended approach to this is either use NPM package where you can control the version of the script installed, or proxy it using one of our guides -> https://swetrix.com/docs/adblockers/guides/nginx, or just use it directly via swetrix.org/swetrix.js