FTP Problem
-
Please Help :
I had setup cuteFTP instead of Fillezilla as FTP client and it was working , until i tried to create a new folder using the cuteftp program and this message appears :*** CuteFTP 8.0 - build Aug 9 2006 ***
STATUS:> [10/8/2015 11:42:06 AM] Getting listing ""…
STATUS:> [10/8/2015 11:42:06 AM] Connecting to HTTP proxy server… 192.168.224.77:3128 (ip = 192.168.224.77)...
STATUS:> [10/8/2015 11:42:06 AM] Requesting server…
[10/8/2015 11:42:06 AM] GET ftp://2096:****@ftpq.ecgsa.com/ HTTP/1.1
Host: ftpq.ecgsa.com:21
Range: bytes=0-
Referer: /
User-Agent: CuteFTP/8.0
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Accept: ., /
Pragma: no-cacheSTATUS:> [10/8/2015 11:42:06 AM] Receiving reply…
[10/8/2015 11:42:10 AM] HTTP/1.0 200 Gatewaying
Server: squid
Date: Thu, 08 Oct 2015 09:42:33 GMT
Content-Type: text/html
X-Cache: MISS from ecgproxy
X-Cache-Lookup: HIT from ecgproxy:3128
Via: 1.0 ecgproxy:3128 (squid)
Connection: closeSTATUS:> [10/8/2015 11:42:10 AM] Downloading…
STATUS:> [10/8/2015 11:42:10 AM] Directory listing completed.
STATUS:> [10/8/2015 11:42:14 AM] Connecting to HTTP proxy server… 192.168.224.77:3128 (ip = 192.168.224.77)...
STATUS:> [10/8/2015 11:42:14 AM] Checking directory existence: "/Test".
STATUS:> [10/8/2015 11:42:14 AM] Requesting server…
[10/8/2015 11:42:14 AM] HEAD ftp://2096:****@ftpq.ecgsa.com/Test/ HTTP/1.1
Host: ftpq.ecgsa.com:21
Referer: /
User-Agent: CuteFTP/8.0
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Accept: ., /STATUS:> [10/8/2015 11:42:14 AM] Receiving reply…
[10/8/2015 11:42:16 AM] HTTP/1.0 404 Not Found
Server: squid
Date: Thu, 08 Oct 2015 09:42:40 GMT
Content-Type: text/html
Content-Length: 1368
X-Squid-Error: ERR_FTP_NOT_FOUND 9
X-Cache: MISS from ecgproxy
X-Cache-Lookup: MISS from ecgproxy:3128
Via: 1.0 ecgproxy:3128 (squid)
Connection: closeERROR:> [10/8/2015 11:42:16 AM] Data connection closed.
STATUS:> [10/8/2015 11:42:16 AM] 404 Not found.
STATUS:> [10/8/2015 11:42:16 AM] Checking directory existence: "/".
STATUS:> [10/8/2015 11:42:16 AM] Connecting to HTTP proxy server… 192.168.224.77:3128 (ip = 192.168.224.77)...
STATUS:> [10/8/2015 11:42:16 AM] Requesting server…
[10/8/2015 11:42:16 AM] MKCOL /Test/ HTTP/1.1
Host: ftpq.ecgsa.com:21
User-Agent: CuteFTP/8.0
Connection: Keep-Alive
Authorization: Basic MjA5NjoqKioqSTATUS:> [10/8/2015 11:42:16 AM] Receiving reply…
[10/8/2015 11:42:16 AM] HTTP/1.0 400 Bad Request
Server: squid
Date: Thu, 08 Oct 2015 09:42:40 GMT
Content-Type: text/html
Content-Length: 1303
X-Squid-Error: ERR_INVALID_REQ 0
X-Cache: MISS from ecgproxy
X-Cache-Lookup: NONE from ecgproxy:3128
Via: 1.0 ecgproxy:3128 (squid)
Connection: closeERROR:> [10/8/2015 11:42:16 AM] 400 Bad request.
ERROR:> [10/8/2015 11:42:16 AM] Can't create following directory: "/Test".can any one help me to solve this problem
-
Authorization: Basic MjA5NjoqKioq
This string seams to tell us that you are only got basic rights on the server and this might be
not allowing you to create folders there. If not so, at the FTP Server, you might be looking in the
Squid logfiles if perhaps Squid is the bad one in this game. -
when i connect to the ftp server without the squid , i can create files , download and upload files. when i connect through the proxy i just be able to show the folders.
-
Stop proxying FTP.
-
when i connect to the ftp server without the squid , i can create files , download and upload files. when i connect through the proxy i just be able to show the folders.
1.) Like @doktornotor said.
2.) Use user auth. at the proxy server and give this user more rights. -
-
The User has all the rights , because if i connect to the FTP server without the proxy it connects without any problems.
@doktornotor how could i stop proxing the FTP ? -
The User has all the rights , because if i connect to the FTP server without the proxy it connects without any problems.
There should be an exception list where you could set an entry, that then this FTP would not be any more
filtered by the Proxy thats it.@doktornotor how could i stop proxing the FTP ?
It is the most insecure protocol in the Internet, sends in plain text!
So with S/FTP or FTP/S you would be providing more security and all would be fine for you.
Otherwise could you set up one or more VPN connections to the pfSense firewall and then
the users could get access to the really insecure FTP but also over an encrypted line or tunnel!
And this would be the best way to go these days as I see it right.