TechiCrunch

When an API request fails due to request errors or server errors, an error response message is returned in JSON format. An error response message is returned in JSON format even for endpoints that support other MIME types. The error response message includes error message itself, a description of the error, a unique error code for the endpoint, an HTTP response message, and an HTTP response code. The error response includes following fields: message : the error message details : a field for additional information, which may or may not be populated description : description of the specific error code : Unique error response code http_response : message : HTTP response message code : HTTP response status code For example, the following API request attempts to get information about a non-existent reference set that is called “test-set” https://<host_ip>/api/reference_data/sets/test_set An HTTP 404 response code and the following JSON error response

Learn how to create a complete backup solution for your Open edX installation. This detailed step-by-step how-to guide covers backing up MySQL and MongoDB, organizing backup data into a single date-stamped tarball zip file, plus how to setup a cron job and how to copy your backups to an AWS S3 storage bucket. Summary The official Open edX documentation takes a laissez faire approach to many aspects of administration and support, including for example, how to properly backup and restore course and user data. This article attempts to fill that void. Implementing an effective backup solution for Open edX requires proficiency in a number of technologies, which is fine if you’re part of a full IT team at a major university, but can this can otherwise be a real obstacle to competently supporting your Open edX platform. Open edX stores course data, including media uploads such as images and mp4 video files in MongoDB. To do this, MongoDB’s co

Follow instructions below: Login to Plesk and make sure that  Allow remote connections from any host option  is enabled in  Tools & Settings > Database Servers > Settings Edit  my.cnf/my.ini  file changing  bind-address  parameter to: bind-address = 0.0.0.0 Also, make that  skip-networking  parameter is not defined. For Linux: /etc/mysql/my.cnf  Debian/Ubuntu /etc/my.cnf  CentOS/CloudLinux/RHEL For Windows: "%plesk_dir%\MySQL\my.ini"  for Plesk databases(port 8306) "%plesk_dir%\Databases\MySQL\my.ini"  for Clients databases(port 3306) After that, restart MySQL server. Login to MySQL server. Note : For the access to client's MySQL server on Windows, use PHPMyAdmin:  Plesk > Tools & Settings > Database Servers - MySQL DB Admin. Grant the access to remote IP address and login to MySQL. For example, if you want to allow access to database called  database  for user  user  with password  password  and remote IP add