mojira.dev
BDS-9198

Bug - Bedrock server uses port 0 instead of the defined ones

Ubuntu 20.04

The bedrock minecraft server tries to use port 0 for both ipv4 and ipv6 when started on a VPS server I own.

NO LOG FILE! - setting up server logging...
[2020-10-02 14:48:43 INFO] Starting Server
[2020-10-02 14:48:43 INFO] Version 1.16.40.2
[2020-10-02 14:48:43 INFO] Session ID aa262aba-f109-4d9f-92dc-8f8ace7c656c
[2020-10-02 14:48:43 INFO] Level Name: My World
[2020-10-02 14:48:43 INFO] Game mode: 1 Creative
[2020-10-02 14:48:43 INFO] Difficulty: 0 PEACEFUL
[2020-10-02 14:48:43 INFO] opening worlds/My World/db
[2020-10-02 14:48:47 INFO] IPv4 supported, port: 0
[2020-10-02 14:48:47 INFO] IPv6 supported, port: 0
[2020-10-02 14:48:47 ERROR] Network port occupied, can't start server.

as a reference, IPV6 is even disabled system wide so it shouldn't even say supported.

I also tried to change multiple times the port but no changes, I can thus consider it a bug, it also happens when using docker.

 

as a reference this is the output of ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:16:3c:39:ae:af brd ff:ff:ff:ff:ff:ff
    inet 193.142.58.142/24 brd 193.142.58.255 scope global eth0
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:0a:29:10:4d brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

 

Linked issues

Comments 4

There is currently no way to disable IPv6 for BDS. It showing a port of 0 indicates it was unable to bind to a port, not that its binding to port 0.

We had a previous report for this under BDS-1264 but it was closed as awaiting response as there was no clear steps to reproduce the issue. If you'd like to head over there and provide details on how you disabled IPv6 (reproduction steps that outline any changes you made from a default install) in a comment the report will reopen.

Please try to use the template I provided to the OP to make it easy to reproduce.

There is currently no way to disable IPv6 for BDS. It showing a port of 0 indicates it was unable to bind to a port, not that its binding to port 0.

We had a previous report for this under BDS-1264 but it was closed as awaiting response as there was no clear steps to reproduce the issue. If you'd like to head over there and provide details on how you disabled IPv6 (reproduction steps that outline any changes you made from a default install) in a comment the report will reopen.

Please try to use the template I provided to the OP to make it easy to reproduce.

I actually found a fix for my issue but that was more of a weird workaround

and I didn't disable ipv6 for bedrock but system wide but weirdly it still detected ipv6

I re-enabled IPV6 on my system then tried a different trick, I've deleted the current bedrock server and re-extracted the server files then I made it so the IPV6 in the server properties was set to the port 999999

after doing this the server worked and assigned a random port to the ipv6

I actually found a fix for my issue but that was more of a weird workaround

and I didn't disable ipv6 for bedrock but system wide but weirdly it still detected ipv6

I re-enabled IPV6 on my system then tried a different trick, I've deleted the current bedrock server and re-extracted the server files then I made it so the IPV6 in the server properties was set to the port 999999

after doing this the server worked and assigned a random port to the ipv6

THEO LAMCILAK

(Unassigned)

Unconfirmed

Retrieved