ftp issues after switching hosting to namecheap

I signed up with namecheap to host my website but after a few days of working fine now updates are not working. Ports seem to be the problem

The following is in the ftp log

331 User wateuavs OK. Password required
PASSWORD=****
230 OK. Current restricted directory is /
TYPE I
200 TYPE is now 8-bit binary
CWD /waterfordcityweather.com
250 OK. Current directory is /waterfordcityweather.com
2415.6
PORT 192,168,0,157,194,43
200 PORT command successful
STOR clientraw.txt
425 Could not open data connection to port 49707: Connection refused
141: 425 Could not open data connection to port 49707: Connection refused
PORT 192,168,0,157,194,45
200 PORT command successful
STOR plaintext.txt
425 Could not open data connection to port 49709: Connection refused
141: 425 Could not open data connection to port 49709: Connection refused
PORT 192,168,0,157,194,46
200 PORT command successful
STOR testtags.php
425 Could not open data connection to port 49710: Connection refused
141: 425 Could not open data connection to port 49710: Connection refused
PORT 192,168,0,157,194,48
200 PORT command successful
STOR testtags.txt
425 Could not open data connection to port 49712: Connection refused
141: 425 Could not open data connection to port 49712: Connection refused
PORT 192,168,0,157,194,50
200 PORT command successful
STOR webcam000.jpg
425 Could not open data connection to port 49714: Connection refused
141: 425 Could not open data connection to port 49714: Connection refused
PORT 192,168,0,157,194,51
200 PORT command successful
STOR dailynoaareport.htm
425 Could not open data connection to port 49715: Connection refused
141: 425 Could not open data connection to port 49715: Connection refused
PORT 192,168,0,157,194,53
200 PORT command successful
STOR dirplot.gif
425 Could not open data connection to port 49717: Connection refused
141: 425 Could not open data connection to port 49717: Connection refused
Logging off from 2nd server grouped
QUIT
221-Goodbye. You uploaded 0 and downloaded 0 kbytes.

I have contacted namecheap and they say a huge amounts of ports need to be opened which is not possible on shared hosting

I said to them Brian would not develop a software that needs so many open ports and the software worked fine on shared hosting for me before.

Is namecheap just not suitable for weather display uploads?? Any advice would be helpful

the website is www.waterfordcityweather.com

According to the namecheap knowledgebase you can use secure FTP. My guess is that you were using regular FTP with your old host and will need to change the settings in WD to use one of the following:

FTPES (explicit SSL mode, encrypted):

Host: your server hostname or IP address
Username: your cPanel username or full FTP username
Password: your cPanel password or FTP account password
Port: 21

SFTP (SSH-based secure FTP, encrypted):

Host: sftp://your server hostname or IP address
Username: your cPanel username
Password: your cPanel password
Port: 21098

Thanks Niko. Will give that a try

also try setting to use passive mode

Passive mode didn

when you say issues the same with SFTP
how do you mean exactly?
post the ftplogfull after setting that

Here is what i get when using SFTP. I’m using port 21098 as suggested by namecheap but also have used port 22

Time/date***:21:24:17 23/05/2019
Logging onto FTP server…198.xx.116.236
SFTP Connected to 198.xx.116.236 10060 The current connection has timed out.
Remote directory =/waterfordcityweather.com
Doing abort procedure/program close…

but that is not the same issue at all
that is now a completely different issue
the IP address looks to be a local IP address
that does not seem correct

The common issue of the website not updating remains. The address is the one namecheap gave me and i can gain access to the website files using filezilla in SFTP mode

but the web site will not update if the ftp does not work
you now have a different ftp issue, after setting to use sftp
its not the same issue as before
that looks like a local IP, which is not normal

Different issues but same outcome of a website that

That 198.x.x.x IP is fine, definitely not the issue.

the best thing is to email me your ftp details so I can test here
(it might be that you need to use ftps or similar)

the ftp issue is very different now, to original problem
you cant argue with that

Thats true Brian, i will send you the ftp details

works here with the FTP settings you sent me by using default ftp settings in WD (i.e no secure ftp etc)
i sent you an email

this has been resolved via email

Yes thanks to Brian for his help.