I have been getting this message all day in Natter, but none of theother threads"
502 Connection Failed
This Web page could not be opened. There may be too many people accessing this page or the page may be unavailable. Please try again later.
Harmony ,'Conviction (1)'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
I have been getting this message all day in Natter, but none of theother threads"
502 Connection Failed
This Web page could not be opened. There may be too many people accessing this page or the page may be unavailable. Please try again later.
Hmm. I checked bandwidth allocation, and we're certainly not over our limit.
Anyone else have this problem? Are you still having it, Allyson? Did you get into Natter some but not all of the time?
Can't get into Natter at all. I restarted the comp twice today and both times couldn't get in to Natter.
Are you clicking on the thread name from the main page/message centre, or are you using read new?
Does this "Natter Free 4 All" Nov 23, 2002 9:57:07 pm EST work for you?
I've been using the main page. Let me try the link.
Link works, but still can't get in through the main page.
Just natter and COMM. All the other threads open just fine.
Pfargggh.
More news as I work it out.
But, you know, worse things can happen to a discussion board. Over at Slate, their Fray discussion board just unregistered everybody and required them to get a Microsoft .Net Passport to reregister. That's not going to happen here at our own home. (Though we might have to utter a "Macs are better" watchword if Daniel C. Jensen ever effects his rise to power.)
I couldn't connect to the front page for about 30 minutes (ah, 12:30 to 1am, AST; getting server not found) and then managed to log in, get to natter, then I couldn't move off of the single natter page I was on for 20 or so minutes - no error message, it just kept saying it was contacting the server and didn't go anywhere (I tried clicking on 'read new', 'message centre' and 'next' with no success). Seems fine now. and it might be my connection, which has been ungodly slow tonight.