Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

0 points

iWeb 09 ftp publishing error - Test works, publish fails

When I configure a known working ftp/sftp session, the test works, but the publish step fails. I get one of two errors. The first is that the first connection attempt works fine, but subsequent connections (there are many to publish a site) fail because iWeb neglects to include the password. The other issue occurs when I've aligned the stars (by deleting the keychain entry for the ftp service) and got the passwords entering correctly, but the app trys to to a dir/list operation in an intermediate path on the hosting server (which fails due to authentication issues) instead of the full path that I provide.

I can't see how this ever worked in the QA shop??? Something is amiss with the keychain and/or iWeb. This is the first time I've been let down by Apple s/w ... sigh ... 😟

FYI, this is publishing to www.pair.com (Pair Networks' sites) ...

In a few other semi-related posts, others found relief in switching their hosting server from Windows to Linux, which lends some credibility to the keychain issue since I would expect that the keychain entry would need to change for these cases?

Robert

Mac Pro, Mac OS X (10.5.6)

Posted on Jan 28, 2009 8:17 PM

86 replies

Jan 29, 2009 11:44 PM in response to planoBob

I'm having the same problem (test works, publish fails) trying to upload a site to a host (dot5hosting) I just signed up with.

Dot5hosting is completely oriented toward PCs -- no mention of Macs, and all the FTP clients they have instructions for are Mac-only. I'm now, of course, very sorry I chose them but am no doubt stuck with them because I licensed my domain name through them.

I have the Directory/Path field in iWeb blank. If I were to fill it in, what might I put there?

planoBob Author

Level 1

0 points

Jan 30, 2009 4:04 AM in response to mysterioustraveler

Don't know what others have to put in the directory path field, but for my hosting account, I have two web sites, each with a different name. In other FTP clients, I must provide some variation of a unix path (relative or rooted) to be able to ensure that the client places the the right web site contents in the right location. I'd expect that on some other systems, your default directory on login might be the correct place already and there would be no need to enter anything.

I hope that makes sense.

Robert

RRoman

Level 1

0 points

Jan 30, 2009 4:53 AM in response to planoBob

Was on the phone with Apple last night and they believe the problem is with Windows servers. They are investigating and will post fix soon.... At least that's what they told me.

Jan 30, 2009 5:22 AM in response to RRoman

No, the problem isn't with windows servers, it's a bug. I might be to do with how it handles those servers but I doubt it.

B
U
G

Roddy

Level 6

17,265 points

Jan 30, 2009 6:01 AM in response to mysterioustraveler

You're not stuck with a hosting company because of a domain name registration. Simply sign up with a new one and get it redirected.
Although I'm not going to use the built in FTP because of all the downsides, I have tested it and it works on my server whether I fill in the Directory/Path or not.
This is because Host Excellence allows you to create your own folder on the server and name it the same as the one produced by iWeb. This overcomes the limitations of the way in which the iWeb FTP works.

planoBob Author

Level 1

0 points

Jan 31, 2009 6:10 AM in response to RRoman

Not for my case ... pair networks (my hosting company) uses unix systems. Apple support is very wrong and that's because the developers aren't being brought in on this soon enough. I know some folks have fixed their problems with a switch to a linux platform from windows, but that's likely only because they have changed the destination server causing a keychain change which I suspect is the critical link.

Feb 1, 2009 1:29 AM in response to RRoman

Regarding "Windows problem" there is a simple way to reply to that lame excuse. Try publishing with sftp to your own OS X. Test works, but when actually publishing the very elaborate "unknown error". I've managed to make iWeb simply crash on me when trying different ways as well. This was the key feature for updating for me, hope a patch is out soon.

Feb 1, 2009 10:17 AM in response to planoBob

I've just found out that the issue of error 530 "authentication failed" has something to do with the form of the password. If you use other characters than letters and numbers, some servers seem to have problems with it. Try to change your password at your webhoster that it is a combination of letters and numbers.

Steffen

planoBob Author

Level 1

0 points

Feb 1, 2009 4:19 PM in response to Steffen Bendix

When I sniffed the FTP packets, for my case, I found that iWeb wasn't sending a password for the publish operation, just for the test. My solution was to open key chain access and delete the existing keychain entry and then add it again through iWeb.

planoBob Author

Level 1

0 points

Feb 1, 2009 4:21 PM in response to planoBob

I've found that if I remove the directory/path, the tool can publish to the "current directory" fine ... it just doesn't know how to handle a provided alternate directory.

Feb 1, 2009 5:26 PM in response to planoBob

I followed this thread and found how how my host needs the form filled in. I tested it and it works!!!!!!
In the FTP server settings under Directory/Path: I put in the website name only! I did not include www. or ftp:// or http:/ JUST the name of the website. In my case, my website is www.huisking.net and all I put in was huisking.net
Hopefully this works for you. By the way, Bruce S was great on the 1/2 time show that just ended...
Skip

Feb 1, 2009 5:59 PM in response to William Huisking1

To be clear for everyone, the ftp part NEVER belongs in path/directory. The FTP part goes in the first field to get to the server. Apple gives you the gray example. The path/directory is ONLY the part after the .com text. You begin with the "/" and list anything up til and including the folder/directory in which you want your site to land.

Feb 1, 2009 6:04 PM in response to Deborah Shadovitz

In my case, what I plugged in to the Path/Directory box was my hosted website name which included the .com and what was before the .com. It did work as my test website was published.
Skip

Dav-o

Level 1

10 points

Feb 4, 2009 3:50 PM in response to William Huisking1

I had the same problem, generally. Test worked, publish failed. So I tried some of the suggestions listed in this discussion. I changed my ftp password to start with a number, all lower case letters, no special characters. I deleted the keychain listing, and I only listed my domain (in iWeb's ftp setup) as "mydomain.com" - no www, no http://

It worked.

One slight hiccup - even though I only changed one or two pages, I had to upload the entire site, so it took a while, but the site works. I am hoping that was only for the first upload using iWeb 09.

Feb 5, 2009 12:48 AM in response to Viktor.Karlsson

Yay, a patch was released. But did it help? Nope. This is getting silly, I can publish fine to a folder, testing (sftp to the very same machine) works fine but "unknown error" when publishing over (s)ftp.

I guess I'll try to go through the steps (again) in this discussion when I get home but really this 100% reproducible bug should be fixed.

iWeb 09 ftp publishing error - Test works, publish fails