MetaChat REGISTER   ||   LOGIN   ||   IMAGES ARE OFF   ||   RECENT COMMENTS




artphoto by splunge
artphoto by TheophileEscargot
artphoto by Kronos_to_Earth
artphoto by ethylene

Home

About

Search

Archives

Mecha Wiki

Metachat Eye

Emcee

IRC Channels

IRC FAQ


 RSS


Comment Feed:

RSS

21 March 2007

Vox Users and Computer Geniuses I need help. It seems I can no longer upload the posts from my blog to my vox blog. This worked so well in the beginning. Now I get the following error...[More:]Error: Fetching http://@www.typepad.com/t/atom/weblog/blog_id=219444/limit=20 failed: 500 Internal Server Error

What does this mean?
I'm neither, but it would seem to be a problem on the typepad side rather than the vox side. You are trying to export entries from typepad to vox, and it used to work but stopped working, correct?

The URL you posted seems to require a username/password before the @ sign to work...did you edit that part out purposely (as you should have), or is that the actual link vox is trying to use to get the post?
posted by danostuporstar 21 March | 14:14
Once you put in the url it requests the password and then a separate window opens. Once I have supplied that information -- I get the error.
posted by Lola_G 21 March | 14:20
How long has the problem been occuring ... aka have you eliminated the possibility of typepad being temporarily flakey?
posted by danostuporstar 21 March | 14:29
About three weeks...
posted by Lola_G 21 March | 14:40
Hee, yeah, you've eliminated the possibility.

Well, I lose. Good luck. (You've tried searching the user forums for vox and typepad?)
posted by danostuporstar 21 March | 14:43
I appreciate your help. Hopefully, vox will come through for me (I sent this question to them as well).
posted by Lola_G 21 March | 14:57
"500 Internal Server Error" is a general error message the typepad Web server is throwing when its processes consume more resources than it is allowed, or if an internal process it is trying to run is throwing an error. To see what is really going on, you need to read the Web server's internal error log, or more likely, any database error logs. If the Web server or database on the typepad installation isn't set up to log internal process errors, you'll have to trap errors during the execution of your next command run, and resolve any associated diagnostic messages accordingly.
posted by paulsc 21 March | 15:01
I don't think typepad provides that sort of access, paulsc.
posted by danostuporstar 21 March | 15:18
"I don't think typepad provides that sort of access, paulsc."
posted by danostuporstar 21 March

Right you are, danostuporstar. Then Lola_G, we toss you into the loving arms of typepad support. Lotsa luck.
posted by paulsc 21 March | 16:03
Police arrest man for possession of flour || You wanna know what's funny?

HOME  ||   REGISTER  ||   LOGIN