# How do I fix a "The resource you were accessing could not be found" error when restoring a Droplet from a snapshot?

The [**Restore Droplet** option](https://docs.digitalocean.com/products/snapshots/how-to/create-and-restore-droplets/index.html.md#restore-a-snapshot-on-an-existing-droplet) overwrites a Droplet’s data with specified snapshot. An error saying “The resource you were accessing could not be found” occurs when the Droplet are trying to restore no longer exists,

In this situation, [create a new Droplet from the snapshot](https://docs.digitalocean.com/products/snapshots/how-to/create-and-restore-droplets/index.html.md#create-new-droplets-from-a-snapshot) instead.

## Related Topics

[Can I restore individual files or directories from a snapshot or a backup?](https://docs.digitalocean.com/support/can-i-restore-individual-files-or-directories-from-a-snapshot-or-a-backup/index.html.md): The only way to restore files from an image is to recreate a Droplet or volume from the image and copy the flies from there.

[Why is my snapshot's size different from reported disk usage?](https://docs.digitalocean.com/support/why-is-my-snapshots-size-different-from-reported-disk-usage/index.html.md): Snapshots of Droplets are a best estimate based on the disk usage. Snapshots of volumes operate at the block storage level, so the snapshot size may not match what the filesystem reports.

[Do snapshots retain the IP address of the Droplet they were created from?](https://docs.digitalocean.com/support/do-snapshots-retain-the-ip-address-of-the-droplet-they-were-created-from/index.html.md): No, but you can use reserved IPs to assign the same address to new or redeployed Droplets.