stewi1014
commented
3 weeks ago 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 https://github.com/webbukkit/dynmap/pull/4129#issuecomment-2434507151 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
Dynmap Version: v3.7-SNAPSHOT-948
Server Version: 1.21.1-128-master@d348cb8 (2024-10-21T16:23:24Z)
Pastebin of Configuration.txt: https://pastebin.com/HKRi3e3g
Pastebin of crashlogs: https://pastebin.com/p0rMJAfA
Steps to Replicate: Setup with Paper 1.21.1, dynmap 3.7-SNAPSHOT-948, AWS S3 bucket (with custom endpoint), restart the server
[x] I have looked at all other issues and this is not a duplicate
[x] I have been able to replicate this
Bucket is active and aws tool can read-write there with specified credentials (in config I masked with asterisk)