9:02 am Full service has been restored. During the disruption, many customers had trouble viewing custom themes and logging in using authentication tools like Shibboleth.
8:00 am We are currently experiencing problems for a few of our US-based customers with any custom themes, custom plugins, and authentication tools such as Shibboleth.
We have identified the problem and are in the process of fixing it. Full service should be restored soon and we will update here once that work is complete.
There is much news going around about a recent bug in Cloudflare which resulted in an extremely small number of Cloudflare customers’ that had the possibility of exposing customer data.
We are a Cloudflare hosting partner and do utilize Cloudflare services, but we are 100% confident that we were not impacted by this bug and that no customer data that we host was compromised for the following reasons:
1. We’ve been assured by Cloudflare that none of the domains we host were impacted, including all CampusPress customers and our Edublogs.org network.
2. We do not leverage the specific Cloudflare services that contained the originally disclosed bug.
3. Even still, we decided to change our authentication keys and force all logged in users to re-login just to ensure no further impact was possible.
The problem is location specific which is why your network was loading for me and not for you. Our team is currently working to resolve performance issues that are affecting some of our customers. We are aware that some sites are not available as a result of upstream network issues at one of our Data Center provider. We are working as quickly as possible to resolve this issue and will update here as soon as we know more. We definitely apologize for this inconvenience.
We had reports of sporadic issues yesterday – there wasn’t any technical downtime, but there were time periods where sites looked funny due to CSS not loading. This was random and didn’t affect all of our customers. The issue was in some files being blocked upstream at the network level. We’ve confirmed with our data center partners that this is fully resolved and shouldn’t be a problem going forward.
Campus Press, UO Blogs host company, has upgraded UO Blogs to WordPress version 4.1.4 to address the XSS vulnerability.
For additional information or questions, please contact the Technology Service Desk (techdesk@uoregon.edu; 541-346-HELP).
On Monday, 02/02/15, at 3AM, the UO Blogs host company, Campus Press, will be modifying this plugin so that logged-in users will see the original site domain (blogs.uoregon.edu/example) when working in the Dashboard area and when viewing the site.
All other users will still see the mapped domain (example.uoregon.edu).
Additionally, please note that UO Blogs has a 5 minute caching period. Therefore, any changes to your site will be visible to logged-out users after 5 minutes.
Please share this message with any other administrators for your UO Blogs site.
If you have any questions about this change, please contact the Technology Service Desk (techdesk@uoregon.edu; 541-346-HELP).
The UO Blogs service will be upgraded on Monday, 12/22/14, from 7:00 to 8:00 a.m.
No service interruption is expected.
For more information:http://status.campuspress.com/2014/12/04/upcoming-wordpress-4-1-update/
This problem was resolved on 8/15 at approximately 11:00AM
——
The Technology Service Desk is aware of the warning message being displayed at the top of user’s Dashboards and on the UO Blogs homepage. We have notified our host company and they are working to resolve this.
For sites with large menus, please be aware that UO Blogs does limit how many menu items a site can have. If you have a menu that has approximately 50 or more items, you may have troubles adding additional menu items.
If your site needs a large amount of menu items, we recommend splitting your items across multiple menus.
On May 10th at 12:00am PST Edublogs, our partner in offering the UO Blogs service, will be making changes to improve the reliability, speed, and resiliency of UO Blogs.
We anticipate 1-2 minutes of downtime during this work.
If you have any questions about this change, please contact the Technology Service Desk (techdesk@uoregon.edu; 541-346-HELP).
