Oh I thought your problem was with the data connection. If the only difference is the internal IP, it might be the that internal ip you set is incorrect( or, at least, it is not the ip to which you are trying to connect with Filezilla). Besides enabling logging in the server side you can use standard OS commands to check if your server is listening (netstat -an, telnet from local host etc.) El 09/06/2015 16:03, "Martin Wunderlich" <m...@censhare.de> escribió:
> This is the log output I get when I set the log level to Debug: > (the contents are identical in the console and the log file) > > 16:01:50 Status: Disconnected from server > 16:01:50 Trace: CControlSocket::DoClose(64) > 16:01:50 Trace: CControlSocket::DoClose(64) > 16:01:50 Trace: CControlSocket::DoClose(64) > 16:01:50 Trace: CFileZillaEnginePrivate::ResetOperation(0) > 16:01:50 Status: Resolving address of example.com > 16:01:50 Status: Connecting to 123.123.123.123:4243... > 16:01:50 Status: Connection attempt failed with "ECONNREFUSED - > Connection refused by server". > 16:01:50 Trace: CRealControlSocket::OnClose(61) > 16:01:50 Trace: CControlSocket::DoClose(64) > 16:01:50 Trace: CFtpControlSocket::ResetOperation(66) > 16:01:50 Trace: CControlSocket::ResetOperation(66) > 16:01:50 Error: Could not connect to server > 16:01:50 Trace: CFileZillaEnginePrivate::ResetOperation(66) > > Cheers, > > Martin > > > > Am 09.06.2015 um 15:47 schrieb David Latorre <dvl...@gmail.com>: > > > > Probably the full Filezilla log file will be enough > > El 09/06/2015 15:46, "Martin Wunderlich" <m...@censhare.de> escribió: > > > >> Hi David, > >> > >> There isn’t much in the log files, I am afraid. This is what I get with > >> Filezilla on the client side: > >> > >> 15:44:30 Status: Resolving address of exmample.com > >> 15:44:30 Status: Connecting to 123.123.123.123:4243... > >> 15:44:30 Status: Connection attempt failed with "ECONNREFUSED - > >> Connection refused by server". > >> 15:44:30 Error: Could not connect to server > >> > >> There is nothing logged on the server side. Sorry, not much help, I > know. > >> > >> Cheers, > >> > >> Martin > >> > >> > >> > >> > >>> Am 09.06.2015 um 15:36 schrieb David Latorre <dvl...@gmail.com>: > >>> > >>> Martin, > >>> > >>> Can you include the log file (with the messages which have been > received > >>> and sent) of the Ftp server? Also, the log file of the ftp client > >> would > >>> be helpful > >>> El 09/06/2015 15:25, "Martin Wunderlich" <m...@censhare.de> escribió: > >>> > >>>> No, in the client I set the external IP address, because the server is > >>>> accessed from outside the firewall. This external IP address is also > >>>> configured on the server-side, of course. > >>>> > >>>> Cheers, > >>>> > >>>> Martin > >>>> > >>>> > >>>>> Am 09.06.2015 um 15:18 schrieb Alessio Santacroce < > >>>> alessio.santacr...@gmail.com>: > >>>>> > >>>>> Stupid question... > >>>>> when you set the ip to the ftp server, do you use the same ip on the > >> ftp > >>>>> client as well? > >>>>> > >>>>> On Tuesday, June 9, 2015, Martin Wunderlich <m...@censhare.de> > wrote: > >>>>> > >>>>>> Hi all, > >>>>>> > >>>>>> We observed some strange behavior that I can’t quite explain: Our > FTP > >>>>>> server is running in passive mode and offering a listener for FTP > over > >>>> TLS. > >>>>>> When the internal IP address is set in the configuration, I am not > >> able > >>>> to > >>>>>> connect with the FTP client (tested with both Filezilla and > >> Cyberbuck). > >>>> The > >>>>>> error „Connection refused“ is raised when trying to connect. > However, > >>>> when > >>>>>> the internal IP address is set to „0.0.0.0“, the connection is > fine. I > >>>> have > >>>>>> stepped through the code and the listener seems to be instantiated > >>>> alright. > >>>>>> So, what could be the problem? > >>>>>> > >>>>>> Cheers, > >>>>>> > >>>>>> Martin > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> censhare featured as Cool Vendor for Content Management by Gartner > >>>>>> > >>>> > >>>> > >>>> > >>>> censhare featured as Cool Vendor for Content Management by Gartner > >>>> > >> > >> > >> > >> censhare featured as Cool Vendor for Content Management by Gartner > >> > > > > censhare featured as Cool Vendor for Content Management by Gartner >
