Troubleshooting foundry-ops

What you see	What to do
Download failed. Timed URLs expire after 5 minutes	The link has expired. Copy a fresh Timed URL from Purchased Licenses on foundryvtt.com; the installer asks again. With FOUNDRY_SOURCE set, it stops instead, so run it again with a fresh link.
Not an http(s):// URL or an existing file	Paste the whole Timed URL, starting with https://, or the path to a zip that exists inside the container.
Not a valid zip	The download isn’t a Foundry zip, or it’s the Windows or macOS package. Choose the Node.js package (the Linux one also works).
No Foundry main.js/package.json in that zip	Choose the Node.js package.
No terminal to ask on	The installer is running without a terminal, as from Ansible. Set FOUNDRY_SOURCE (see Unattended install).
Foundry did not answer on port 30000	After starting Foundry, the scripts wait up to a minute for it to answer. Check its log with journalctl -u foundryvtt and its state with systemctl status foundryvtt.
options.json not created yet	Foundry hadn’t written its settings within a minute of its first start. Set UPnP and the proxy settings in Foundry’s setup screen.
No FoundryVTT Installation Found!	update found no /opt/foundryvtt/app. Run it in a container that foundry-ops installed.
curl: (22) ... 404 lines during the install	Harmless. The engine looks for a banner that foundry-ops doesn’t have.

To see where everything is, and the service commands, see Layout.

Open an issue on GitHub. Include your Proxmox VE version, the Foundry version, whether you installed interactively or unattended, and the error you saw.

Never attach Foundry files or download links to an issue or pull request: no Timed URLs, license keys, zips or Foundry app files. A Timed URL works like a password while it’s valid. Pull requests that add Foundry files or download links fail the project’s checks.

Problems with Foundry VTT itself go to Foundry Gaming, not to foundry-ops.

Report security problems privately, through GitHub’s private vulnerability reporting for foundry-ops, not in a public issue. Expect a first reply within a week.

That covers the foundry-ops scripts and what they set up in a container: the service user, permissions, changes to options.json, and how the download link is handled. Report problems in Foundry VTT to Foundry Gaming, and problems in the community-scripts engine to community-scripts.