Skip to main content
Question

FTP Caller causes URL using bad/illegal format or missing URL

  • September 15, 2016
  • 5 replies
  • 253 views

 

 

FTP Caller causes URL using bad/illegal format or missing URL. I am trying to upload a file to my ftp server but keep getting this error. Attached are the screen shots of my configurations. I have tried various different possibilities but no luck. I have no trouble uploading file to my ftp server through command line. Here is the

 

Variations I have tried (It can connect but says the url is bad! Because if i put bad username password etc I just get can't connect or get bad domain name error):

ftp://dev-gismap02.flysfo.com/

 

ftp://dev-gismap02.flysfo.com/home/abhandari/

ftp://dev-gismap02.flysfo.com

 

ftp://dev-gismap02.flysfo.com/home/abhandari

ftp://x.x.x.x/

 

ftp://x.x.x.x/home/abhandari/

5 replies

david_r
Celebrity
  • September 16, 2016

You have to put the complete filename in the URL, e.g.

ftp://dev-gismap02.flysfo.com/home/abhandari/testing.kmz


  • Author
  • September 16, 2016
david_r wrote:

You have to put the complete filename in the URL, e.g.

ftp://dev-gismap02.flysfo.com/home/abhandari/testing.kmz

OK When I tried that, I get 

 

 

2016-09-16 14:16:16|   0.2|  0.0|ERROR |HTTP/FTP transfer error: 'Couldn't connect to server'

 

 

Cannnot connect. I can connect fine via my shell for mac. 

 

 


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • September 19, 2016
david_r wrote:

You have to put the complete filename in the URL, e.g.

ftp://dev-gismap02.flysfo.com/home/abhandari/testing.kmz

The full filename is definitely the way to go (I see other confirmation of that).

 

So if you are still having problems...

 

1) Try turning on Debug logging (Tools > FME Options > Translation > Log Debug) and see if that reveals any more information in the log window

 

2) Try writing to a site that I know works. Copy a small test file to ftp.safe.com/incoming/filename.kmz - no username or password required. I just did that and you can see that there is imarktest.kmz there. So I know it works for me. Let's see if it works for you. It will at least narrow down where the problem lies.

 

 


  • Author
  • September 19, 2016
mark2atsafe wrote:
The full filename is definitely the way to go (I see other confirmation of that).

 

So if you are still having problems...

 

1) Try turning on Debug logging (Tools > FME Options > Translation > Log Debug) and see if that reveals any more information in the log window

 

2) Try writing to a site that I know works. Copy a small test file to ftp.safe.com/incoming/filename.kmz - no username or password required. I just did that and you can see that there is imarktest.kmz there. So I know it works for me. Let's see if it works for you. It will at least narrow down where the problem lies.

 

 

 

That worked for me.. I am not sure why its not working for my machine then. I can transfer file through my command line shell. I also made sure the username password is correct. I am using vsftd in redhat. Could it be having to put username and password?

 

 

 

This is the output for log file. ftp.txt (Is this the one you are looking for?)

  • Author
  • September 19, 2016
mark2atsafe wrote:
The full filename is definitely the way to go (I see other confirmation of that).

 

So if you are still having problems...

 

1) Try turning on Debug logging (Tools > FME Options > Translation > Log Debug) and see if that reveals any more information in the log window

 

2) Try writing to a site that I know works. Copy a small test file to ftp.safe.com/incoming/filename.kmz - no username or password required. I just did that and you can see that there is imarktest.kmz there. So I know it works for me. Let's see if it works for you. It will at least narrow down where the problem lies.

 

 

Also configured anon login. Even that doesn't work. When I put the wrong dir I get access denied, which is good. But when i put the right dir, I get Can't Connect.

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings