Uploads and downloads are getting the 500 Internal Server Error response.
Uploads seem to complete, but the downloads do not.
What method can be advised to us to transfer solution files between our own computers internally ?
Which files are involved and where do we need to place them ?
Weekends are the ideal time for us to work on your issues, problems like these severely hamper our progress.
Thanks to Bletchley Park for reporting the bug. Over in #bugs-and-feedback on Discord, jflat06 responded that there are disk space problems. He's archiving data to free up space, but says it will take some time.
We went through something like this a couple of months ago. One workaround for sharing with others is to locate the ir_solution file for your save and drag it over to your group Discord channel. Group members can then download it to their Foldit directory. It should show up in Open/Share Solutions as usual.
Bletchley Park outline the procedure for locating the ir_solution file
in this post: https://fold.it/forum/suggestions/how-to-copy-solutions-locally-if-the-server-is-down
The "server response 500" errors have been resolved.
The problem was a lack of disk space, which jflat06 was able to address.
Uploads which received the "server response 500" appeared in the list, but the data file was never created on the Foldit server due to the space issue. The corresponding database entry did get created, but it contained only the metadata, like the solution name and description.
Uploads which failed this way will always get "server response 500" on an attempt to load or download them. A fresh upload corrects this part of the problem. The original failed upload can be deleted, although Foldit must be restarted to see that the delete was actually successful, due to a pre-existing bug.
Saved solutions (seen on the right side of Open/Share Solutions) were not impacted by the problem, and can simply be uploaded again. (It's probably a good idea to change the solution name or description to indicate it's a new upload.)
Thank you all for your patience with this.
We're trying to make sure this doesn't happen again!