<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 07:17:11 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[BDS-1264] Unable to launch - Network port occupied, can&apos;t start server.</title>
                <link>https://bugs.mojang.com/browse/BDS-1264</link>
                <project id="11700" key="BDS">Bedrock Dedicated Server</project>
                    <description>&lt;p&gt;&lt;tt&gt;Upon trying to launched bedrock server, it appears that it is ignoring both options within &lt;font color=&quot;#ff0000&quot;&gt;server.properties&lt;/font&gt;:&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;server-port=19132
server-portv6=19133&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;The following output is observed:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# LD_LIBRARY_PATH=. ./bedrock_server
NO LOG FILE! - setting up server logging...
[2019-08-08 13:58:15 INFO] Starting Server
[2019-08-08 13:58:15 INFO] Version 1.12.0.28
[2019-08-08 13:58:15 INFO] Session ID e0d9fbf4-a584-4d6e-8df1-03e76330598f
[2019-08-08 13:58:15 INFO] Level Name: Bedrock level
[2019-08-08 13:58:15 INFO] Game mode: 0 Survival
[2019-08-08 13:58:15 INFO] Difficulty: 1 EASY
[2019-08-08 13:58:16 INFO] IPv4 supported, port: 0
[2019-08-08 13:58:16 INFO] IPv6 supported, port: 0
[2019-08-08 13:58:16 ERROR] Network port occupied, can&apos;t start server.
Quit correctly&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;It appears that BDS is trying to bind both IPv6 and IPv4 to port 0.&lt;/p&gt;

&lt;p&gt;Also, it is incorrectly identifying IPv6 as being supported, as this is disabled on the host via grub upon launch:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;&lt;span class=&quot;code-keyword&quot;&gt;default&lt;/span&gt;/grub:10:GRUB_CMDLINE_LINUX=&lt;span class=&quot;code-quote&quot;&gt;&quot;ipv6.disable=1&quot;&lt;/span&gt;&#160;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;This is with a fresh copy of BDS, with default config values present:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;server-name=Dedicated Server
gamemode=survival
difficulty=easy
allow-cheats=&lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
max-players=10
online-mode=&lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
white-list=&lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
server-port=19132
server-portv6=19133
view-distance=10
tick-distance=4
player-idle-timeout=30
max-threads=8
level-name=Bedrock level
level-seed=
&lt;span class=&quot;code-keyword&quot;&gt;default&lt;/span&gt;-player-permission-level=member
texturepack-required=&lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
content-log-file-enabled=&lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;No other processes or services are running on the ports set within the configuration.&lt;/p&gt;</description>
                <environment>Debian 10 (Buster)&lt;br/&gt;
