Personal FTP Repository - Transport error

[VojkanC]

When I try to set up Personal FTP Repository I get this error message:
Transport error: unable to list directory: Curl error: Couldn't resolve host name

I am pretty sure that my server address, user name and password are correct.
Can someone please explain why am I getting this error message?

Please take a look at attached screen-shot for more information.

 

[IgorG]

Do you have the same error when you specify IP address instead of hostname?

 

[VojkanC]

Hi Igor, Thank you for your answer.
Yes I tried to specify IP address instead of hostname and it doesn't work either.
Also, I cannot connect from command line in CentOS (Connection time out).

It seems that more than a few strange things happen:
- postfix stoped working so I had to transfer to Qmail (you can read more about it here),
- domain gets suspended and cannot be activated from Plesk, but only from command line,
- when I activate problematic domain from command line before "completed successfully" I get some info about Postfix not working, but I uninstalled Postfix and Installed Qmail, so I don't know why is that happening.

Can you please advise me if and how this VPS is worth fighting for or I should rent another VPS and transfer all domains and data there?

 

[IgorG]

It is difficult to say what is wrong there without deep investigation directly on your server. Maybe there is lack of VPS resources, maybe corrupted VPS filesystem, maybe some misconfiguration, maybe something else. Have you asked help of Support Team?

 

[UFHH01]

Hi VojkanC,

... did you try as well to use the "passive mode" and no "FTPS"? ... your VPS-hosting might not include these optrions. Please consider to include log - files for further investigations and you have as well the possibility to define another log - level for the Plesk Control Panel, or for other services on your server, which could lead to a better output of possible issues/problems and failures.

Odin / Parallels Plesk Panel for Linux services logs and configuration files ( KB - article: 111 283 )​

 

[trialotto]

@VojkanC,

This

Transport error: unable to list directory: Curl error: Couldn't resolve host name

is very likely to be related to the remote FTP server not supporting passive and/or FTPS mode, i.e. the remote FTP only allows plain FTP.

Having unchecked the "passive mode" and "FTPS" checkboxes, the FTP issue should be resolved.

A request: when testing the setup of the FTP Repository, please log in with SSH and run "ps aux | grep passive". It should contain nothing, otherwise post the output, please.

If the FTP issue is not resolved AND you are managing the remote server, THEN try to create a passive port configuration of proftpd on the remote server.

Have a look at: http://talk.plesk.com/threads/tips-...tp-with-tls-and-ftp-backup-repository.332166/

This

It seems that more than a few strange things happen:
- postfix stoped working so I had to transfer to Qmail (you can read more about it here),
- domain gets suspended and cannot be activated from Plesk, but only from command line,
- when I activate problematic domain from command line before "completed successfully" I get some info about Postfix not working, but I uninstalled Postfix and Installed Qmail, so I don't know why is that happening.

is very likely to be related to the issue of insufficient disk space.

In the light of the above, note that cleaning up a small amount of disk space (as indicated in your other post) will not be sufficient: mail servers will retry delivery for undelivered mails, implying that the free space will be filled up fast.

However, this should not be the only explanation, given the facts that you (in your other post) gave hints that network resources (i.e. causing timeouts) and computer resources (i.e. causing failures when starting programs) are not used properly.

In order to investigate your problem in more detail:

a) go to Server Management > Tools & Settings > Mail Server Settings and have a look under the tab "Mail Queue": delete messages (note: you can delete all, if they are not spam, most of the relevant messages will be redelivered),

b) log in with SSH and run "ps aux" in order to view all processes (note: try to see whether some double processes are present) OR run "top" (note: try to find all processes that consume a lot of memory or cpu resources),

c) run "service psa stop" AND kill any double processes and resource exhaustive processes,

d) run "service psa start" and (if necessary) "service drwebd start"

e) check again, whether the VPS does run properly and efficiently

Hope the above helps a little bit.

In addition to the above, it should be noted that you are very likely better off with

- less backups on the VPS itself (note: use a remote FTP Repository AND reduce the number of local backups)
- a VPS with a bigger disk and more compute power.

Kind regards......

 

[VojkanC]

Thank you everyone for your kind posts.
FTP stopped working even with other FTP servers that support both active and passive mode (so it wasn't up to passive mode).
Also, I deleted dump files and some data from domains and freed 80GB of space but problems were still there.

After few days of troubleshooting I had to fix the issue asap so I deleted the whole VPS and installed new one.
Then I tried to restore a backup, but it had the same problems as before (I've tried this 4 times with different settings, with and without restoring server configuration).
Finally, I've decided to delete VPS again, install new one and manually upload and configure everything.