Problem With Backup Over FTP
Hello
I am having a strange issue with backups over FTP. My business has a few cpanel servers, two of them are online dedicated servers and the other two are internal development servers running on VMWare vSphere (hypervisor) as virtual machines.
Internally we also have a Windows Server 2016 VM on vSphere which we use as a file /backup server running FileZilla server.
All of these servers are connected to their own public and private static ips. So for example cpanel server one might have internal of 192.168.1.5 and external of 88.111.333.222 (not a real Ip) and then they are mapped together on the router (at the moment we're using a crappy BT Business HUB 6 [smart hub] but will be upgrading).
The two online dedicated servers have no problem with the ftp transfer of the backups, they both connect to the internal office windows server on FileZilla no problems but for some reason the two internal ones on the same network as the windows backup server can't seem to connect to the ftp at all. I have also tested the connection myself manually in FileZilla client and I can connect and upload files no problem. Please note that I don't have passive ports setup so using active mode at the moment.
I'm wondering if there is a common / known issue with this? It doesn't make sense why the internal cpanel servers can't connect to the ftp on the same network but the external servers can.
The transporter log has lots of lines saying this:
[2018-11-04 00:38:50 +0000] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2018-11-04 00:38:50 +0000] info [cpbackup_transporter] cpbackup_transporter - Waiting up to 0s for new tasks
And then followed by:
[2018-11-04 00:38:51 +0000] info [cpbackup_transporter] cpbackup_transporter - Exiting - the queue has been emptied; no more work to do after waiting for 300s
[2018-11-04 00:38:51 +0000] info [cpbackup_transporter] cPanel Backup Transporter Queue Daemon is being stopped.
When I try to use the Verify destination in WHM it just times out.
-
I've fixed it by enabling passive ports - :) 0 -
Hi @glenelkins1984 I'm happy to see you were able to identify the cause of the issue and thank you very much for updating the thread with the solution that worked for you! 0
Please sign in to leave a comment.
Comments
2 comments