FTP and outging mail from client problems

39 posts / 0 new
Last post
#1 Fri, 06/19/2009 - 10:55
recci

FTP and outging mail from client problems

As per the end of my DNS thread everything is working apart from two issues thanks to ronald.

The first issues is I cant connect to any of my virtual servers via ftp:

In virtualmin system information ProFTPd FTP Server is not running, when I try to enable it I get the following error:

Failed to start service :

  • Starting ftp server proftpd
  • warning: unable to determine IP address of 'ns1.flirtsnflings.com_'
  • error: no valid servers configured
  • Fatal: error processing configuration file '/etc/proftpd/proftpd.conf' ...fail!

I tired to edit the /etc/proftpd/proftpd.conf and remove the _ from the end of ns1.flirtsnflings.com but its not in that file.

The second issue is sending outgoing mail from thunderbird email client. I can receive mails but I cannot send them it just continually asks for the password even though i know its correct. I seen in the forums this issues has been mentioned before but I was unable to find the solution. Both sending and receiving os working fine from within usermin.

Fri, 06/19/2009 - 11:21
ronald
ronald's picture

as for the mail I think this may have to do with your TLS settings in thunderbird. I would disable them if they are enabled atm and enable them if they were disabled atm. And see how that goes.

ftp -> Joe, Eric?

oh and you can always use port 22 in your ftp client...

Fri, 06/19/2009 - 11:43
recci

Iv tired the mail on all setting still the same. . Whats the deal with ftp on port 22 again? that does seem to be working

Just to get one thing straight ProFTPd FTP Server is supposed to be running after a default installation of virtualmin using the install script correct?

Fri, 06/19/2009 - 11:55
ronald
ronald's picture

port 22 is the ssh server which is a secure way of logging into your server. You can use your ftpclient to upload files to your server. So its not proftp, but the ssh server (and is preferred actually)

proftp should be running on a default installation, but you had trouble with FQDN which may have messed up something which I can not find.

if you save passwords in thunderbird, try deleting it for joomlaplazza and empty the cache if there is such thing. I think somehow you got the wrong password in thunderbird. Or try another mailclient to test. evolution, mulberry etc.

Fri, 06/19/2009 - 13:17
ronald
ronald's picture

BTW in the documentation here: http://www.virtualmin.com/documentation/email/pop-and-imap

look at the bottom part contributed by a member. For thunderbird to login it needs ftp access as well and that's not working yet with you. Per haps the two are related...

Fri, 06/19/2009 - 16:52
recci

I found this thread where a guys is having the same problem but mine is worse because I cant even send when auth is off.

http://www.virtualmin.com/node/9441

He says something about enabling SMTPS and/or Submission in Postfix, so I enabled those and restarted postfix but no difference

Fri, 06/19/2009 - 18:19
Joe
Joe's picture

What are we talking about here? Mail or FTP? If mail, sending or receiving or both? (All different servers, all different protocols, and all have different troubleshooting steps and solutions.)

If mail, the maillog is where all answers will be found, so we'll want to see the relevant entries from the maillog.

--

Check out the forum guidelines!

Fri, 06/19/2009 - 18:28
recci

we are talking about mail and FTP as separate issues. But id like to deal with the FTP first

ProFTPd FTP is down and i get this error when i try to restart it

Failed to start service :

* Starting ftp server proftpd
* warning: unable to determine IP address of 'ns1.flirtsnflings.com_'
* error: no valid servers configured
* Fatal: error processing configuration file '/etc/proftpd/proftpd.conf' ...fail!

any ideas Joe?

Fri, 06/19/2009 - 19:05
Joe
Joe's picture
 * warning: unable to determine IP address of 'ns1.flirtsnflings.com_'

So this one means DNS still isn't setup right.

What do you get when you run:

host ns1.flirtsnflings.com

I get a reasonable response back when I look it up from my neck of the woods, but for some reason your system isn't able to look it up. Figuring out why is the first step.

--

Check out the forum guidelines!

Fri, 06/19/2009 - 19:10
recci

I get

ns1.flirtsnflings.com has address 94.76.201.163

which is fine but if you notice in the error message its ns1.flirtsnflings.com_ with an _ at the end of it, I dont know where the _ is coming from?

Fri, 06/19/2009 - 19:13 (Reply to #10)
Joe
Joe's picture

which is fine but if you notice in the error message its ns1.flirtsnflings.com_ with an _ at the end of it, I dont know where the _ is coming from?

Yeah, that's whack. Do you have a typo in your /etc/hosts file or in hostname?

--

Check out the forum guidelines!

Fri, 06/19/2009 - 19:16
recci

Na both /etc/hosts and /etc/hostname are fine. Was the first thing i checked(im learning ;)). Hence im stumped.

