karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
Thanks to everyone who let us know that Photobucket images were not loading properly on some pages. The problem seemed to be mostly limited to HTTPS requests; Dreamwidth maintains a list of known high-traffic image sites that support HTTPS, so that our secure content proxy service doesn't cache them unnecessarily. Unfortunately Photobucket seems to have recently changed their site configuration such that HTTPS requests aren't being served as expected, and we've now taken it out of our list of "proxy-exempt" sites.

If you continue to have issues, make sure you're not using HTTPS Photobucket links. It's a bit counterintuitive, but if you use HTTP instead, it will be automatically transformed on our end to an HTTPS link that uses p.dreamwidth.org.

Hope that clears everything up for now! Let us know if it doesn't...
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
InsaneJournal has had a hardware failure that means their service is temporarily offline. To avoid sending traffic to them while they're down, we've temporarily disabled them as a crossposting and importing source. We'll re-enable them when they're back up.

Good luck to [insanejournal.com profile] squeaky with the recovery!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
LiveJournal has unblocked and whitelisted our webserver IP addresses, so importing, crossposting, and feed accounts should work properly again! Thanks for the quick fix, LJ.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise

Cloudflare


We've had people ask us about the Cloudflare leak reported a few days ago. We are Cloudflare customers, and it is possible that login cookies or passwords may have been exposed as part of the incident. We believe the risk to you is relatively low -- it was a small percentage of Cloudflare's requests that were involved over a relatively short period of time, and we haven't found any evidence that anything from us was among them. This is not an absolute guarantee that none of your accounts were affected, but we don't think the likelihood is very high.

Because we believe the risk to be low, we aren't automatically expiring everyone's session cookies and requiring you to log back in and change your password -- whenever we do that, it does lock some people who they can't remember their passwords and no longer have access to their confirmed email addresses out of their accounts, and we believe that will affect more people in this case.

Still, it's always a good idea to change your passwords regularly, and now would be a good time to do it, especially if you want peace of mind. We have a FAQ on how to change your password. If your browser logs you in automatically and you don't remember your password, you can reset it. If you've forgotten your password and no longer have access to your most recent confirmed email address, you can have the password reset email sent to any email address you've confirmed on your account by entering both your username and your old email address at the Lost Info page.

Unfortunately, if you've forgotten your password and no longer have access to any email address you've confirmed on your account, you probably won't be able to reset your password. In some cases, if you've previously paid for your account, we can validate your payment details to confirm your identity and reset your password. If you can't reset your password, but think you may have paid for your account in the past, you can open a support request in the Account Payments category and I'll check into it for you.


LiveJournal imports/crossposts/feeds


LiveJournal has temporarily blocked about 2/3rds of our webservers from contacting their site, presumably because they feel that we're requesting data from them too often. This affects the ability to import your journal, the ability to crosspost entries from your Dreamwidth account to your LiveJournal account, and whether syndicated feeds of accounts on LiveJournal will update on Dreamwidth. Those features will fail when they're unable to contact LJ because of the block.

