Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
B

benneic

@benneic
About
Posts
3
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Need help connecting to Bedrock on LAN
    B benneic

    Solution was to connect from iPad to server using the FQDN pointing to the public IP of Cloudron.

    Unclear why I couldnt connect via private IP, but I was using local DNS pointing the FQDN to the private IP, so I switched that to the public ip. I think that is what fixed it.

    @girish thanks for the tip on the UDP scan, port was open via UDP on private IP.

    benneic@MacBookPro ~ % sudo nmap -sU -Pn -p 19132 192.168.1.100           
    Starting Nmap 7.95 ( https://nmap.org ) at 2025-05-17 08:37 AEST
    Nmap scan report for # (192.168.1.100)
    Host is up (0.0025s latency).
    
    PORT      STATE         SERVICE
    19132/udp open|filtered unknown
    
    Nmap done: 1 IP address (1 host up) scanned in 0.32 seconds
    
    Minecraft networking

  • Need help connecting to Bedrock on LAN
    B benneic

    I've just done a fresh install of MC Bedrock and configured with default settings. But I can not seems to connect with it from the iPad app while connected on the same network/subnet.

    App Title and Version: Minecraft Bedrock 1.21.80.3
    App ID: 613cef5b-96ff-489d-a8bf-c1f9c07cd4b4
    Package Version: net.minecraft.bedrock.cloudronapp@2.35.5
    Installed At: 3:59 PM
    Last Updated: Never

    MC Bedrock Server console shows:

    IPv4 supported, port: 19132: Used for gameplay and LAN discovery
    IPv6 supported, port: 19133: Used for gameplay
    Server started.
    

    Scaning the server & port from my computer:

    benneic@MacBookPro ~ % nmap -p 19132 192.168.1.100
    Starting Nmap 7.95 ( https://nmap.org ) at 2025-05-15 16:38 AEST
    Nmap scan report for # (192.168.1.100)
    Host is up (0.012s latency).
    
    PORT      STATE  SERVICE
    19132/tcp closed unknown
    
    Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
    

    Scaning listening ports on my server host (192.168.1.100):

    benneic@chopsticks:~$ sudo netstat -l -p --numeric-ports | grep 19132
    tcp        0      0 0.0.0.0:19132           0.0.0.0:*               LISTEN      847/dockerd         
    tcp6       0      0 [::]:19132              [::]:*                  LISTEN      847/dockerd         
    udp        0      0 0.0.0.0:19132           0.0.0.0:*                           847/dockerd         
    udp6       0      0 [::]:19132              [::]:*                              847/dockerd  
    

    Scanning listening ports inside the MC Bedrock docker container:

    root@613cef5b-96ff-489d-a8bf-c1f9c07cd4b4:/app/pkg# sudo netstat -l -p --numeric-ports | grep 19132
    udp        0      0 0.0.0.0:19132           0.0.0.0:*                           -                  
    

    I am surprised there is not a tcp socket listening inside the docker host.

    As far as the server console and logs are concerned it looks like it is running:
    3afe7251-5f97-4525-8e85-9bcb0812944c-image.png

    What am I missing here?

    Minecraft networking
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search