dw_maintenance | (no subject)

>"Please let us know if you notice any issues."

I'm now unable to cross-post to LJ. But as I'm the only one replying here, it must not be widespread!

Aha. I'd asked you what error message you got in your inbox when you tried, but I'd replied by email and looking at this entry on the website now, it seems that the comment never came through. Which tells me what's wrong, I think. :) Lemme poke at it.

It works now! :-) Thanks to all who worked on it!

---
Yes, exactly. No error messages came for cross-posting attempts last night. The tickboxes were unchecked, so I'd check them and post, and see the usual statement. All attempts failed; none generated failure notifications.

Your reply before this, asking about an error message in my Inbox, did reach me by email.

I'm sorry for being so very brief in my first reply. I should have filed a proper report of steps and results. I'll blame it on the late hour in my timezone, and next time I will remember!

I can't cross post either.

Aha. I'd asked you what error message you got in your inbox when you tried, but I'd replied by email and looking at this entry on the website now, it seems that the comment never came through. Which tells me what's wrong, I think. :) Lemme poke at it and I'll see what's up.

Can you look in your inbox, find the failure message, and copy the text of it for me?

I never got one for any of my morning posts, they just wouldn't cross post to LJ so I pasted them over there myself.

Ha, that was the comment that I'd sent in as a reply just after you made your first comment -- I sent it in via email and didn't notice that the email-to-comment job wasn't running.

Anyway, I think I've figured out what the ultimate cause of the problem is; it's not something I can fix, but the people who can fix it will be around in a bit. When it's fixed, the posts you made earlier tonight will be crossposted, so you might wind up with duplicates on the LJ side. (Just FYI.)

Yeah, I already thought of that. No problem however.

I just posted an entry, but the cross posting isn't working for me either.

I haven't tried it yet, but now I'm also concerned that the importer won't work either...

Edited 2016-04-10 09:08 (UTC)

I think I know what's up with this, but I don't 100% know if I know how to fix it and I don't think anybody who does is still awake. Let me poke at it, and if I can't fix it, one of the people who can should be up in a few hours!

Plus side - I just tried the importer and it works.

I didn't get a failure notice for my crossposts, so I don't think they went through. I've deleted my entry though, so I hope that doesn't mess things up later to figure out the problem.

Edited 2016-04-10 09:15 (UTC)

Nah, it shouldn't break anything. You might have the entry posted on the LJ side once the workers get kicked, but if so, you can just delete it on that end too.

I'll echo that crossposting isn't working. Also, I haven't gotten a failure notice yet, but usually those come back fairly quickly.

I think I know what's going on, but I'm not 100% sure if I know how to fix it, and I'm the only one who's still awake. I'll go poke at the problem; if I can't fix it, one of the people who can should be up in a few hours.

EDIT: Code push is complete! Please let us know if you notice any issues.

I add my voice to the chorus of users for whom LJ-crossposting is now no longer working. So far two attempts have failed; I have no error messages, but no crossposts, either. Do you have any idea if it's the sort of issue that will correct itself if the problem is fixed—the crossposts will eventually come through, just not any time in the immediate future—or if it will require redoing from scratch? Thank you very much.

Working on fixing the problem now! Only problem is that I'm the only one awake and I'm not 100% sure I know how to fix it, so it may have to wait a few hours for someone who does know what they're doing to flip the right switches.

I'm not positive, but I *think* the crossposts will fill back in once the workers are restarted. If I'm wrong, I'll come back and tell you.

I'm not positive, but I *think* the crossposts will fill back in once the workers are restarted. If I'm wrong, I'll come back and tell you.

I appreciate it! Thank you for attempting a fix.

And fixing it is beyond my capabilities, so I've texted Mark -- if he doesn't wake up for the text, Robby or Jen should be awake in a few hours to kick!

I shall be patient ;-)

Victory!

(And thank you!)

Edited (Now with added gratitude) 2016-04-10 13:35 (UTC)

Yes, if this is a workers-aren't-running problem then once they get kicked into action they should clear out the queue!

unsure whether this change is due to the recent code-push or our weird setup or something else, but huge gratitude for the fact that the 'entry posted' page now specifies which of our custom filters the entry is visible to. that was extremely stressful and a major anxiety source for us before when it just said "posted with custom access" without specifying, so this is an enormous relief and a massive improvement. we're really, really appreciative!

so if that was you folks, THANK YOU YOU ARE AWESOME <3 <3 <3

OMG, IT DOES?!

WHOOOOOOOOOOOOOOOOT!!!!

Adding my <3<3<3<3s to

beasta_and_men's!

Yep, that was this code push! I'm delighted you like it :-)

yeah, it's awesome! :DDD

i mean we completely understood why it didn't specify before and we never expected it to, i realized after

ilyena_sylph replied that we didn't put that in the original comment. x3 but yeah this was a super-cool unexpected bonus, and we really love it! :D thankyou <3

~marki

It was something I'd been wanting and I'm super excited that I'm getting to the point with coding where a lot of the time, with stuff like this, I can go "hmm, wouldn't it be nice if..." and actually make it happen. Other people enjoying it too is a really nice bonus. :D

Hurray code push! Great to see the HTTPS work and all the miscellaneous UX improvements.

A new issue: my reading page won't finish loading when I load or reload it. I took a quick look at the console and there's no obvious culprit; it looks like the requests that were made all got responses. I have to click the "Stop loading this page" button to stop the spinny icon at the top of the tab. I'm using Firefox 44.0.

I wonder if this might have also been related to our certificate update issues? I haven't seen any other reports of this, and I'm not seeing any similar behavior on my end. If it keeps happening, open a support request so we can investigate further? Thanks!

Whatever it was, it's stopped now. \o/

However, I've now been seeing a lot of Cloudflare DNS errors over the past couple of days when I try to access my reading page, my entries, and other people's entries. The error code is "Error 1001 DNS resolution error".

Yeah, we've been moving some services around, which causes problems related to propagating DNS changes. I'm told that refreshing the page while holding down the shift key is a thing to try that might help.

Ok, great, known issue. :)

I'm having security certificate woes:

dw-maintenance.dreamwidth.org uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported. Error code: SEC_ERROR_UNKNOWN_ISSUER

I'm getting that for every user, near as I can tell, not just dw-maintenance.

Debian/KDE, Firefox 45 with NoScript (Dreamwidth is whitelisted) and HTTPS Everywhere and Privacy Badger and Ghostery and uBlock Origin and other add-ons but those are the ones I can think of that might matter.

Edited (dx info) 2016-04-10 19:40 (UTC)

I second this. This is very frustrating as I have to add exceptions for each user.

Mark is in the process of updating our SSL certificates. If the error isn't fixed yet, it should be sometime in the next few hours.