It isn't every one of our webservers, so things will work intermittently -- if you crosspost two entries one right after the other, one might succeed while the other fails. Unfortunately, there isn't much we can do to resolve this other than contacting them and asking them to unblock us (which I'll be doing right after I hit 'post' on this entry).

EDIT 2249 EST 25 Feb: We appear to be down to zero unblocked webservers, so imports, crossposts, and feeds will all fail until LJ unblocks us.

EDIT 26 Feb noon EST: LJ unblocked and whitelisted us this morning, so all is working again!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
We're about to pull the lever on tonight's code push! I'll update this post when it's finished. For a reminder of what to expect, check the previous post for the list of changes.

Update: All done! Comment here if you notice any issues that need our attention.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
We are planning to do a code push late this weekend, at approximately 9pm PST / 12am EST / 5am UTC on either Sunday, Feb 12 or Monday, Feb 13, depending on whether you live east or west of midnight. (Time is an illusion anyway, right?)

Here's a partial list of changes that will go live with this push, apart from the usual minor tweaks and bugfixes:

  • HTTPS Everywhere beta! Users can opt-in to have all Dreamwidth content automatically served over HTTPS. We'll post the instructions for this after the feature goes live.

  • New and improved design for the file management pages, which we were hiding from you because we were so embarrassed about them before. Thanks to [personal profile] momijizukamori for making them prettier and more functional!

  • Backend fixes to resolve problems using the aforementioned file management pages. (Did I already mention the embarrassment?)

  • At long last, international character support for journal search! Our systems guru [personal profile] alierak finally cracked this long-standing bug.

  • Support index page converted to Foundation styling, for your mobile viewing pleasure.

  • For users of the Practicality style: color properties now sort properly in the customization wizard.

  • For users of the Drifting style: the QuickReply box will now appear in the appropriate location, instead of wandering off somewhere unexpected.

  • Improved handling of word break (<wbr>) elements in user entries.

  • Allow embeds from: Facebook, CNN, 4shared.com, playmoss.com, onedrive.com, jsfiddle.net, scratch.mit.edu


We'll update again to let you know when the code push is in progress!
mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark
Hey all,

Sorry for the 'Welcome to nginx!' issues we've been seeing for a bit now. It was a server configuration issue that hit us when a webserver rebooted.

Basically when the machine rebooted, nginx (software that can act as a web server) started up and then when Apache (the software Dreamwidth code uses for a web server) tried to start, it failed because nginx had already started and registered on the ports (the way web server software gets your requests).

Again, sorry for the site issues. Everything should be back to happy-times now, so let us know if you see any issues!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
The site slowdown tonight (Saturday night) is due to database load -- Saturday nights are one of our busiest times and we're still going to need to do some performance tweaks to our new setup over the next few days as we run into load issues. (Some problems only show up once all y'all start banging on the site!) We've made a few changes now that will improve things for some people, and will do a more permanent fix later on tonight or tomorrow morning once the traffic dies down, since doing it now would just increase database load.

Site performance may continue to be rocky on and off for the next few days until we get everything tuned the way it needs to be tuned -- thank you for your patience!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
  • The site may occasionally be slow to respond or have trouble connecting as we tune servers and databases, or you may receive Gateway Timeout errors.

  • Comment notification emails may be delayed due to database load.

  • Inbound email (post-by-email and comment-by-email) may be delayed for a bit while your outgoing mail server catches up with the switch.

  • Email sent to your username@dreamwidth.org address may be more likely to be marked as spam, due to our mail server changing its IP address.

  • The site search database may be missing entries and comments and will catch up over the next few days, as database load allows. Entries and comments posted since the site came back up will be added to the index as they're posted.

  • Logging into other sites using your Dreamwidth OpenID is working again! Yay!

  • Loading embedded content over secure connections should be fixed!

  • There is a known problem with trying to rearrange elements on the Beta Update page because a script element isn't loading properly. Update: This should be fixed now!


Let us know if you see anything else odd with the site that isn't listed here!

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
We have now cut over to our new hardware! If you can see this, the site should be working for you.

Things you don't need to tell us about:

* The site may look a little weird or naked for a while as your computer/network/ISP/etc catches up with the switch.
* Comment notification emails should be going out properly, but inbound email (post-by-email and comment-by-email) may be delayed for a bit while your outgoing mail server catches up with the switch.
* The site search database is a few days out of date (missing entries from the past two days) and will catch up over the next few days. Entries and comments posted since the site came back up will be added to the index when they're posted.

Known issues:

