My bad, just fixed that, but the error persists. That is what is added on my wp-config.php with some hidden information here for security reasons:
/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
define('WP_REDIS_CLIENT', 'pecl');
define('WP_REDIS_HOST', 'localhost');
define('WP_REDIS_PORT', '6379');
define('WP_REDIS_MAXTTL', '86400');
define( 'WP_REDIS_SERIALIZER', Redis::SERIALIZER_IGBINARY );
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
define('FS_METHOD', 'direct');
define('FS_CHMOD_DIR', (0755 & ~ umask()));
define('FS_CHMOD_FILE', (0664 & ~ umask()));
/* Multisite */
define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', 'xxx');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);
define('ESITES_PARENT_SITE_ID', xxx);
define( 'xxx_xxxx_PATH', 'wp-content/themes/xxx' );
define('COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] );
//set_time_limit(60);
/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
What could be causing the issue if not something at this peace of code? Thank you! ??