snapshot create internal server error when using packer to create image

I use the Oxide packer-plugin to create vw images. This has been working for a while now. But recently I've started hitting 500s on the snapshot create step.

The following is from a build on rack3, so I do not have access to the logs, perhaps @augustuswm does?

==> oxide-instance.vivado: Clearing shell history
==> oxide-instance.vivado: Cleanup complete
==> oxide-instance.vivado: Provisioning with shell script: /tmp/packer-shell2176865329
==> oxide-instance.vivado: Stopping Oxide instance
==> oxide-instance.vivado: Waiting for Oxide instance to stop: Currently stopping.
==> oxide-instance.vivado: Waiting for Oxide instance to stop: Currently stopping.
==> oxide-instance.vivado: Waiting for Oxide instance to stop: Currently stopping.
==> oxide-instance.vivado: Waiting for Oxide instance to stop: Currently stopping.
==> oxide-instance.vivado: Waiting for Oxide instance to stop: Currently stopping.
==> oxide-instance.vivado: Oxide instance is stopped.
==> oxide-instance.vivado: Creating Oxide snapshot
==> oxide-instance.vivado: Failed creating Oxide snapshot.
==> oxide-instance.vivado: Provisioning step had errors: Running the cleanup provisioner, if present...
==> oxide-instance.vivado: Checking if Oxide instance is stopped: 0e61626f-b3eb-44e8-aa83-217dba26b1c8
==> oxide-instance.vivado: Deleting Oxide instance: 0e61626f-b3eb-44e8-aa83-217dba26b1c8
==> oxide-instance.vivado: Deleting Oxide disk: 79c872d6-b47b-472b-8bc4-92423117d3e4
==> oxide-instance.vivado: Deleting Oxide SSH public key: aa0b9e1d-a99f-4eae-8397-442a869def9d
Build 'oxide-instance.vivado' errored after 33 minutes 53 seconds: POST https://oxide.sys.r3.oxide-preview.com/v1/snapshots?project=vw-beta
----------- RESPONSE -----------
Status: 500 Internal
Message: Internal Server Error
RequestID: 8f51f70b-770c-4642-8896-5b543d9e4a55
------- RESPONSE HEADERS -------
Content-Type: [application/json]
X-Request-Id: [8f51f70b-770c-4642-8896-5b543d9e4a55]
Date: [Wed, 09 Sep 2026 06:43:58 GMT]
Content-Length: [124]

Start with the snapshot-create API request at POST /v1/snapshots and use request ID 8f51f70b-770c-4642-8896-5b543d9e4a55 to locate the server-side failure. Reproduce the Packer image workflow if possible and inspect the relevant service logs; done means the snapshot step no longer returns an unexplained 500.