* Accessing the site will be slow for a while as the caches warm back up, and you may receive Gateway Timeout errors.
* Due to the occasional database connection problem due to high load and site slowness earlier, some comments did not generate emailed notifications and those notifications can't be re-sent. New comments made since we resolved the DB problems are generating email notifications, but slowly (due to the general database slowness).
* Logging in to other sites using your Dreamwidth OpenID is broken (& we'll fix it as soon as we can!)

Let us know if you see anything else weird!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
We are now within our maintenance window for today. The site will go into read-only mode when we're ready to begin the maintenance, and will be unavailable for at least most of the morning. Watch our Twitter status account for updates!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
A reminder: the site will be down/in read-only mode tomorrow for server maintenance for at least a little while. (Some people may also have trouble accessing the site even after it comes back up, depending on your network/computer/ISP settings.) We're beginning the maintenance window at 10AM EST/7AM PST/11PM UTC, and to be on the safe side, we're setting a window of 8 hours for possible downtime. It probably won't take that long, but there's also a (very small) chance it may take longer! We'll keep you updated on any changes with our off-site status Twitter account.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
As we prep for tomorrow's server maintenance, the site may look weird or 'naked' (no styling, images not loading, etc) on and off over the next hour or so. If you notice it, there's no need to report it: if it happens, we did it on purpose.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
There will be a maintenance window, with some downtime, on Thursday, December 1, starting at 10AM EST/7AM PST/3PM UTC, for server maintenance and upgrades. To err on the side of caution, we're calling it an 8 hour window (so, until 6PM EST/3PM PST/11PM UTC), although we don't expect that the site will be in maintenance mode for the whole time.

We'll remind you Wednesday night, and again when the site is going into maintenance mode.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
I'm about to pull the lever on tonight's code push! I'll update this post when it's finished.

Update: All done! Comment here if you notice any issues that need our attention. Sorry about any transient weirdness for a few minutes there.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
We are planning to do a code push around 21 hours from now, at approximately 6pm Pacific time on Saturday, Oct 1.

Here's a partial list of changes that will go live with this push, apart from the usual minor tweaks and bugfixes:


  • Selective Screening, a new feature that lets you screen comments from a particular user.

  • Two new journal layouts with one theme each: Gold Leaf/Elegant Notebook and Venture/Radiant Aqua.

  • Six new themes for Heads Up, and seven new themes for Corinthian.

  • The minimal spacing between line elements in the list of success links on Foundation pages has been restored.

  • Punctuation marks in message subjects will no longer be overescaped.

  • The admin pages for the translation system are now hidden from anonymous viewers, to avoid scaring unsuspecting search engine users away from the site.

  • The text messaging feature has been removed from user profiles.

  • The email notification worker is now less likely to misbehave.


We'll update again to let you know when the code push is in progress!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
Sorry for the delayed response on the issue with emailed comment and support notifications not being delivered. We weren't receiving our emailed comment and support notifications saying that there was a problem...

We restarted the relevant software services around 10AM EDT, and the backlog of delayed notifications should have all been sent by now. Thanks for your patience, and extra thanks to everyone who tried to let us know about the problem!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
Reminder that I'm going to start working on tonight's code push in the next 30-45 minutes or so. I know you just CAN'T WAIT to use the larger icon filesize for your animated gif talents, so I'm going to start a bit earlier than originally planned, closer to 5:30pm PDT. I'll update this post when we're done!

Update: All done! Comment here if you notice any issues that need our attention.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
We are planning to do a code push around 32[*] hours from now, at approximately 6pm Pacific time on Saturday.

Here's a partial list of changes that will go live with this push, apart from the usual minor tweaks and bugfixes:

  • Icon size limit raised from 40kb to 60kb.

  • Fixed the "hook: enddata returned false" error when uploading multiple icons.

  • Posting DW links on Facebook will now use the "Swirly D" logo for the link image.

  • Added seven new color variants on the popular "Teeny Tinies" mood theme.

  • The user profile page now lists "Other Services" in responsive columns.

  • The user icons page no longer uses "(Default)" in the alt text for every icon.

  • Improved non-ASCII character support in plain text email notifications.


We'll update again to let you know when the code push is in progress!

[*] I had a computer check my math this time, because it was almost wrong again. YAY COMPUTERS.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
People getting mail at Gmail are reporting email delays of about an hour. As far as I can figure out, it's because some of our recent changes to our network have wiped out our existing sending reputation with them and made us start building reputation again, and they're refusing all mail on first delivery and making us re-send it. (It's a common spam reduction technique, because spammers don't bother retrying if the first attempt fails.)

There isn't much we can do about it but wait it out until Gmail decides that we're legit senders again, but we'll poke at it and see if there's anything we can do to make the process go faster. (I doubt there will be, though; Gmail is persnickety.) In the meantime, to get comment notification email faster, you can switch your confirmed email to a different provider, or just refresh your on-DW inbox.

EDIT: And people are now letting me know that mail's delayed to other providers, too, which is probably follow-on effects from having to send everything to Gmail at least twice. There isn't a lot we can do about it; I'm sorry about the hassle, folks.
Page generated Mar. 25th, 2017 07:44 pm
Powered by Dreamwidth Studios