Hey folks! It looks like…

Hey folks! It looks like all outgoing e-mail via our SupportPress install on WordCamp.org (support.wordcamp.org) is broken. I’m getting the following error when attempting to send manually via wp_mail():

SMTP Error: Could not connect to SMTP host.

Let me know if you need any additional details, and thanks!

There’s a virus message on…

There’s a virus message on the wp-testers mailing list archive.

http://lists.automattic.com/pipermail/wp-testers/2016-June/014659.html

low priority Another #https report came in this…

(low-priority) Another #https report came in, this time for https://svn.buddypress.org/ which is not using the buddypress cert, but rather than WordPress.org wildcard.

https://wordpress.slack.com/archives/buddypress/p1465520101000488

Although https://buddypress.svn.wordpress.org/ is the canonical SVN location, https://svn.buddypress.org/ shows up in search results and is affected by the HTTPSEverywhere-type browser extensions too.

502 Bad Gateway errors

The number of reports for 502 Bad Gateway errors is increasing recently.

My first report for 502 errors was for https://*.wordpress.org/?fetch-custom-header=/plugins/ requests on Jan 7th. This was solved by @barry, “some memory corruption probably caused by a bug in pecl-memcache that we are working on fixing“.

Around April 3rd I got a few reports for translate.wordpress.org but couldn’t confirm them.

On April 13th I reported that the https://*.wordpress.org/?fetch-custom-header=/plugins/ issue happens again. This issue is still there, see #dotorg-warnings.

Since this Monday we’re getting reports for 502 Bad Gateway errors on our make sites. For example  https://make.wordpress.org/polyglots/feed/p2.ajax returns a 502 which prevents adding new comments.

502

But there are also new reports for translate.wordpress.org (when submitting translations) and for localized sites:

Image 2016-06-07 at 9.56.15 am

The 502 errors do not happen on our sandboxes, only in production. Can someone please look into this? Thank you!

Low priority It looks like https security wordpress…

(Low-priority) It looks like https://security.wordpress.org doesn’t act the same as http://security.wordpress.org:

http: (note: p2 automatically https’s the below urls, edit post to see raw)
$ curl -IL https://security.wordpress.org/ | grep Location
Location: https://codex.wordpress.org/FAQ_Security
Location: https://make.wordpress.org/core/handbook/reporting-security-vulnerabilities/
Location: https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/

https:

  • invalid cert (multipattern)
  • redirect to default cpanel URL

The URL is used as a shorthand in some documentation AFAIK, mentioned to me by @netweb who uses HTTPS Everywhere which triggered this.

Could I please have the en US utf8…

Could I please have the en_US.utf8 locale setup on my sandbox please?

I need it to finish the work on the Plugin Directory ZIP/SVN handling with non-ASCII filenames.

For reference, locale -a only lists C, C.UTF-8, POSIX currently, while I know production and some other sandboxes have en_US.utf8.

As a new member of the community team…

As a new member of the community team, I’m needing Super Admin access for the wordcamp.org network. My WordPress.org username is hlashbrooke.

Posting on behalf of @julia ullrich We need…

Posting on behalf of @julia.ullrich. We need proxy access for Lauren Zarzycki (.org username @laurenzarzycki) and trusted deputy access on the wordcamp.org network. She needs to access the payment dashboard in the network admin, as well as individual payments/reimbursements on each WordCamp event site for bookkeeping purposes.

Her public key is:

Thanks!

#proxy, #wordcamp-org

mail.wordcamp.org disk space

We’re getting low on disk space for mail.wordcamp.org again; it was down to ~2 GB today. I pruned some things and got it back up to ~6 GB, but wanted to get the ball rolling on a long-term solution.

The Community Team has discussed this in the past and decided that we’d strongly prefer to not delete old messages, because we sometimes need to go back and reference them. For Central’s accounts, there are also some legal restrictions around contracts, etc that need to be kept.

The last time this happened, sysmonk increased the space from 20 GB to 50 GB, but we’ve used that up in the past two years. We’re expecting to have about 125 WordCamps this year, and that’s growing 10% – 15% each year, so I don’t think the current solution is going to work for much longer, unless we can get a much larger chunk of the 300 GB available on the server.

What kind of options would you recommend? It might be good to answer the SSL/webmail question first, since we might end up migrating to Google Apps or something if modern webmail isn’t an option.

#disk-space, #mail, #wordcamp-org

It looks like WordPress org doesn’t use ALPN…

It looks like WordPress.org doesn’t use ALPN for negotiating the connection encryption. Chrome is dropping support for NPN next month, so it’d be nice if we could upgrade before then.

#nginx