&lt;br/&gt;
Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux&lt;br/&gt;
&lt;br/&gt;
openjdk 11.0.4 2019-07-16&lt;br/&gt;
&amp;nbsp;OpenJDK Runtime Environment (build 11.0.4+11-post-Debian-1deb10u1)&lt;br/&gt;
&amp;nbsp;OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Debian-1deb10u1, mixed mode, sharing)&lt;br/&gt;
&lt;br/&gt;
{color:#FF0000}*BDS Version 1.12.0.28*{color}</environment>
        <key id="254761">BDS-1264</key>
            <summary>Unable to launch - Network port occupied, can&apos;t start server.</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="4">Incomplete</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ErTnEc">Paul Bramhall</reporter>
                        <labels>
                            <label>awaiting-response</label>
                    </labels>
                <created>Thu, 8 Aug 2019 15:06:09 +0200</created>
                <updated>Mon, 21 Jun 2021 08:57:04 +0200</updated>
                            <resolved>Fri, 29 Jan 2021 17:19:51 +0100</resolved>
                                    <version>1.9.0.15</version>
                                                            <votes>1</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="1020220" author="JIRAUSER531695" created="Mon, 21 Jun 2021 08:57:04 +0200"  >&lt;p&gt;@Zizzy zizzy&lt;br/&gt;
&#8220;Failed successfully&#8221;. I laughed so hard that I spelt my coffee, luckily not on the keyboard.&lt;/p&gt;

&lt;p&gt;I&#8217;ve been running a Bedrock server in Docker for about a year and suddenly started having the port &#8216;0&#8217; issue. (bds v 1.17.1.01)&lt;/p&gt;

&lt;p&gt;After reading this I&#8217;ve set-up my server.properties&lt;/p&gt;

&lt;p&gt; SERVER_PORT_V6: &#8220;disable&#8221;&lt;/p&gt;

&lt;p&gt;Fails perfectly!&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="935675" author="zizzyzizzy" created="Tue, 2 Mar 2021 21:37:31 +0100"  >&lt;p&gt;This is still broken on Ubuntu 18 with Bedrock Server v1.16.201.3.&lt;/p&gt;

&lt;p&gt;If IPv6 is disabled completely via GRUB, Bedrock Server crashes during startup. There doesn&apos;t appear to be a way to tell it to only use IPv4, even when the entire server has already been configured to do so.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;/etc/apt/apt.conf.d/99force-ipv4&lt;/b&gt;:&lt;br/&gt;
Acquire::ForceIPv4 &quot;true&quot;;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;/etc/sysctl.conf&lt;/b&gt;:&lt;br/&gt;
net.ipv6.conf.all.disable_ipv6=1&lt;br/&gt;
net.ipv6.conf.default.disable_ipv6=1&lt;br/&gt;
net.ipv6.conf.lo.disable_ipv6=1&lt;br/&gt;
net.ipv6.bindv6only=1&lt;/p&gt;

&lt;p&gt;&lt;b&gt;/etc/default.grub&lt;/b&gt;:&lt;br/&gt;
GRUB_CMDLINE_LINUX_DEFAULT=&quot;ipv6.disable=1&quot;&lt;br/&gt;
GRUB_CMDLINE_LINUX=&quot;ipv6.disable=1&quot;&lt;/p&gt;

&lt;p&gt;IPv6 causes nothing but problems on every server I&apos;ve ever encountered, which is why we always disable it completely. If something odd is going on with networking/DNS/etc., disabling IPv6 and rebooting usually does the trick.&lt;/p&gt;</comment>
                            <comment id="907936" author="mega_spud" created="Fri, 29 Jan 2021 17:19:51 +0100"  >&lt;p&gt;Cleaning up old tickets:  This ticket had been set to &apos;Awaiting Response&apos;, but has not received a response from the reporter (~3 months+) so is being closed as &lt;em&gt;Incomplete&lt;/em&gt;.  If you feel this is still a valid issue then please comment, or create a new ticket following the &lt;a href=&quot;https://aka.ms/MCBugTrackerHelp&quot; title=&quot;How To Write helpful bug reports&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Issue Guidelines&lt;/a&gt; which includes steps to reproduce the problem.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Quick Links&lt;/b&gt;:&lt;br/&gt;
&#128211; &lt;a href=&quot;https://aka.ms/MCBugTrackerHelp&quot; title=&quot;How To Write Awesome Tickets! &#128175;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Issue Guidelines&lt;/a&gt; &amp;#8211; &#128172; &lt;a href=&quot;https://help.minecraft.net/hc/en-us/requests/new&quot; title=&quot;Account Support &#128377;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Mojang Support&lt;/a&gt; &amp;#8211; &#128231; &lt;a href=&quot;https://feedback.minecraft.net/&quot; title=&quot;Feedback and Suggestions &#9997;&#65039;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Suggestions&lt;/a&gt; &amp;#8211; &#128214; &lt;a href=&quot;http://minecraft.gamepedia.com/Minecraft_Wiki&quot; title=&quot;Minecraft Wiki &#127891;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Minecraft Wiki&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="741222" author="ionicecko" created="Wed, 24 Jun 2020 03:59:35 +0200"  >&lt;p&gt;Does this issue happen on a Ubuntu 18+ install?&lt;/p&gt;

&lt;p&gt;If so can someone please provide steps to reproduce:&lt;/p&gt;
&lt;blockquote&gt;
&lt;h4&gt;&lt;a name=&quot;WhatIexpectedtohappenwas...%3A&quot;&gt;&lt;/a&gt;What I expected to happen was...:&lt;/h4&gt;
&lt;p&gt;When I killed a squid, it should have dropped an ink sac.&lt;/p&gt;

&lt;h4&gt;&lt;a name=&quot;Whatactuallyhappenedwas...%3A&quot;&gt;&lt;/a&gt;What actually happened was...:&lt;/h4&gt;
&lt;p&gt;Instead, it dropped an apple.&lt;/p&gt;

&lt;h4&gt;&lt;a name=&quot;StepstoReproduce%3A&quot;&gt;&lt;/a&gt;Steps to Reproduce:&lt;/h4&gt;
&lt;ol&gt;
	&lt;li&gt;Find a squid (though we all know how difficult they are to find when you &lt;b&gt;actually&lt;/b&gt; want to find one).&lt;/li&gt;
	&lt;li&gt;Kill the squid.&lt;/li&gt;
	&lt;li&gt;Notice that it drops apples instead of ink sacs. How am I supposed to get black dye now?&lt;/li&gt;
&lt;/ol&gt;
&lt;/blockquote&gt;

&lt;p&gt;The original report was for Debian which is not a supported OS for BDS and therefore would not be a valid report unless it can be reproduced on a new Ubuntu install.&lt;/p&gt;</comment>
                            <comment id="667603" author="zizzyzizzy" created="Fri, 17 Apr 2020 00:16:56 +0200"  >&lt;p&gt;&lt;b&gt;Update&lt;/b&gt; - the 99999 port hack stopped working randomly.&lt;/p&gt;

&lt;p&gt;Now I have to script it so a random, unused lower port is assigned to the server-portv6 line:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
freeport=$(comm -23 &amp;lt;(seq 1025 19130 | sort) &amp;lt;(ss -Huan | awk &lt;span class=&quot;code-quote&quot;&gt;&apos;{print $4}&apos;&lt;/span&gt; | cut -d&lt;span class=&quot;code-quote&quot;&gt;&apos;:&apos;&lt;/span&gt; -f2 | sort -u) | shuf | head -n 1)&#160;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;That works fine now. Just make sure to remove the kernel&#160;&lt;b&gt;ipv6.disable=1&lt;/b&gt; line if it&apos;s active, and then reboot. I found out on a different Ubuntu server that with that kernel option enabled, there is no work-around to this frustrating issue.&lt;/p&gt;</comment>
                            <comment id="654488" author="zizzyzizzy" created="Fri, 27 Mar 2020 00:06:56 +0100"  >&lt;p&gt;@Paul Thanks for that!&lt;/p&gt;

&lt;p&gt;Even with ipV6 disabled, if you specify just a random ipV6 port that happens to be in use by anything, the server says &quot;IPv6 supported&quot;, then &quot;Network port occupied&quot;. Same if you leave it undefined, same if you remove it from server.properties completely.&lt;/p&gt;

&lt;p&gt;Even more head-scratching: if you set the port to something &lt;b&gt;completely invalid&lt;/b&gt;, it starts up fine. I &lt;b&gt;certainly&lt;/b&gt; &lt;b&gt;appreciate&lt;/b&gt; that this is unsupported and basically a &quot;gift&quot; from Microsoft to have it available at all, but seriously - who writes this stuff?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&quot;Failed successfully!&quot;&lt;/em&gt;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;[2020-03-26 23:03:56 INFO] IPv4 supported, port: 19134
[2020-03-26 23:03:56 INFO] IPv6 not supported
[2020-03-26 23:03:56 INFO] IPv4 supported, port: 35122
[2020-03-26 23:03:56 INFO] IPv6 not supported
[2020-03-26 23:03:57 INFO] Server started.
stop
Quit correctly&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# grep port server.properties
server-port=19134
server-portv6=99999&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="647430" author="uxorious" created="Sun, 15 Mar 2020 22:01:31 +0100"  >&lt;p&gt;Just ran into the same.&lt;/p&gt;

&lt;p&gt;When disabling with GRUB, it refused to start the server.&lt;/p&gt;

&lt;p&gt;After sysctl, it starts.&lt;br/&gt;
But as in the log above, it seems really confused about what port to use.&lt;/p&gt;</comment>
                            <comment id="641267" author="lzap" created="Sat, 29 Feb 2020 15:15:48 +0100"  >&lt;p&gt;For the record, Minecraft exits with this weird error if it&apos;s unable to write to data directories. I unpacked the ZIP file accidentaly by root, executed as minecraft user and the error was the exactly same one. Beware!&lt;/p&gt;</comment>
                            <comment id="573461" author="ertnec" created="Thu, 8 Aug 2019 16:08:49 +0200"  >&lt;p&gt;After some further digging, it appears that BDS doesn&apos;t respect using the kernel boot-time option &lt;font color=&quot;#FF0000&quot;&gt;ipv6.disable=1&lt;/font&gt; and relies entirely on ipv6 being disabled via sysctl:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 1&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Once ipv6 was disabled via sysctl, BDS would launch successfully:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;NO LOG FILE! - setting up server logging...
[2019-08-08 15:04:12 INFO] Starting Server
[2019-08-08 15:04:12 INFO] Version 1.12.0.28
[2019-08-08 15:04:12 INFO] Session ID 41d3e2e9-0e7a-4b0c-bbd4-2554fc0b8b08
[2019-08-08 15:04:12 INFO] Level Name: Bedrock level
[2019-08-08 15:04:12 INFO] Game mode: 0 Survival
[2019-08-08 15:04:12 INFO] Difficulty: 1 EASY
[2019-08-08 15:04:14 INFO] IPv4 supported, port: 19132
[2019-08-08 15:04:14 INFO] IPv6 not supported
[2019-08-08 15:04:14 INFO] IPv4 supported, port: 50531
[2019-08-08 15:04:14 INFO] IPv6 not supported
[2019-08-08 15:04:15 INFO] Server started.&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="376157">BDS-9198</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i11v3z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>