---
title: "DF0063: Remote Asset Cache Write Failed"
description: "Failed to persist a remote asset into the cache at \"{filepath}\": {reason}"
canonical_url: "https://devfra.me/errors/df0063"
---
# DF0063: Remote Asset Cache Write Failed

> Failed to persist a remote asset into the cache at "\{filepath}": \{reason}

## Message

> Failed to persist a remote asset into the cache at "`{filepath}`": `{reason}`

## Cause

A remote asset streamed through the CDN back-proxy to the browser, but writing the teed copy into the local cache directory (`<project storage>/.remote-assets/<package>@<version>/…`) failed, usually from a permissions problem, a full disk, or a removed `node_modules`. The response was still served; only caching failed, so the file streams through the provider again next request.

## Fix

Check that the project storage directory (conventionally `node_modules/.<app>/devframe/`) is writable and has free space.

## Source

- [`packages/devframe/src/utils/remote-assets.ts`](https://github.com/devframes/devframe/blob/main/packages/devframe/src/utils/remote-assets.ts): `createRemoteAssetsStore()`'s background cache write reports this when persisting a fetched file fails.


## Sitemap

See the full [sitemap](https://devfra.me/sitemap.md) for all pages.