Topic: 530 Error--Can't make ftp connection

[Bunty]

Does anyone know how to solve this odd problem?  It didn't happen until the day after I started using Weather Display to upload.  It's now offline.  I can't connect to my ftp because of it.  Instead, I get back:  530 Sorry, the maximum number of clients (3) from your host are already connected I use e-rice and have reported it to them.

[Weather Display]

most likely caused by the FTP not releasing/disconnecting a session ...leaving open too many connections
or too many concurrent FTP connections
(i.e try reducing the frequency of uploads)
what were you using to upload before?

[Bunty]

most likely caused by the FTP not releasing/disconnecting a session ...leaving open too many connections
or too many concurrent FTP connections
(i.e try reducing the frequency of uploads)
what were you using to upload before?

Weatherlink and WS FTP or Filezilla.  With WD now offline, I don't believe I'm doing anything different now, other than using TCP/IP, rather than a port,  to connect Weatherlink..  I'm kinda afraid to disconnect Weatherlink out of fear I may not be able to get back on.

[Bunty]

E-rice responded back to ask if there was something I could do at my end.  All I know is to do is to get Weatherlink off of TCP/IP on Virtual VP and restore it back to where it was before I installed Virtual VP.

[Weather Display]

TCP/IP of data from the IP data logger to the weatherlink.com server or just to VVP via your LAN has no bearing or interaction with FTP to your FTP provider

[Bunty]

TCP/IP of data from the IP data logger to the weatherlink.com server or just to VVP via your LAN has no bearing or interaction with FTP to your FTP provider

Thanks, but I was afraid that would be the response.  I've ran web sites for 10 years and have never encountered this problem.  Resetting my cable modem and wireless router did not work.  Going into Filezilla and setting maximum connections to a greater number than 3 did not work, either.  For now, all I know to do is to wait and hope the problem solves itself.

[mackbig]

This is one of the reasons I went to Fling several years ago.  Godaddy limit is 2, I only really noticed it on occasion when I went in via Filezilla or another ftp app.  t would say I couldnt connect.

At the time I was running these apps, and they all had their own ftp running and logging in a various times:
vws (wflash files, 8 htx generated php files, jpgs)
wasp2 (jpg)
nextstorm (jpg, spark, and stormvue)
GR3
2 web cams.  (images)
not weather-related but I also upload my Brultech energy file. (csv)

So all those applications that could potentially be trying to login at the same time, and putting me over the 2 limit.  Plus my manual ftp when editing files on the site.

Added one more potential when I started using WD for my new Vp2 in 2009.

Fling does all the apps listed above except for:
GR3 (does it own re-write routine with files names on each upload)
webcams (both IP based)
WD clientraw (i do all the non clientraw WD files via Fling)

I dont recall seeing the "too many connections" message since 2009.  And never a locked connection.

Andrew


 

[Weather Display]

one way to avoid the problem would be to reduce the frequency of WD ftp uploads, so that you do not get 2 concurrent FTP uploads or similar
or use a plan/host that allowd more concurrent FTP connections

[Axelvold]

one way to avoid the problem would be to reduce the frequency of WD ftp uploads, so that you do not get 2 concurrent FTP uploads or similar
or use a plan/host that allowd more concurrent FTP connections

I'm allowd to have 12 connections at the same time but I do also get the message that I cant make ftp connection.

All I have is WD to update Clientraw files every 2 second, and ftp some every 5 minute.

I'm currently using 5.5 of the real time ftp, because the latest version seems to get stuck after a few hours of uploading.

Don't get me wrong now, I'm not saying it's WD that causing this problem.

[Weather Display]

I dont have any stuck problems with the latest clientrawrealtimeftp here
might depend on the FTP server used (I have never seen this 530 error here myself after 10 years of using the FTP server I use)