site upgrade mostly complete

[mark]

Okay, so the site is now running on the hardware from ServerBeach. This is a big change for us, as we're now using dedicated machines: i.e., hardware that isn't shared with other users.

This should help improve our speed and reliability and generally make things better. Yay.

The move itself seems to have gone pretty well. We have a few things left to iron out (cron jobs, search, incoming email) but by and large it's running smoothly. No complaints yet.

If you see anything not working (except for the aforementioned journal search), please let us know!

Edit: Since our IP addresses have changed, we're going to have to go through the process of getting ISPs and mail providers to trust us again. This can be a lengthy process, so if you see mail not going through, please let us know so we can investigate and contact the ISP in question.

Comments

[cesy]

Yay for new servers! All looks fine so far.

[afuna]

Yay \o/ Congratulations on the smooth server move. Felt no pain here on my end!

[pixel]

Congrats guys!

[brutal_priestess]

Yeah, I don't know if Yahoo is taking too well to it. I seem to have stopped getting comment notifications.

[denise]

Yahoo's one of the providers that greylists us at a moment's notice, yeah. We're working on the steps we need to take to get whitelisted again -- I'm really sorry about the inconvenience!

Gmail still works

[baggyeyes]

I just received a comment, so I know that's fine.

[davidcook]

I seem to have found a small issue - since the move, I can read my full reading page ok (i.e. http://davidcook.dreamwidth.org/read) and I can still view communities and feeds with ?show=c and ?show=f - but the "people" (?show=p) filter is giving me an error page :

Oops!

If you've gotten this error, it means that something is currently (and, with luck, temporarily) broken. Please wait five minutes and try again.

If the problem persists after five minutes, please check our offsite status page to see if we're aware of the problem. If we haven't updated it, drop us an email and let us know something's broken. (Be sure to tell us what you were doing.)

It's been more than five minutes, obviously, and occurs from home and work and despite cache cleaning and all the usual stuff.
(as an aside: The Preview function is not really showing me my post with the HTML active, e.g. the blockquote is just showing up as text in Preview. Don't know how it'll look when posted :-) )

[resonant]

My mail isn't getting through still. I'm using sbcglobal.net. Can I do anything to help?

[mark]

Thanks for the heads up. I just filled out AT&T's form again, if I don't hear back in a few days I'll try to call them.

[isagel]

I posted about not getting comment emails, and my circle helpfully sent me to this post. :)

I've never had any problems getting my comment notification mails from DW before, but lately I'm not getting anything, and it's not in the spam filter. I have my DW mail set to come to the address associated with my personal domain (isagel at wunderwesen dot com), which is hosted by godaddy.com. Since I'm getting all other mail, as far as I can tell, I'm guessing that means the problem is somewhere between you and GoDaddy.

Thank you all so much for the great work you're doing! Dreamwidth is turning out amazing, and I've remained thrilled to be a part of it at every turn.

[mark]

Okay, I did some investigation, and it looks like we're getting this error:

Permanent failure TO [wunderwesen.com]: 553 Attack detected from pool 69.174.244.159.

Unfortunately, it looks like someone else near our IP (we are 69.174.244.50 and thereabouts) is spamming. GoDaddy has overzealously blocked an entire range of IPs, which includes us.

I'll try to contact them and see if we can get this sorted.

[isagel]

Thank you for looking into it and for replying so quickly. I hope it won't be too hard to sort out. :)