Cumulus Support

My ISP sent me a new router which seems to work, however since it was installed Cumulus reports various Connection refused messages.
I am using the plain old FTP to upload.
I have turned off the router's Filewall but this didn't help.
Filezilla also confirms the web uploads are not getting through to my server.

Help is much appreciated.

Thanks

It almost looks like the server isn't accepting passive connections (which is why the connection port is in the 63000 range; that's where the passive ports are).

Can you try using SFTP instead? I'm not sure if Cumulus has an option for passive FTP (I've never tried it) and not sure it would even matter.

Just a thought.

Thanks, I've tried using SFP and get similar messages like connection refused.
So no further forward.

With both FTPS and SFTP you have to have valid user and a password. You don't say what version you are on but have you tried the new PHP upload, works well and is fast.

Hi,
I don't know much about FTP but have learned the file and paths must be correct. Your MXdiags shows: so presume your FTP settings for Remote FTP Directory: is /public_html.
Try it without the / slash so just public_html as that is what I have.

Enjoy,
Paul

water01
I have been using the plain old FTP to upload and worked for many years.
Would like the system to work 100% before trying the new PHP upload. I read somewhere that not all hosting companies currently allow it.
I do have a valid user name and password. I can access the web server using Filezilla but the upload files are not getting in.
I am using Cumulus v3.25.1 (b3244)

Paul
You are correct my FTP settings for Remote FTP Directory: is /public_html
I have tried removing the / just leaving public_html and again Connection refused with various port numbers shown.

This problem only started after I replaced my router provided by my ISP so perhaps thats where where the issue is. Unfortunately I cannot put back the old router as its 'settings' at their end has been removed.

If you can connect to your site using FileZilla from the same network then your router is unlikely to be the problem - provided you are using FTP in FileZilla too.

If FileZilla works then I would check the settings you use in that program and duplicate them in CumulusMX.

I would definitely ensure your router firewall is never left switched off.

Dennisdg wrote: ↑Sun 28 May 2023 3:58 pm This problem only started after I replaced my router provided by my ISP so perhaps thats where where the issue is. Unfortunately I cannot put back the old router as its 'settings' at their end has been removed.

Some routers have intelligent support for some applications like ftp, and they adjust their firewall, nat and portforwarding automatically without user even knowing about it. I would guess it seems that the new one is not so smart as the old one was, or the feature is just disabled on the new one. Look for application layer gateway (alg) or nat passthrough for ftp or something similar.

But at first you could try change your Cumulus settings to use passive ftp instead of active. The settings are hidden under internet settings - web/upload site - advanced settings. Check that Enable active ftp(s) is not selected. Also enable automatic connection usually should not be selected. After saving the settings restart of Cumulus might be needed to take settings in effect. Of course you can test the automatic connection detection if all else fails.

freddie

Thanks for your comments.

Router's firewall is now back on - thanks.

Checked and the same settings FTP, user name, host, password and port number used in Cululux and Filezilla.

I'll try and speak to my ISP tech people tomorrow.

One more thing came to my mind after my last post. If you are running on windows, could the router change have also changed your Windows firewall profile from home/work to public and therefore block Cumulus from connecting?

Many thanks for all your help.
Finally back up and running, thanks to SamiS. Enable active ftp was set (always has been) now unticked.

Great support from all of you.

Best wishes

Glad to hear it is sorted.

Active ftp is a tricky protocol since it requires dynamic inbound connections from the server to the client through nat and/or firewalls, so it should not be used anymore really. Opening the necessary ports from firewall or doing port forwarding will cause security issues.

However on passive mode all ftp connections are opened from client to server, so it is much more compatible with nat and firewalls. Of course it is still plaintext readable, so not very secure either.