Fri, 06/19/2009 - 19:18 (Reply to #12)
Joe
Joe's picture

Try:

grep -R flirtsnflings.com_ /etc/*

See if maybe there's some configuration somewhere about that.

And, refresh my memory on what "hostname -f" returns?

--

Check out the forum guidelines!

Fri, 06/19/2009 - 19:21
recci
grep -R flirtsnflings.com_ /etc/*
/etc/apache2/sites-available/flirtsnflings.com.conf:ErrorLog /var/log/virtualmin                  /flirtsnflings.com_error_log
/etc/apache2/sites-available/flirtsnflings.com.conf:CustomLog /var/log/virtualmi                  n/flirtsnflings.com_access_log combined
/etc/apache2/sites-enabled/flirtsnflings.com.conf:ErrorLog /var/log/virtualmin/f                  lirtsnflings.com_error_log
/etc/apache2/sites-enabled/flirtsnflings.com.conf:CustomLog /var/log/virtualmin/                  flirtsnflings.com_access_log combined
/etc/awstats/awstats.flirtsnflings.com.conf:LogFile=/var/log/virtualmin/flirtsnf                  lings.com_access_log
/etc/awstats/awstats.www.flirtsnflings.com.conf:LogFile=/var/log/virtualmin/flir                  tsnflings.com_access_log
grep: /etc/fonts/conf.d/30-defoma.conf: No such file or directory
/etc/logrotate.conf:/var/log/virtualmin/flirtsnflings.com_access_log /var/log/vi                  rtualmin/flirtsnflings.com_error_log {
/etc/webmin/syslog/flirtsnflings.acl:extras=/var/log/virtualmin/flirtsnflings.co                  m_access_log Apache access log for flirtsnflings.com    /var/log/virtualmin/flir                  tsnflings.com_error_log Apache error log for flirtsnflings.com
/etc/webmin/webalizer/flirtsnflings.acl:dir=/var/log/virtualmin/flirtsnflings.co                  m_access_log
/etc/webmin/webalizer/var_log_virtualmin_flirtsnflings.com_access_log.conf:LogFi                  le /var/log/virtualmin/flirtsnflings.com_access_log
Fri, 06/19/2009 - 19:22
recci

hostname -f is returning:

hostname: Unknown host

Fri, 06/19/2009 - 19:27 (Reply to #15)
Joe
Joe's picture
hostname -f is returning:

hostname: Unknown host

What?!? That makes no sense.

What's in /etc/hosts?

--

Check out the forum guidelines!

Fri, 06/19/2009 - 19:32
recci
127.0.0.1       localhost.localdomain localhost
94.76.201.163   ns1.flirtsnflings.com ns1
94.76.201.164   ns2.flirtsnflings.com ns2
Fri, 06/19/2009 - 19:34 (Reply to #17)
Joe
Joe's picture

Looks right.

What's in the "hosts:" line in /etc/nsswitch.conf?

--

Check out the forum guidelines!

Fri, 06/19/2009 - 19:37
recci

passwd: compat

group: compat

shadow: compat

hosts: files dns

networks: files

protocols: db files

services: db files

ethers: db files

rpc: db files

netgroup: nis

Sat, 06/20/2009 - 04:51
ronald
ronald's picture

In my system FTP is running as nobody and is User:Group-> ftp:ftp

in your system it's running as ftp:nogroup. That may cause it as it may not have the correct permissions?

edit: If I recall you also made a virtual server or user called FTP .. You may want to get rid of it. And check the users:group module found under webmin

Sat, 06/20/2009 - 10:52 (Reply to #20)
Joe
Joe's picture

In my system FTP is running as nobody and is User:Group-> ftp:ftp

in your system it's running as ftp:nogroup. That may cause it as it may not have the correct permissions?

This one is a red herring. It's different on different operating systems. It's just different user and group names. The fundamentals of how they work is the same.

We'd want to see the secure.log and possibly and proftpd logs.

--

Check out the forum guidelines!

Sat, 06/20/2009 - 18:57
recci

I'm not aware of creating a virtual server or user called FTP.

Here are the proftpd logs.

Jun 16 01:52:49 mclaughlan.info proftpd[11551] parkwebwin-v01.prod.mesa1.secureserver.net: ProFTPD 1.3.1 (stable) (built Thu Feb 21 04:21:14 UTC 2008) standalone mode STARTUP
Jun 16 01:53:12 mclaughlan.info proftpd[11551] parkwebwin-v01.prod.mesa1.secureserver.net: ProFTPD killed (signal 15)
Jun 16 01:53:12 mclaughlan.info proftpd[11551] parkwebwin-v01.prod.mesa1.secureserver.net: ProFTPD 1.3.1 standalone mode SHUTDOWN
Jun 16 01:53:13 mclaughlan.info proftpd[13015] parkwebwin-v01.prod.mesa1.secureserver.net: ProFTPD 1.3.1 (stable) (built Thu Feb 21 04:21:14 UTC 2008) standalone mode STARTUP
Jun 16 04:11:34 mclaughlan.info proftpd[26556] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:95.154.210.61[::ffff:95.154.210.61]): FTP session opened.
Jun 16 04:11:34 mclaughlan.info proftpd[26557] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:95.154.210.61[::ffff:95.154.210.61]): FTP session opened.
Jun 16 04:11:35 mclaughlan.info proftpd[26557] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:95.154.210.61[::ffff:95.154.210.61]): FTP session closed.
Jun 16 04:11:35 mclaughlan.info proftpd[26556] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:95.154.210.61[::ffff:95.154.210.61]): FTP session closed.
Jun 16 05:00:17 mclaughlan.info proftpd[27388] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:77.240.118.43[::ffff:77.240.118.43]): FTP session opened.
Jun 16 05:00:17 mclaughlan.info proftpd[27388] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:77.240.118.43[::ffff:77.240.118.43]): FTP session closed.
Jun 16 05:00:17 mclaughlan.info proftpd[27389] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:77.240.118.43[::ffff:77.240.118.43]): FTP session opened.
Jun 16 05:00:17 mclaughlan.info proftpd[27389] parkwebwin-v01.prod.mesa1.secureserver.net (::ffff:77.240.118.43[::ffff:77.240.118.43]): FTP session closed.
Jun 16 21:54:30 mclaughlan.info proftpd[25801] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session opened.
Jun 16 21:54:30 mclaughlan.info proftpd[25801] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): USER admin: Login successful.
Jun 16 21:55:43 mclaughlan.info proftpd[25801] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session closed.
Jun 16 21:55:53 mclaughlan.info proftpd[25822] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session opened.
Jun 16 21:55:53 mclaughlan.info proftpd[25822] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): USER admin: Login successful.
Jun 16 21:56:42 mclaughlan.info proftpd[25822] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session closed.
Jun 16 21:56:52 mclaughlan.info proftpd[25823] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session opened.
Jun 16 21:56:52 mclaughlan.info proftpd[25823] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): SECURITY VIOLATION: root login attempted.
Jun 16 21:56:52 mclaughlan.info proftpd[25823] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session closed.
Jun 16 22:20:55 mclaughlan.info proftpd[26231] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session opened.
Jun 16 22:20:55 mclaughlan.info proftpd[26231] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): USER admin: Login successful.
Jun 16 22:21:40 mclaughlan.info proftpd[26232] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session opened.
Jun 16 22:21:40 mclaughlan.info proftpd[26232] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): USER admin: Login successful.
Jun 16 22:24:00 mclaughlan.info proftpd[26231] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session closed.
Jun 16 22:31:43 mclaughlan.info proftpd[26232] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP no transfer timeout, disconnected
Jun 16 22:31:43 mclaughlan.info proftpd[26232] parkwebwin-v01.prod.mesa1.secureserver.net (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session closed.
Jun 17 00:51:11 mclaughlan.info proftpd[30050] parkwebwin-v01.prod.mesa1.secureserver.net (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session opened.
Jun 17 00:51:11 mclaughlan.info proftpd[30051] parkwebwin-v01.prod.mesa1.secureserver.net (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session opened.
Jun 17 00:51:11 mclaughlan.info proftpd[30050] parkwebwin-v01.prod.mesa1.secureserver.net (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session closed.
Jun 17 00:51:11 mclaughlan.info proftpd[30051] parkwebwin-v01.prod.mesa1.secureserver.net (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session closed.
Jun 17 03:54:03 mclaughlan.info proftpd[13015] parkwebwin-v01.prod.mesa1.secureserver.net: ProFTPD killed (signal 15)
Jun 17 03:54:03 mclaughlan.info proftpd[13015] parkwebwin-v01.prod.mesa1.secureserver.net: ProFTPD 1.3.1 standalone mode SHUTDOWN
Jun 17 20:19:08 ns1.flirtsnflings.com proftpd[1667] 94.76.201.163: ProFTPD 1.3.1 (stable) (built Thu Feb 21 04:21:14 UTC 2008) standalone mode STARTUP
Jun 17 22:30:32 ns1.flirtsnflings.com proftpd[1667] 94.76.201.163: ProFTPD killed (signal 15)
Jun 17 22:30:32 ns1.flirtsnflings.com proftpd[1667] 94.76.201.163: ProFTPD 1.3.1 standalone mode SHUTDOWN
Jun 17 22:33:20 ns1.flirtsnflings.com proftpd[1664] ns1.flirtsnflings.com: ProFTPD 1.3.1 (stable) (built Thu Feb 21 04:21:14 UTC 2008) standalone mode STARTUP
Jun 17 22:46:25 ns1.flirtsnflings.com proftpd[1664] ns1.flirtsnflings.com: ProFTPD killed (signal 15)
Jun 17 22:46:25 ns1.flirtsnflings.com proftpd[1664] ns1.flirtsnflings.com: ProFTPD 1.3.1 standalone mode SHUTDOWN
Jun 17 22:49:22 ns1.flirtsnflings.com proftpd[1692] ns1.flirtsnflings.com: ProFTPD 1.3.1 (stable) (built Thu Feb 21 04:21:14 UTC 2008) standalone mode STARTUP
Jun 18 06:43:07 ns1.flirtsnflings.com proftpd[18012] ns1.flirtsnflings.com (::ffff:78.111.76.119[::ffff:78.111.76.119]): FTP session opened.
Jun 18 06:43:07 ns1.flirtsnflings.com proftpd[18013] ns1.flirtsnflings.com (::ffff:78.111.76.119[::ffff:78.111.76.119]): FTP session opened.
Jun 18 06:43:08 ns1.flirtsnflings.com proftpd[18012] ns1.flirtsnflings.com (::ffff:78.111.76.119[::ffff:78.111.76.119]): FTP session closed.
Jun 18 06:43:08 ns1.flirtsnflings.com proftpd[18013] ns1.flirtsnflings.com (::ffff:78.111.76.119[::ffff:78.111.76.119]): FTP session closed.
Jun 18 11:03:33 ns1.flirtsnflings.com proftpd[28045] ns1.flirtsnflings.com (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session opened.
Jun 18 11:03:33 ns1.flirtsnflings.com proftpd[28044] ns1.flirtsnflings.com (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session opened.
Jun 18 11:03:33 ns1.flirtsnflings.com proftpd[28045] ns1.flirtsnflings.com (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session closed.
Jun 18 11:03:33 ns1.flirtsnflings.com proftpd[28044] ns1.flirtsnflings.com (s15313712.onlinehome-server.info[::ffff:87.106.54.138]): FTP session closed.
Jun 18 16:42:26 ns1.flirtsnflings.com proftpd[9844] ns1.flirtsnflings.com (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session opened.
Jun 18 16:42:26 ns1.flirtsnflings.com proftpd[9844] ns1.flirtsnflings.com (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): USER joomlaplazza: Login successful.
Jun 18 16:53:07 ns1.flirtsnflings.com proftpd[9844] ns1.flirtsnflings.com (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP no transfer timeout, disconnected
Jun 18 16:53:07 ns1.flirtsnflings.com proftpd[9844] ns1.flirtsnflings.com (82-41-170-249.cable.ubr03.linl.blueyonder.co.uk[::ffff:82.41.170.249]): FTP session closed.
Jun 18 18:54:27 ns1.flirtsnflings.com proftpd[13350] ns1.flirtsnflings.com (ip217-46-212-87.adsl2.static.versatel.nl[::ffff:87.212.46.217]): FTP session opened.
Jun 18 18:54:27 ns1.flirtsnflings.com proftpd[13350] ns1.flirtsnflings.com (ip217-46-212-87.adsl2.static.versatel.nl[::ffff:87.212.46.217]): FTP session closed.
Jun 18 23:13:13 ns1.flirtsnflings.com proftpd[1692] ns1.flirtsnflings.com: ProFTPD killed (signal 15)
Jun 18 23:13:13 ns1.flirtsnflings.com proftpd[1692] ns1.flirtsnflings.com: ProFTPD 1.3.1 standalone mode SHUTDOWN

Sat, 06/20/2009 - 19:07
recci

cant find secure.log its not in /var/log/ that I see.

Sat, 06/20/2009 - 19:36 (Reply to #23)
andreychek

If you're using Debian or Ubuntu, you may need to take a peek in /var/log/auth.log and /var/log/syslog, as they don't use a logfile named "secure" by default. -Eric

Sat, 06/20/2009 - 20:08
recci

I dont think I want to post them openly on the forum as I can see from those logs Iv already been the victim of several attacks on the server with people trying to login with a lot of usernames and ports ect..

what should I be looking for in the log files.

Sun, 06/21/2009 - 14:49 (Reply to #25)
andreychek

What should you be looking for? Anything unusual ;-)

I guess I'd try both starting up and connecting to FTP, and looking for messages in the logs that may relate to the problem you're having.

Sorry, the problem could be anything, so it's hard to say what specifically to look for :-) -Eric

Sun, 06/21/2009 - 17:02
recci

But that's problem FTP wont start up. So surly trying to connect to FTP will just show as trying to connect to unknown service or something like that and Iv very little idea what most of the log entries mean so I wouldn't know what's unusual and whats not, Id need something specific to look for that might identify why proftp wont start!

Sun, 06/21/2009 - 22:10 (Reply to #27)
andreychek

Sure, then what you'd do is try launching FTP, and when it doesn't work, it should immediately dump some info into the logs.

Unfortunately, the problem could be anything -- so the best info I can offer is that look right after you try launching FTP, and hopefully you'll see something odd in there, perhaps relating to FTP :-) -Eric

Wed, 06/24/2009 - 10:35
recci

Still struggling with this issue! cant find anything dumped in the logs when it fails.

Is ununstalling and reinstalling proftp an option?

Thu, 06/25/2009 - 20:22 (Reply to #29)
Joe
Joe's picture

Is ununstalling and reinstalling proftp an option?

What useful thing would you expect that to do? (That's my snarky way of saying, "I don't think uninstalling and reinstalling is a useful use of your time".) ;-)

That, of course, assumes you have a non-broken ProFTPd package. There are a number of broken proftpd packages in various third party repos for CentOS. If you have one of those, then you'd want to switch to ours which is known to work or the EPEL package (which I'm pretty sure also works).

--

Check out the forum guidelines!

Wed, 06/24/2009 - 16:37
ronald
ronald's picture

I would say yes, but then you may not know what the issue was and might appear again after reinstallation. I may be able to have a look on friday or per haps Eric/Joe want to free up some time.

Wed, 06/24/2009 - 21:34
recci

I tried to uninstall via the command line but it said the entire virtualmin tree would have to be removed. Is there a way to uninstall it from within virtualmin/webmin?

Thu, 06/25/2009 - 14:24
ronald
ronald's picture

i think you can do with the --nodeps but joe/eric would know the exact way of removing proftp

Thu, 06/25/2009 - 14:34
andreychek

Yeah, how to remove it would depend on the distro -- I'm not sure I see which one we're working with in the thread above.

It baffles me that this is happening at all though, I'm a bit suspicious that it's a configuration issue outside of ProFTP.

In your first post, you mention a series of errors that pop up -- I know you've attempted to correct some/all of those. So at this point, when you're launching ProFTP, do any errors at all show up? -Eric

Thu, 06/25/2009 - 14:55
ronald
ronald's picture

hi eric it's a VPS that's got Ubuntu 8.10 installed and has two ip addresses. I logged in once to fix the dns issues/hostname/networking, this all works fine afaik.

then there was a postfix issue which I fix by commenting #myorigin

I noticed then that ftp wouldn't start and it complains it can not find a hostname. Per haps it is listening on the wrong IP for that hostname. No other errors show up

If it was my vps to play around with I would contemplate on reimageing it with centos and reinstall virtualmin. Initially the errors seemed due to not having a FQDN so I guess a lot of stuff has errors unknown at this time.

Im not sure were to look for with proftp and once it is fixed there may be other errors turning up later.

edit: intodns.com gives perfect results on the fqdn.

Fri, 06/26/2009 - 08:46
recci

It seems to have sorted itself out now!

I noticed an update package for SSH was available via virtualmin so I installed it and rebooted the server and now the proftp issues has gone..weird!

Fri, 06/26/2009 - 09:09
ronald
ronald's picture

that is good news. likely the reboot fixed whatever was wrong with proftp.

Sat, 06/27/2009 - 16:19
recci

I had tried rebooting before but it made no difference so dunno, as long as its working now.

Sat, 06/27/2009 - 18:28
recci

actually just noticed that it changed my hostname back to the default name. But only the hostname it did'nt seem to alter any of the other settings we setup thankfully.

Topic locked