Updated to the latest PreAlpha and enabled MIS2's FTP server while disabling the one in MIS. It reports error 216 and shuts down when I try to start.

---------- Mystic v1.12 A36 2017/11/19 Mon, Nov 20 2017 (loglevel 3)
+ 11:28:02 MANAGER Starting event system
+ 11:28:02 MANAGER Starting 5 server(s)
+ 11:28:02 FTP Data port range 60000 to 60004
+ 11:28:02 BINKP Listening on IPV4 port 24554 using interface "0.0.0.0"
+ 11:28:02 SSH Listening on IPV4 port 22 using interface "0.0.0.0"
+ 11:28:02 RLOGIN Listening on IPV4 port 513 using interface "0.0.0.0"
+ 11:28:02 TELNET Listening on IPV4 port 23 using interface "0.0.0.0"
+ 11:28:02 FTP Listening on IPV4 port 21 using interface "0.0.0.0"
+ 11:28:02 FTP Resolving domain: deepspace94.com
+ 11:28:02 EVENT Starting 7 event(s)
+ 11:28:02 FTP Error 216: Shutting down server

--- Mystic BBS v1.12 A36 2017/11/19 (Windows/32)
* Origin: Deep Space '94 * telnet://deepspace94.com * fnord (21:2/136)

Updated to the latest PreAlpha and enabled MIS2's FTP server while disabling the one in MIS. It reports error 216 and shuts down when I try to start.

Did you happen to try to create a FTP server prior to this prealpha?

--- Mystic BBS v1.12 A36 2017/11/20 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/20/17, g00r00 said the following...

Did you happen to try to create a FTP server prior to this prealpha?

I was running it in MIS but I don't recall trying to create one in MIS2. I
saw the note about that in the whatsnew - how would I nuke whatever's there just in case?

--- Mystic BBS v1.12 A36 2017/11/19 (Windows/32)
* Origin: Deep Space '94 * telnet://deepspace94.com * fnord (21:2/136)

On 11/20/17, deepthaw said the following...

I was running it in MIS but I don't recall trying to create one in MIS2.
I saw the note about that in the whatsnew - how would I nuke whatever's there just in case?

Just disable it in configuration, then re-enable it, I also turned on
anonymous (toggle it on and off if you like) and after shutting down mis2 and restarting it, it worked fine.

--- Mystic BBS v1.12 A36 2017/11/19 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

I was running it in MIS but I don't recall trying to create one in MIS2.
I saw the note about that in the whatsnew - how would I nuke whatever's there just in case?

If you went into MIS2 servers and created a FTP server then you'd just have
to delete it and remake it, otherwise you could corrupt some things.

--- Mystic BBS v1.12 A36 2017/11/20 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Just disable it in configuration, then re-enable it, I also turned on anonymous (toggle it on and off if you like) and after shutting down
mis2 and restarting it, it worked fine.

If you created the FTP server before the FTP was in the whatsnew (from an earlier prealpha) then you should physically delete the server in the configuration and create a new one.

Setting active to "No" does not get you in the safe zone; It has to be physically deleted or you risk unknown behavior because the structure of the data for FTP server changed.

Or if all of the settings look "normal" and it works, then so be it :)

FYI - I think I fixed the majority of the badness you were seeing in the Linux version tonight.

--- Mystic BBS v1.12 A36 2017/11/20 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/20/17, g00r00 said the following...

If you went into MIS2 servers and created a FTP server then you'd just have to delete it and remake it, otherwise you could corrupt some things.

I deleted and remade it multiple times, and still getting the same error. It always happens after it says "resolving deepspace94.com" (don't know if
that's related or coincidental.)

I tried turning passive mode on/off and anonymous mode on/off as well as deleting/creating the server multiple times.

--- Mystic BBS v1.12 A36 2017/11/20 (Windows/32)
* Origin: Deep Space '94 * telnet://deepspace94.com * fnord (21:2/136)

I deleted and remade it multiple times, and still getting the same
error. It always happens after it says "resolving deepspace94.com"
(don't know if that's related or coincidental.)

Are you using Windows XP?

--- Mystic BBS v1.12 A36 2017/11/21 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/21/17, g00r00 said the following...

Are you using Windows XP?

Windows Server 2003 R2 SP2 32-Bit (it's an AWS EC2 instance.)

FTP worked fine (well, at least didn't crash) in MIS.

--- Mystic BBS v1.12 A36 2017/11/20 (Windows/32)
* Origin: Deep Space '94 * telnet://deepspace94.com * fnord (21:2/136)

I deleted and remade it multiple times, and still getting the same error. It always happens after it says "resolving deepspace94.com" (don't know if that's related or coincidental.)

Are you using Windows XP?

I've updated the pre-alpha just a little bit ago (for the second time today) and this one might fix up the FTP thing if you are using Windows XP. Windows XP didn't natively support Winsock2/IPV6 (among other things) so sometimes I have to jump through hoops to keep supporting it.

This particular hoop has been jumped :)

--- Mystic BBS v1.12 A36 2017/11/21 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)