Blogger 550 error
I should have gone to bed ages ago, but setting up a blog on Blogger.com for 9mmfilm was driving me nuts.
I set two blogs up for Seanoneillsongs.com without a hitch, but when it came to 9mmfilm I kept getting a 550 error (permission denied). I guess I should have gone to bed and dealt with it in the morning because the answer was staring me in the face...
I did a google on it and found it to be a common problem, but for a lot of people it was because they didn't enter the ftp path correctly, which I knew I had.
Then I came accross an article which said when they turned off archiving it worked fine. So I tried that and I discovered that it got me a step further in that files were created on my site, but I then got a 550 error for the atom.xml file.
And this is where my stupidity comes into play... I guessed straight away that the atom.xml file was being put somewhere I didn't have write access to being on a virtual server. But it took me hours to discover that under the Site Feed options you are supposed to enter the full path for creating the file.
I had assumed that Blogger derived all paths from the initial ftp path, but it doesn't.
So then I went through all the settings tabs and entered the paths for the archive and the xml file and bang, everything worked fine.
So goodnight!
I set two blogs up for Seanoneillsongs.com without a hitch, but when it came to 9mmfilm I kept getting a 550 error (permission denied). I guess I should have gone to bed and dealt with it in the morning because the answer was staring me in the face...
I did a google on it and found it to be a common problem, but for a lot of people it was because they didn't enter the ftp path correctly, which I knew I had.
Then I came accross an article which said when they turned off archiving it worked fine. So I tried that and I discovered that it got me a step further in that files were created on my site, but I then got a 550 error for the atom.xml file.
And this is where my stupidity comes into play... I guessed straight away that the atom.xml file was being put somewhere I didn't have write access to being on a virtual server. But it took me hours to discover that under the Site Feed options you are supposed to enter the full path for creating the file.
I had assumed that Blogger derived all paths from the initial ftp path, but it doesn't.
So then I went through all the settings tabs and entered the paths for the archive and the xml file and bang, everything worked fine.
So goodnight!

10 Comments:
This comment has been removed by a blog administrator.
just testing comments and comments delete now that I'm up and running. Getting to know all the features...
This comment has been removed by a blog administrator.
This comment has been removed by a blog administrator.
this is all just testing. i updated the template and needed to make sure delete still worked!
hey, I'm just testing
Your posting helped me fix my blog!
My problem was also with Site Feed on blogger.com, even though it had been working before.
Thanks so much!
Keith
Glad it helped!
Cheers,
Frank
hngr! it is indeed such a simple fix, i wish Blogger had put it on their site. I am very grateful that you did!
I'm just glad this comes in useful for people from time to time!
Post a Comment
Subscribe to Post Comments [Atom]
<< Home