-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
BlueMapWebChat 4.7.0 · Minecraft 1.18–26.2 · Java 17 baseline
- Confirm
enabled: true - Check
http.hostandhttp.port - Check for a port conflict
- Confirm reverse-proxy upstream points to
127.0.0.1:8899 - Enable
standalone-web.enabledwhen a standalone page is required
- Enable
web-addon.auto-install - Enable
web-addon.auto-patch-webapp-conf - Check BlueMap paths
- Read installation/patch log messages
- Run
/bluemap reload - Refresh browser cache
- Check HTTPS domain and cookie path
- Confirm link code expiration
- Check login lockout logs
- Verify
auth.password-login - Check administrator IP restrictions
- Set
chat.send-web-chat-to-game: true - Confirm players are online
- Check chat-format plugin conflicts
- For relay messages, confirm
server-relay.delivery.game: true
- Set
chat.broadcast-ingame-chat-to-web: true - Check player permissions and event cancellation
- Check whether another chat plugin exclusively consumes the event
- Enable
reply.game-click.enabled - For local game messages, enable
local-game-chat - Check chat-format plugin conflicts
- URL parts opening a link instead of replying is expected
- Confirm the BMChat emoji file exists
- Check ImageEmojis-Bero shared folder and permission
- Enable
replaceInCommands - Run
/emojis reloadand/emojis update - Confirm matching emoji files on every relay server
- Compare receiver
peers[].idwith senderserver-id - Reload the receiving server too
- Check the active-peer log
- Compare the actual effective secrets
- Confirm the proxy does not modify body or HMAC headers
- Check server clock synchronization
- Confirm every server runs the same fixed build
- Check for another plugin reposting relay messages
- Keep
game-to-discord: falsewhen DiscordSRV already forwards game chat
- Confirm HTTPS
- Check notification permission
- Check Service Worker and Push API support
- On iOS, use an installed Home Screen web app
- Check VAPID subject and key files
- Bukkit/Spigot/Paper-compatible server or compatible fork
- Java 17 or newer for build/runtime
- BlueMap plugin and a working BlueMap webroot
- The chat API port must be reachable by the browser. Default:
8899/tcp - DiscordSRV is optional and only needed when enabling the Discord bridge
mvn clean packageOutput:
target/BlueMapWebChat-4.7.0.jar
- Stop the Minecraft server.
- Replace the old BlueMapWebChat jar in
plugins/with the new jar. - Start the server.
- Check
plugins/BlueMapWebChat/config.yml. - Run
/bmchat reloador restart if you changed important paths. - Run
/bluemap reloadif BlueMap does not pick up webapp changes automatically. - Hard-refresh the browser.
grep -R "bluemap-web-chat" -n /opt/minecraft/server/plugins/BlueMap/webapp.confThe entries should include the current version query, for example:
addons/bluemap-web-chat/config.js?v=4.7.0-<cache-token>
addons/bluemap-web-chat/chat.js?v=4.7.0-<cache-token>
addons/bluemap-web-chat/chat.css?v=4.7.0-<cache-token>
Also verify the actual web files were updated:
find /opt/minecraft/server -path "*addons/bluemap-web-chat/chat.js" -printf "%p %TY-%Tm-%Td %TH:%TM\n"If /api/config works but the chat panel does not appear, BlueMap may be serving a different webroot than the one configured in BlueMapWebChat.
Check BlueMap's webapp.conf and make sure these match your setup:
web-addon:
bluemap-web-root: "bluemap/web"
bluemap-webapp-conf: "plugins/BlueMap/webapp.conf"
addon-path: "addons/bluemap-web-chat"When testing web UI changes, open DevTools, enable Network -> Disable cache, then hard-refresh the page.
You can also check the loaded version in the console:
[...document.scripts]
.filter(s => s.src.includes("bluemap-web-chat"))
.map(s => s.src)If BlueMap still loads an older BlueMapWebChat addon version after updating, run /bmchat reload once more or restart the server, then hard-refresh the browser.
For public servers, use HTTPS through Caddy or nginx. See:
-
docs/CADDY_HTTPS_EN.mdandexamples/caddy/Caddyfile -
docs/NGINX_HTTPS_EN.mdandexamples/nginx/bluemapwebchat.conf