Topic: Can't connect to SME11 server using Filezilla

[wdepot]

I'm trying to connect to my newly created SME11 server using Filezilla from my Windows computer which is on the same local network and keep getting a Connection closed by server error. I've checked the remote access settings on the server in Smanager and both SSH and FTP are set to allow access from only local networks with FTP accepting passwords from only local networks. I've also double checked the local network setting and it is correct and adding this network in remote access doesn't fix the problem. Does anyone have an idea of what might be going on? I've never had this problem under SME10. And I do have Filezilla using the IP address of the server directly.

I just checked and I have no problem accessing the SME11 server from my Windows machine using Putty.

[ReetP]

Your logs probably hold the answer.

Have a look. Or bug it.

[Jean-Philippe Pialasse]

https://wiki.koozali.org/Ftp

with sme11 no more insecure plain text password exchange.

we use explicit encryption, not implicit.

ftpes:// is mandatory. 

also depending on your network setting you need to open passive ports

[wdepot]

https://wiki.koozali.org/Ftp

with sme11 no more insecure plain text password exchange.

we use explicit encryption, not implicit.

ftpes:// is mandatory. 

also depending on your network setting you need to open passive ports

Thanks for the help. After switching Filezilla to SFTP mode I can access the test server using the root login and see anything I need to. Normally I only use this mode when I need to create a custom template on the server since files are created with the ownership root:root.

Under SME10 I used admin login in Filezilla for working with files in the ibays since that sets file ownership as admin:shared which seems to be needed to make them usable from a web browser. However on the SME11 test server I still cannot log in as admin. SFTP does not work when connecting admin so I switched Filezilla back to FTP and changed "Use explicit FTP over TLS if Available" to "Require explicit FTP over TLS". Still no luck. I've tried changing the transfer settings in Filezilla from Default to both Active and Passive and neither mode is allowing a connection from admin.

Based on the page about FTP that you pointed me to I downloaded the /etc/proftpd.conf file and took a look at that first and compared it to the same file from SME10. I noticed that PassivePorts is a new entry for SME11. I then downloaded the templates that create the proftpd.conf file from the test server and found the fragment that creates the PassivePorts line, noticing that it pulls the value from the TCPPorts property of the ftp configuration (not TcpPorts as shown in the documentation). Based on that I did the following:

Code: [Select]

config setprop ftp TCPPorts 21:49200:49999
signal-event post-upgrade; signal-event rebootAfter the test server restarted I again tried connecting Filezilla as admin and was still unable to connect to the test server.
The proftpd.log file on the test server contains this after the failed attempt:

Code: [Select]

Apr 21 15:25:27 www proftpd[2365]: tcpsvd: info: status 0/40

Apr 21 15:25:32 www proftpd[2365]: tcpsvd: info: status 1/40

Apr 21 15:25:32 www proftpd[4173]: tcpsvd: info: pid 4173 from 10.0.3.246

Apr 21 15:25:32 www proftpd[4173]: tcpsvd: info: concurrency 4173 10.0.3.246 1/4

Apr 21 15:25:32 www proftpd[4173]: tcpsvd: info: deny 4173 www.test.local:10.0.3.234 ::10.0.3.246:55528 ./peers/0

Apr 21 15:25:32 www proftpd[2365]: tcpsvd: info: end 4173 exit 100

I checked the proftpd.conf file again and discovered that the PassivePorts line looked like this:

Code: [Select]

PassivePorts             21 49200:49999I'm guessing this should probably be bug reported since I would think that all colons should have been converted to spaces when the template was expanded.

Anyone have any further thoughts on what I might need to set up to connect to the SME11 server using Filezilla while logging in as admin?

[ReetP]

Under SME10 I used admin login

Please be aware things change. A lot of security defaults have been updated. Ssh, httpd etc etc.

Things don't always stay the same.

I'm guessing this should probably be bug

As we have said many times previously.... If it doesn't work as expected open a bug.

Your admin issue may be a bug.

But regarding ports, rather than guessing you should search the wiki for TCPports to see the syntax:

https://wiki.koozali.org/Firewall

So like this:

Code: [Select]

TCPPorts 21,49200:49999
However, changing ports won't affect your admin login and I'm not sure what makes you think it would - it clearly works with root by default so it isn't ports.

You are creating your own XY problem here.

Please just open an issue for 'ftp admin login not permitted' or similar rather than trying to blindly hack your way to a solution to an issue that may be insoluble.

Thanks.

[wdepot]

Just a follow up. After returning the ftp configuration variables to the defaults I decided to try changing the remote access settings for the test server in Smanager for FTP to allow access from anywhere and allow passwords from anywhere. This allowed Filezilla to connect to the test server using the admin user. I would definitely not use those setting for any computer that was directly connected to the internet so I will be raising a bug since there is obviously a problem somewhere in SME11Beta.

I also decided to test FTP allowed from local network only with FTP passwords accepted anywhere and was unable to connect Filezilla. However when I tried allowing FTP from anywhere but FTP passwords from only the local network the connection works. I would say there is a bug somewhere in the current SME11 FTP that has a problem with the local network setting.

[ReetP]

Bug:

https://bugs.koozali.org/show_bug.cgi?id=13511

Follow up there please.