Server prompts to download and install server recommended resource pack. when I click yes it downloads it and it doesn't work. I have tried several times and every time it doesn't work. I have tried with a popular resource pack and one that I am in the process of making that doesn't show up when it is a zip. (another problem that even the power of the entire internet can't solve for some reason)
Linked issues
Attachments
Comments 7
This is a packet capture showing the attempted download of a resource pack using 1.8.1 clients and server. They fail with a number of TCP connection resets.
Wow. I should've caught that a lot sooner.
Full log here: http://pastebin.com/RYUQaYbH
I think the key lines, and correct me if I'm wrong:
[08:16:39] [Downloader 0/WARN]: Deleting /home/talia/.minecraft/server-resource-packs/legacy_Conquest_18zip as it does not match what we currently have (72544314 vs our 0).
java.io.IOException: Filesize is bigger than maximum allowed (file is 3.0, limit is 52428800)
Where is that limit configured? Please don't tell me it's hardcoded
I cannot get server-side resource packs to work either. I've done some troubleshooting on this and found the following. This is the line from my server.properties:
resource-pack=http\://daniprice.me/Conquest_1.8.zip
That URL is valid, has no redirects, it's a plain as vanilla apache server running on a current Debian. Here's the apache access logs:
67.173.187.207 - - [16/Feb/2015:07:45:51 +0000] "GET /Conquest_1.8.zip HTTP/1.1" 200 10993216 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.94 Safari/537.36"
67.173.187.207 - - [16/Feb/2015:07:47:37 +0000] "GET /Conquest_1.8.zip HTTP/1.1" 200 31856 "-" "Java/1.7.0_75"
67.173.187.207 - - [16/Feb/2015:07:52:17 +0000] "GET /Conquest_1.8.zip HTTP/1.1" 200 72400 "-" "Java/1.6.0_65"
The first line is me requesting the file from my browser, line 2-3 are two different clients, diff javas. I've tried this with the vanilla server, and with both spigot and bukkit.
See the attached file for a packet capture from the webserver side and from client side. They both show a bunch of TCP connection resets at the end.