found drama

get oblique

beat my head…

by Rob Friesel

CURRENTLY AGGRAVATING: Blogger and FuitadNet, not playing nice.

What I don’t get: My Blogger account can connect to the FuitadNet server just fine and dump my posts etc. up there w/ no difficulty. Clean and easy every time (and over SFTP no less). However, for whatever reason, A’s account refuses to connect over FTP or SFTP. She says that she’d post more often but that the frequency of these errors (see also “every time she tried to post something”) have caused a level of frustration unsuitable for even one with a high tolerance for that sort of thing. Take the following examples:

Post attempts over FTP yield:
001 java.net.ConnectException: Connection timed out on file:archive/2004_08_01_archive.html

…vs…

Post attempts over SFTP yield:
005 Unable to connect to SFTP server: Auth fail

Now the first error suggested to me a permissions problem w/r/t/ being able to create new files in the archive tree. OK, that’s annoying but hardly the end of the world. Unfortunately, similar time-out errors were occuring when trying to “republish index only”. Now, since I’ve had no problems publishing over SFTP, I tried to just switch them (knowing that this was unlikely to yield the results I wanted as I would probably need to request that the account be given SFTP perms). Sure enough, it didn’t work and so I assumed (correctly?) that it just wasn’t set up for this sort of access. OK… But if that’s the case, why am I getting these responses out of FuitadNet tech support:

Greetings,

Your FTP user amy@founddrama.net is already enable SFTP access; Please let us know what exactly you want please brief.

Regards,
Support Team.
———————————-
Thank you for choosing FuitadNET WebHosting Services.

I really want this to make sense… So why doesn’t it?

UPDATE: For folks just now joining the discussion (Sept. 14, 2005) – – I never did come to any thrilling conclusions. It just sort of started working. For one thing, the systems seem to talk better using SFTP over FTP. But after a little while I stopped getting the errors. Blogger fixed? FuitadNet fixed? Just don’t know…

About Rob Friesel

Software engineer by day, science fiction writer by night. Author of The PhantomJS Cookbook and a short story in Please Do Not Remove. View all posts by Rob Friesel →

6 Responses to beat my head…

Anonymous says:

I was having an issue with this at one point (although with my own setup — not FuitadNet. I found that the DNS setup pointing modus-ponens.com to my server was whack and not pointing to the correct place nameserver (duh). Then finally, after I corrected that issue it still didn;t work because the nameserver change had not disseminated through the net and therefore took a long time to connect given a request thus causing the timeout errors. After about 72 hours all seemed well.

-m

mike says:

I was having an issue with this at one point (although with my own setup — not FuitadNet. I found that the DNS setup pointing modus-ponens.com to my server was whack and not pointing to the correct place nameserver (duh). Then finally, after I corrected that issue it still didn;t work because the nameserver change had not disseminated through the net and therefore took a long time to connect given a request thus causing the timeout errors. After about 72 hours all seemed well.

-m

Anonymous says:

I’ve had horrible problems with fuitadnet… And the worst part is that I’m having problems finding a replacement host for the same price.

Regardless, I can’t connect over FTP for long periods of time, and my mail server doesn’t always receive messages immidiatly (i have to wait HOURS before my messages arrive!)

Cruachan says:

I’ve been having the exact problem with sftp
“005 Unable to connect to SFTP server: Auth fail”

all the necessary permissions have been setup.. i can even login manually when i’m using the blog username i created for the sftp server.. why is this happeneing? i have no idea.. although i did create the cname sftp.?????.net recently and that is what i’m telling blogger to use as the server to login on. I guess i’ll wait 72 hours

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*