Skip to main content
Browse documentation

App Storage compatibility and troubleshooting

An app is missing from the attachment list​

Check all of the following:

  • It is your app and is Stopped.
  • It is on a supported Dallas host.
  • Its exact app version, service and destination path have been qualified.
  • The volume is available, unattached and uses the supported block-storage mode.
  • The pool is paid and its transfer allowance has not been reached.
  • Another pending attachment is not blocking changes to that app.

The compatibility information in App Storage is the current source for approved recipes. Qualification is specific to the version and path; a catalog listing alone does not mean every path supports attachment. Send support the app name and the data path you want to expand if it is not offered.

Attachment is provisioning or needs attention​

Wait for the status to finish before starting the app. File transfer, mount validation and file-access setup must complete together. If the panel reports a recovery error, leave the app stopped and send support the exact message. Repeatedly deleting/recreating the app or volume makes recovery harder.

SFTP stopped working​

Check whether an attachment/detachment is in progress or the pool has reached its transfer allowance. Both can temporarily pause file access. After recovery or the allowance reset, retry with the credentials on the app's Files page. For a password or host problem, follow file access.

The app will not start​

Check attachment status and transfer usage first. The panel blocks starts when attached storage is not ready so the app cannot accidentally start against an empty fallback directory. If both are healthy, inspect the app's logs and send the relevant error to support.

Files look old after detaching​

Detachment returns the app to its original local files. The newer remote data stays in the detached volume. Stop the app and contact support about moving that data; do not delete the volume or keep writing to two competing copies.

Database files are not visible in SFTP​

That is expected for a managed database volume. Check the service through the application or the database guide. Support can help with an export or a database migration; changing raw database files over SFTP is not the file-access workflow.

Include this in a ticket​

Send the pool label, volume label, app name, service/path, current status and error, the time of the last action, and whether the issue followed an attachment, update, detach or transfer-limit event. Include the pool screenshot with any unrelated account details cropped out.