Support

Can you please confirm that all backup parts exist on the S3 bucket and there are no discontinuities? For example, if you have files .j01 through .j10 but the next one is .j12 (not .j11) the download will stop on the assumption that there are no more parts to be found.

Regarding the error: it is expected and completely unrelated to your issue. Every time you access Solo it checks whether your configuration file is inaccessible over the web. That's what causing the access error and it is a good thing; it means that your configuration cannot be read by a random user by accessing its well-known URL. In case Solo detects that the file is accessible over the web it shows a big, scary notice to let you know that you must fix this issue for security reasons. In any case, that error should be in your logs and is unrelated to your issue. Just forget about it.

Sorry for the delay. Debugging file transfers, especially those involving files at volume, are notoriously slow since they're affected by the network speed.

Apparently the whole problem was a single mistyped letter. I had put "remorefiles" instead of "remotefiles". This meant that the download started, it hit a breakpoint to prevent it from timing out, but the next run was never taking place because of the typo.

I have fixed that in this developer's build. You will need to update manually to it per the documentation instructions under "Manual update method".