FTP Login Problem after Backup restoring....

[TrippleEx]

Hi,

i reinstall my Rootserver and install a fresh version of ispCP.
Befor i do this, i download the vHost Backup to my local machine.
After the installation i upload the both Backup via FTP to the Backupfolder. I give both Files chmod 650.

After restoring User Backups over ispCP "Restor Backup", user can't loggin with their FTP Account now.

I try change the FTP Account Password, and i try readding a new FTP Account, but nothin change, the user can't login.!!!!

Iam looking via SSH to the /vhost/../htdocs/ Folder, and checkup the mySQL Tables via myphpAdmin, the files ind Folder and tables in the DB are avalible. But there is Blank Page (on .php) the .html works.

Server:
Debian Etch 4, with ispCP 1.0.0 rc4.
http://www.kocubaba.com/index.htm --> works
http://www.kocubaba.com/portal.php --> didn't work

What is worng...???

[kilburn]

Regarding the failed FTP login, are there any messages on the proftpd log? Paste them here please.

On the php side, I see a "No input file" message on your page so something is going on, maybe your script needs an unexistant file?

[TrippleEx]

kilburn Wrote:Regarding the failed FTP login, are there any messages on the proftpd log? Paste them here please.

On the php side, I see a "No input file" message on your page so something is going on, maybe your script needs an unexistant file?

No there no Messages in the log:

Quote:May 14 19:03:13 ulucom.de proftpd[5752] ulucom.de: error setting IPV6_V6ONLY: Protocol not available
May 14 19:03:13 ulucom.de proftpd[5752] ulucom.de: ProFTPD 1.3.0 (stable) (built mar gen 2 10:57:47 CET 2007) standalone mode STARTUP
May 14 19:25:48 ulucom.de proftpd[5752] ulucom.de: ProFTPD killed (signal 15)
May 14 19:25:48 ulucom.de proftpd[5752] ulucom.de: ProFTPD 1.3.0 standalone mode SHUTDOWN

What you mean with "unexistant file" ?[/quote]

[kilburn]

Try to connect and then do a "grep proftpd /var/log/syslog" to see the actual messages, paste here

AFAIK the message "No input file" is not a standard php/apache error, so it must be an error generated by your php script so I'm afraid that I can't further diagnose this...

EDIT: Well, I don't know everything! See this