# Intermittent "500 Internal Server Error" with Snap and DigitalOcean S3 **URL:** \ **Category:** ℹ️ Support\ **Created:** [October 1, 2020, 6:44pm UTC](https://help.nextcloud.com/t/intermittent-500-internal-server-error-with-snap-and-digitalocean-s3/93715 "2020-10-01T18:44:06Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Roenix](https://help.nextcloud.com/letter_avatar/roenix/32/6_22734026db12803ebb3e059622ac3534.png) [@Roenix](https://help.nextcloud.com/u/Roenix)\ **Post date:** [October 2, 2020, 8:45am UTC](https://help.nextcloud.com/t/intermittent-500-internal-server-error-with-snap-and-digitalocean-s3/93715/5 "2020-10-02T08:45:53Z")
At the moment Nextcloud works fine for normal workloads again for me. But for migrating a lot of files I choose not to upload via the webclient or sync client, but put the files directly in the data directory on the server and then forced Nextcloud to reindex the files with the command: sudo nextcloud.occ files:scan --all See also: > [@Tutorial: How to migrate mass data to a new NextCloud server](https://help.nextcloud.com/t/tutorial-how-to-migrate-mass-data-to-a-new-nextcloud-server/9418/20): > > Great post I have needed to do this with over 16gb of data a few times I never knew bout the console.php script to force a scan and update the database so I always spent a few days using the sync app for each user. In the owncloud days (and i think in the early nextcloud versions) you use to be able to just copy the data to the webroot data folder and it would just work but this option was removed a few years ago for reasons I never understood. Just an fyi rather than running ls to check the pr… This worked for me, although I consider it a workaround, not a definitive solution to the errors. --- _[View the full topic](https://help.nextcloud.com/t/intermittent-500-internal-server-error-with-snap-and-digitalocean-s3/93715)._