Backup to FTP will not resolve to URL addresses only IP addresses

[rjamesm2884]

Someone needs to find out why 3CX will not backup to URL address. I'm trying to backup to Wasabi cloud storage with their FTP address s3.wasabi.com and it fails to resolve the address, however if I point it the IP address of that URL it resolves and connects putting the backup at risk if they change their IP address. Can someone explain why 3CX is behaving this way? Is this bug?

 

[rjamesm2884]

This would suggest that I have resolved and reached the server since it replies with invalid credentials
View attachment 18978

Also this would suggest that you may be ending up on any given IP below, and I don't know that they are all serving FTP
View attachment 18979

So I'm not sure that there is any issue with your PBX here, you will have to look into the networking side of things, and WireShark is your friend

It replies back to you with invalid credentials because you don't have credentials. I have credentials and I have made sure my credentials work, I still believe we are not on the same page here, the problem is FQDN will not work if I use any given IP address from that NSLOOK list I can get in, if I use the server FQDN it will not work.

We are just going in circles with an issue that is being cause by 3CX and not the third party.

 

[JohnS_3CX]

If you like, you can send me some test credentials in a private message (for the same FQDN) and I can run a quick check from here too.

Wireshark will also show you what IP your PBX resolved, and which one it connected to. It can also reveal if something went wrong and the PBX never ended up connecting.

 

[rjamesm2884]

If you like, you can send me some test credentials in a private message (for the same FQDN) and I can run a quick check from here too.

Wireshark will also show you what IP your PBX resolved, and which one it connected to. It can also reveal if something went wrong and the PBX never ended up connecting.

John I replied to you in private for the username and password.
Thanks!

 

[JohnS_3CX]

After testing various scenarios, we did not find any issues with resolving the IP and connecting to your specific server, at least not with our test machines (cloud and local).

We did find a separate issue though, which update 7 already takes care of. So DNS resolution aside, you should be able to resume backups on your specific FTP server with update 7.

Just clarifying that this is has been recorded with the specific FTP server you use, but when using other servers for testing we did not come across such issues, and this appears to be and edge case so far.