Dynmap-Forge/Fabric

Dynmap-Forge/Fabric

888k Downloads

My Dynmap isn't working

Cassolotl opened this issue · 9 comments

commented

This is where it's meant to be: http://144.76.213.176:25591/

It's been fine for ages, but I just updated to 1.21 Spigot. Now it's got this:

[22:10:05] [Dynmap Render Thread/INFO]: [dynmap] Loading default resource pack
[22:10:05] [Dynmap Render Thread/WARN]: [dynmap] Resource assets/minecraft/textures/all.png for mod minecraft not found

I am not sure how to resolve this - are you able to help?

commented

Just did /ver dynmap:

dynmap version 3.7-SNAPSHOT-948

commented

i am also having this same issue with snapshot-949

commented

If I'm correct this is not an error but a warning that it couldn't load a resource pack. Not really necessary for the function of dynmap as my server throw it and dynmap still loads

Is the server or computer still listening on the port you've assigned?

commented

Is the server or computer still listening on the port you've assigned?

How do I check?

commented

Here's the startup blurb:

[10:19:32] [Server thread/INFO]: [dynmap] Added 20 custom biome mappings
[10:19:32] [Server thread/WARN]: [dynmap] Loaded class ru.tehkode.permissions.bukkit.PermissionsEx from PermissionsEx v1.23.4 which is not a depend or softdepend of this plugin.
[10:19:32] [Server thread/INFO]: [dynmap] Using PermissionsEx 1.23.4 for access control
[10:19:33] [Server thread/INFO]: [dynmap] Mod Support processing completed
[10:19:35] [Server thread/INFO]: [dynmap] Loaded 27 shaders.
[10:19:35] [Server thread/INFO]: [dynmap] Loaded 83 perspectives.
[10:19:35] [Server thread/INFO]: [dynmap] Loaded 22 lightings.
[10:19:35] [Server thread/INFO]: [dynmap] Starting enter/exit processing
[10:19:35] [Dynmap Render Thread/INFO]: [dynmap] Finish marker initialization
[10:19:35] [Server thread/INFO]: [dynmap] Web server started on address [0.0.0.0:25591](http://0.0.0.0:25591/)
[10:19:35] [Server thread/INFO]: [dynmap] version 3.7-SNAPSHOT-948 is enabled - core version 3.7-SNAPSHOT-949
[10:19:35] [Server thread/INFO]: [dynmap] For support, visit our Discord at https://discord.gg/s3rd5qn
[10:19:35] [Server thread/INFO]: [dynmap] For news, visit https://reddit.com/r/Dynmap or follow https://universeodon.com/@dynmap
[10:19:35] [Server thread/INFO]: [dynmap] To report or track bugs, visit https://github.com/webbukkit/dynmap/issues
[10:19:35] [Server thread/INFO]: [dynmap] If you'd like to donate, please visit https://www.patreon.com/dynmap or https://ko-fi.com/michaelprimm
[10:19:35] [Server thread/INFO]: [dynmap] Loaded 3 maps of world 'world'.
[10:19:35] [Server thread/INFO]: [dynmap] Loaded 1 maps of world 'world_nether'.
[10:19:35] [Server thread/INFO]: [dynmap] Loaded 2 maps of world 'world_the_end'.
[10:19:35] [Server thread/INFO]: [dynmap] Enabled
commented

I just checked my support ticket history - my host has a habit of moving the server to a new IP and I have to ask them to assign us a port for stuff like Dynmap. Soooo I think that is it. 🤦 Anyway, once that's sorted I'll get back to you on whether the resource pack thing is an issue.

commented

Just found something critical regarding the Spigot 1.21 version of Dynmap (version 3.7-SNAPSHOT-948):

It requires ProtocolLib to run. The 1.21 version of ProtocolLib (the one that would be compatible with Dynmap 1.21) produces a startup error. This error is nothing to do with your server, but rather the plugin itself. The only thing you can do is wait for a stable version of ProtocolLib to release for version 1.21.

I've reported the error on the ProtocolLib Github, you can see that here.

commented

It really depends on what OS you are using for the system. The following could tell you for each system

Ubuntu: ss -a | grep "25591"
Windows: netstat -a | find "25591"

Just found something critical regarding the Spigot 1.21 version of Dynmap (version 3.7-SNAPSHOT-948):

It requires ProtocolLib to run. The 1.21 version of ProtocolLib (the one that would be compatible with Dynmap 1.21) produces a startup error. This error is nothing to do with your server, but rather the plugin itself. The only thing you can do is wait for a stable version of ProtocolLib to release for version 1.21.

I've reported the error on the ProtocolLib Github, you can see that here.

I have no clue what your on about as my current server running this exact version doesn't have this installed and its working just fine with that very ProtocolLib not install on it at all.

image_2024-07-17_101725821

commented

I sent a support ticket to my host, and they replied to say that it was working - and lo, it was! So, I have no idea what happened, and it is troubling, but I don't think I will get to the bottom of it. :S Thank you everyone for trying to help!