You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would recommend trying to revert #4030, it seems a few problems for AWS's s3 were introduced with it.
files have extra null characters appended, and I've also experienced #4129 (comment) which I've since found out has incurred a cost of 30USD from AWS because Dynmap silently ran up the monthly API call limit and then a fee for excess API calls in under a day. An impressive number, so be careful.
Try reverting #4030, and see how it goes. I'm currently looking into the idea of replacing the s3 library in use and making a PR.
Issue Description: Dynmap crashes on start when S3 storage type is used
Bucket is active and aws tool can read-write there with specified credentials (in config I masked with asterisk)
The text was updated successfully, but these errors were encountered: