naive nebula
Im self hosting a Debian Linux VM with CASA OS running Crafty that is hosting my paper-1.21.3 minecraft server.
I can successfully connect outside my network using any java client but am having issues getting bedrock users connecting.
I have 25565 and 19132 on both tcp/udp port forwarding on my router to the VM.
Just at a bit of a loss on where I should be looking
DUMP FILES = https://dump.geysermc.org/SCaHlW5xnNeTJyy2edEtECfJUcvlFOCe
Any help is much appropriated
frosty shellBOT
Im self hosting a Debian Linux VM with CASA OS running Crafty that is hosting my...
naive nebula
I am able to log into the server with bedrock client on port 19132, but only on the LAN, still am not able to log in outside the local network. However java is able to connect both on LAN and outside the network even using a domain name.
using https://mcsrvstat.us/ I seem to be able to reach the server on 19132 using the domain name.
Any ideas where my issue might be here? I seem to be able to reach the server outside my network on https://mcsrvstat.us/, but still cant connect with the minecraft bedrock client... however on the local area network using the local ip minecraft bedrock clients works fine
trail wing
So far, we've seen quite a few issues specifically to the casa os + crafty combo
we'd recommend to just use debian or ubuntu, or try without crafty
alternatively, try using playit.gg for the bedrock tunnel to see if it's portforwarding
naive nebula
After triple checking my port forwards and firewall it now just started working, well sorta. I am using my own domain for the hostname and when outside the LAN hostname works now with bedrock, however hostname does not connect when on the LAN, even though bedrock can see the status of the server. Once I try to connect and fail on LAN the server status goes away, but switch networks to outside the LAN and everything works again. Also the dedicated IP works both on LAN and WAN