Is there any trick to get the FTP Server to work properly with Mac FTP clients? Everything seems to work fine under direct command line, but I can't get modern or vintage Mac FTP clients to work with it.

With a modern FTP client like Cyberduck, I get a "250 Working directory is now "/". Please contact your web hosting service provider for assistance." error once I get connected. On the server side, it shows me connected and logged in.

With a vintage FTP client like Fetch, I can connect to the root directory but it errors out when changing directories. On the server side it appears to change directories and list the files but it just stalls out on the client side.

Thanks,

Todd

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

With a vintage FTP client like Fetch, I can connect to the root directory but it errors out when changing directories. On the server side it appears to change directories and list the files but it just stalls out on the client side.

This can be an active vs passive mode issue.

If the ftp server wants passive mode but your client is in active mode that can happen. I can sometimes get past this in my classic ftp client by going into passive mode before doing a dir command. Try just entering "passive" without the quotes on the ftp command line before issueing any other commands like dir.

ftp is kind of a cranky protocol, that may or may not help but it's worth a try.

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.3)

With a vintage FTP client like Fetch, I can connect to the root
directory but it errors out when changing directories. On the server
side it appears to change directories and list the files but it just stalls out on the client side.

I would say first make sure the Mystic you are using isn't using an old
version of Mystic. Latest version is today.

... Kids: They're not sleeping, they're recharging!

--- Mystic BBS v1.12 A47 2021/07/31 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On Tuesday, August 3, 2021 at 4:20:18 PM UTC-5, Al wrote:

This can be an active vs passive mode issue.

If the ftp server wants passive mode but your client is in active mode that can
happen. I can sometimes get past this in my classic ftp client by going into passive mode before doing a dir command. Try just entering "passive" without the quotes on the ftp command line before issueing any other commands like dir.

ftp is kind of a cranky protocol, that may or may not help but it's worth a try.

Thanks for the reply. Everything works fine from modern command line, but the vintage Fetch app doesn't allow you to enter any commands. I'm guessing the old app doesn't support passive mode so I tried switching the Passive Mode to "No" in the FTP
server settings without any luck...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Wednesday, August 4, 2021 at 11:20:13 AM UTC-5, g00r00 wrote:

I would say first make sure the Mystic you are using isn't using an old version of Mystic. Latest version is today.

I'm using Version 1.12 A46.
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Thanks for the reply. Everything works fine from modern command line,
but the vintage Fetch app doesn't allow you to enter any commands. I'm guessing the old app doesn't support passive mode so I tried switching
the Passive Mode to "No" in the FTP
server settings without any luck...

Another thing to do is make sure you have your BBS domain set correctly in System Configuration > Servers > General Options > Domain Name

The FTP server may require this domain to resolve your IP address so it should be set to your BBS domain name.

... This virus requires Microsoft Windows 3.x

--- Mystic BBS v1.12 A47 2021/07/31 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On Friday, August 6, 2021 at 12:20:24 AM UTC-5, g00r00 wrote:

Another thing to do is make sure you have your BBS domain set correctly in System Configuration > Servers > General Options > Domain Name

The FTP server may require this domain to resolve your IP address so it should
be set to your BBS domain name.

It is, but I'm just testing this out on my local network by ftp'ing directly to the IP address. Would this make a difference?

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Ok, I was able to get things working locally by turning passive mode off on the server and using a faster vintage client computer.

I can't get it to connect over the internet at all though. Is there a trick to the FTP port forwarding? I tried to port forward ports 20 & 21 (for active mode) without any luck...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

I can't get it to connect over the internet at all though. Is there a trick to the FTP port forwarding? I tried to port forward ports 20 & 21 (for active mode) without any luck...

If you have a firewall which I assume most do then for passive mode you have to open a range of ports to allow incoming connections. For example if you allow 10 incoming connections on your FTP server then you would need to open up 10 ports. The starting port range by default is 60000 (configurable in FTP server settings) and Mystic will use that starting port + the number of incoming connections as the ports for passive FTP. If you have 10 incoming connections configured you'd need to open ports 60000-60009 in your firewall for incoming connections.

... Error 3032 - Recursion error. See error 3032.

--- Mystic BBS v1.12 A47 2021/08/07 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)