Title: February 2017 – Make WordPress Systems --- # Monthly Archives: February 2017 [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 6:04 pm _on_ February 24, 2017 Tags: [prio2 ( 135 )](https://make.wordpress.org/systems/tag/prio2/) # 󠀁[Marx cPanel License Expired](https://make.wordpress.org/systems/2017/02/24/marx-cpanel-license-expired/)󠁿 When I log in to cPanel, I get a `License not activated` error instead of the normal dashboard. [#prio2](https://make.wordpress.org/systems/tag/prio2/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fsystems%2F2017%2F02%2F24%2Fmarx-cpanel-license-expired%2F%23respond&locale=en_US) * [Clear to-do](https://make.wordpress.org/systems/2017/02/?output_format=md#) [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 4:03 pm _on_ February 20, 2017 Tags: [prio1 ( 83 )](https://make.wordpress.org/systems/tag/prio1/) # 󠀁[Marx blacklisted by Barracuda](https://make.wordpress.org/systems/2017/02/20/marx-blacklisted-by-barracuda/)󠁿 I noticed a legitimate message in the WordCampWordCamp WordCamps are casual, locally- organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). Help Scout account was flagged as spam because `66.155.40.24` is blacklisted by Barracuda. [Lookup](http://barracudacentral.org/lookups/lookup-reputation) | [Removal](http://barracudacentral.org/rbl/removal-request) I can request removal, but it seems like it’ll just get added again if we don’t figure out what outbound messages caused the blacklisting and prevent that from happening again. [#prio1](https://make.wordpress.org/systems/tag/prio1/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fsystems%2F2017%2F02%2F20%2Fmarx-blacklisted-by-barracuda%2F%23respond&locale=en_US) * [Clear to-do](https://make.wordpress.org/systems/2017/02/?output_format=md#) [ ](https://profiles.wordpress.org/ocean90/) [Dominik Schilling](https://profiles.wordpress.org/ocean90/) 3:58 pm _on_ February 19, 2017 Tags: [prio2 ( 135 )](https://make.wordpress.org/systems/tag/prio2/) # 󠀁[nginx rewrite from `/forums` to `/support`](https://make.wordpress.org/systems/2017/02/19/nginx-rewrite-from-forums-to-support/)󠁿 For two international forums I need a nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. [https://www.nginx.com/](https://www.nginx.com/). rewrite from `/forums` to `/support`. * https://ary.wordpress.org/forums -> https://ary.wordpress.org/support * https://it.wordpress.org/forums -> https://it.wordpress.org/support That seems to be something for the `wporg-rosetta` config: ```notranslate location = /forums { return 301 /support/; } location ~ ^/forums/(.*) { return 301 /support/$1; } ``` Not sure if we need to restrict that to the both hosts. We have a similar rule for wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)/forums. Once the configs are deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. the site URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org needs to be updated as well: * https://global.wordpress.org/ wp-admin/network/site-info.php?id=332 * https://global.wordpress.org/wp-admin/network/ site-info.php?id=352 Could someone please add the rules if they are looking good? Thank you! [#prio2](https://make.wordpress.org/systems/tag/prio2/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fsystems%2F2017%2F02%2F19%2Fnginx-rewrite-from-forums-to-support%2F%23respond&locale=en_US) * [Clear to-do](https://make.wordpress.org/systems/2017/02/?output_format=md#) [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 1:19 am _on_ February 18, 2017 Tags: [prio3 ( 86 )](https://make.wordpress.org/systems/tag/prio3/) # 󠀁[Whitelisted WordCamp Production Data for Dev Environments](https://make.wordpress.org/systems/2017/02/18/whitelisted-wordcamp-production-data-for-dev-environments/)󠁿 Right now WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). devs use a small subset of the production database that was manually created, because it wouldn’t be safe to keep copies of the production database in local environments. That works good enough for most things, but we keep running into situations where reproducing bugs and testing fixes is much harder, and takes much longer, than it would if we had real-world data to work with. So, I’d like to create a way to safely use a whitelisted copy of production data in local environments. Here’s how I envision it working: 1. Create a script that runs on the production web server once a day 2. It would create a copy of the primary database on the production database server 3. Then run lots of SQL commands against that copy in order to redact anything that hasn’t been whitelisted 4. Have another script in dev environments that uses `sftp` to download a copy of the whitelisted database once a day The whitelist would contain a list of tables, columns, and keys that have been determined to not have any sensitive data. For example: * `wp_users` – The table itself would be whitelisted, but only the `ID`, `user_login`,` user_nicename`, `user_registered`, `user_status`, `display_name`, `spam`, and` deleted` fields would be whitelisted. Because `user_pass`, `user_email`, and ` user_activation_key` would _not_ be in the whitelist, the script would replace the contents of those columns with `[redacted]` (or in the case of `user_email`,` redacted@example.org`). * `wp_usermeta` – The table itself would be whitelisted, along with the `umeta_id`,` user_id`, `meta_key`, and `meta_value` columns, but only certain `meta_key` rows would be whitelisted. For instance, `first_name`, `last_name`, `description`, and `wp_capabilities` would be whitelisted, but `session_tokens` and `wordcamp- qbo-oauth` would not be. Additionally, the script would have some logic to redact potentially sensitive values within whitelisted columns. For example, any e-mail addresses inside a `meta_value` value would be replaced with `redacted@example.org`. What does Systems think about that? I’d do all the work to build the script, but I want to make sure you don’t have any security/privacy concerns. [#prio3](https://make.wordpress.org/systems/tag/prio3/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fsystems%2F2017%2F02%2F18%2Fwhitelisted-wordcamp-production-data-for-dev-environments%2F%23respond&locale=en_US) * [Clear to-do](https://make.wordpress.org/systems/2017/02/?output_format=md#)