Title: Jessica's Replies | WordPress.org

---

# Jessica

  [  ](https://wordpress.org/support/users/leadstartorg/)

 *   [Profile](https://wordpress.org/support/users/leadstartorg/)
 *   [Topics Started](https://wordpress.org/support/users/leadstartorg/topics/)
 *   [Replies Created](https://wordpress.org/support/users/leadstartorg/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/leadstartorg/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/leadstartorg/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/leadstartorg/engagements/)
 *   [Favorites](https://wordpress.org/support/users/leadstartorg/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)

1 [2](https://wordpress.org/support/users/leadstartorg/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/leadstartorg/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[AI Engine - The Chatbot, AI Framework & MCP for WordPress] Conflict Between AI Engine & NotificationX Causes Guest PHP Sessions](https://wordpress.org/support/topic/conflict-between-ai-engine-notificationx-causes-guest-php-sessions/)
 *  [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [7 months, 1 week ago](https://wordpress.org/support/topic/conflict-between-ai-engine-notificationx-causes-guest-php-sessions/#post-18662911)
 * If you do not mind, please can you explain/share how you confirmed that the AI
   Engine plugin is not apart of the problem?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[AI Engine - The Chatbot, AI Framework & MCP for WordPress] Conflict Between AI Engine & NotificationX Causes Guest PHP Sessions](https://wordpress.org/support/topic/conflict-between-ai-engine-notificationx-causes-guest-php-sessions/)
 *  [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [7 months, 1 week ago](https://wordpress.org/support/topic/conflict-between-ai-engine-notificationx-causes-guest-php-sessions/#post-18662313)
 * Any update on the fix because WordPress support states the problem still exists:
 *     ```
       You'll want to thoroughly review any custom code for inefficiencies as it's outside our Scope of Support. That said, we can tell you that our built-in caching is not working and bypassed from PHP sessions always being created on every page load as well as cookies being set named guest_id and mwai_session_id. These cookies are from the following plugins:
       ai-engine
   
       We'd recommend deleted or modifying these plugins to not set cookies if you want cache to work. Afterwards, you could then determine where the PHP sessions are being created in your code. This guide outlines a general process for checking cookies/sessions that will break cache causing performance issues: https://developer.wordpress.com/docs/troubleshooting/site-performance/#7-practical-steps-to-optimize-ttfb-on-wordpress-com
   
       Searching for session_start functions in plugins, these are just a few you may want to test deactivating to see if cache then works: 
       ai-engine
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Yoast SEO Autoredirects](https://wordpress.org/support/topic/yoast-seo-autoredirects/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/yoast-seo-autoredirects/#post-18058439)
 * I used these filters to disable auto redirection: [https://developer.yoast.com/customization/yoast-seo-premium/disabling-automatic-redirects-notifications/](https://developer.yoast.com/customization/yoast-seo-premium/disabling-automatic-redirects-notifications/)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Simple History – Track, Log, and Audit WordPress Changes] Tracking User login Activity](https://wordpress.org/support/topic/tracking-user-login-activity/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/tracking-user-login-activity/#post-18049921)
 * Again, I only allow WordPress backend and SSH (FTP not setup) through my dedicated
   IP address. I have the latest version of WordPress, Apache server, and a treasure
   trove of plugins, but none that should effect the log history.
 * I also audit through Papertrail and they do not have the attempt either in the
   access log.
    -  This reply was modified 1 year, 7 months ago by [Jessica](https://wordpress.org/support/users/leadstartorg/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Filter Robots Text File](https://wordpress.org/support/topic/filter-robots-text-file/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/filter-robots-text-file/#post-18048322)
 * [https://wordpress.org/support/topic/disable-robots-txt-changing-by-yoast-seo/](https://wordpress.org/support/topic/disable-robots-txt-changing-by-yoast-seo/)
   
   [https://github.com/Yoast/wordpress-seo/issues/19161](https://github.com/Yoast/wordpress-seo/issues/19161)
 * The question pertained to whether this feature could be incorporated in the upcoming
   release. I have already found a solution. The rationale behind its importance
   is that display errors were appearing in the robots.txt file, which is problematic.
   It would be more effective to maintain a static text file.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] XML Sitemap Invalid Date](https://wordpress.org/support/topic/xml-sitemap-invalid-date/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/xml-sitemap-invalid-date/#post-18048274)
 * I had one year of technical support, and they intentionally made my debug.log
   public, which makes me skeptical. I would rather address this through the WordPress
   forum.
 * I was able to fix the issue by switching plugins and tried to assist in improving
   the plugin with additional features. No health check is necessary.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Two Factor] How to reset](https://wordpress.org/support/topic/how-to-reset-10/)
 *  [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/how-to-reset-10/#post-18046347)
 * This is database work!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Two Factor] How to reset](https://wordpress.org/support/topic/how-to-reset-10/)
 *  [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/how-to-reset-10/#post-18046345)
 * Identify Relevant Meta Keys: You want to delete the following meta keys:
    _two_factor_nonce
   _two_factor_last_login_failure _two_factor_failed_login_attempts _two_factor_fido_u2f_register_request
   _two_factor_backup_codes _two_factor_enabled_providers _two_factor_provider
 * Run SQL Queries to Delete 2FA Data: You can delete the data for the specific 
   user by running the following SQL queries. Replace 1 with the actual user_id 
   of the user affected.
 * Run SQL Queries:
 *     ```
       DELETE FROM wp_usermeta WHERE user_id = 1 AND meta_key = '_two_factor_nonce';
       DELETE FROM wp_usermeta WHERE user_id = 1 AND meta_key = '_two_factor_last_login_failure';
       DELETE FROM wp_usermeta WHERE user_id = 1 AND meta_key = '_two_factor_failed_login_attempts';
       DELETE FROM wp_usermeta WHERE user_id = 1 AND meta_key = '_two_factor_fido_u2f_register_request';
       DELETE FROM wp_usermeta WHERE user_id = 1 AND meta_key = '_two_factor_backup_codes';
       DELETE FROM wp_usermeta WHERE user_id = 1 AND meta_key = '_two_factor_enabled_providers';
       DELETE FROM wp_usermeta WHERE user_id = 1 AND meta_key = '_two_factor_provider';
       ```
   
 * These queries will delete the 2FA-related data for the user with user_id = 1.
   Make sure to adjust the user_id if needed.
 * Verify the Deletion: After running the queries, you can verify that the rows 
   have been deleted by running:
    SELECT * FROM wp_usermeta WHERE user_id = 1 AND
   meta_key LIKE ‘_two_factor%’;
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] XML Sitemap Invalid Date](https://wordpress.org/support/topic/xml-sitemap-invalid-date/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/xml-sitemap-invalid-date/#post-18045896)
 * The last mod date is not necessary, no option to remove from sitemap: [https://www.seroundtable.com/google-lastmod-xml-sitemap-20579.html](https://www.seroundtable.com/google-lastmod-xml-sitemap-20579.html)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] SSL does not stay activated](https://wordpress.org/support/topic/ssl-does-not-stay-activated/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/ssl-does-not-stay-activated/#post-16396435)
 * Great, thank you.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] SSL does not stay activated](https://wordpress.org/support/topic/ssl-does-not-stay-activated/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/ssl-does-not-stay-activated/#post-16396372)
 * No, I got the plugin from the WordPress repository and the pro plugin from the
   plugin website.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] SSL does not stay activated](https://wordpress.org/support/topic/ssl-does-not-stay-activated/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/ssl-does-not-stay-activated/#post-16396260)
 * Error: ‘update_option’ is not a registered subcommand of ‘rsssl’.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] SSL does not stay activated](https://wordpress.org/support/topic/ssl-does-not-stay-activated/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/ssl-does-not-stay-activated/#post-16396216)
 * Also my SSL is good: [https://www.ssllabs.com/analyze.html?d=domain.org&latest](https://www.ssllabs.com/analyze.html?d=domain.org&latest)
    -  This reply was modified 3 years, 3 months ago by [Jessica](https://wordpress.org/support/users/leadstartorg/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] SSL does not stay activated](https://wordpress.org/support/topic/ssl-does-not-stay-activated/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/ssl-does-not-stay-activated/#post-16396197)
 * I SSHed into my server and ran the command as requested:
 * `sudo wp rsssl activate_ssl`
 * I get Success: SSL activated successfully
 * I refresh my dashboard in WordPress.
    domain.org/wp-admin/options-general.php?
   page=really-simple-security#dashboard
 * Again, stuck at 25% progress, and SSL is not active.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] SSL does not stay activated](https://wordpress.org/support/topic/ssl-does-not-stay-activated/)
 *  Thread Starter [Jessica](https://wordpress.org/support/users/leadstartorg/)
 * (@leadstartorg)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/ssl-does-not-stay-activated/#post-16396184)
 * The dashboard does have a popup and I click ‘Activate SSL.’
 * I activate and the progress moves to 45% complete in the dashboard.
    There is
   a warning and it says my wp-config.php is not writable.
 * I SSH into my server and change the file permissions for wp-config.php to 644
   and add the SSL cookie session settings and load balancing fix to the file:
 * [https://really-simple-ssl.com/wp-config-fix-needed](https://really-simple-ssl.com/wp-config-fix-needed)
 *     ```
       //Begin Really Simple SSL session cookie settings
       @ini_set('session.cookie_httponly', true);
       @ini_set('session.cookie_secure', true);
       @ini_set('session.use_only_cookies', true);
       //END Really Simple SSL cookie settings
   
       //Begin Really Simple SSL Load balancing fix
       $server_opts = array("HTTP_CLOUDFRONT_FORWARDED_PROTO" => "https", 
       "HTTP_CF_VISITOR"=>"https", "HTTP_X_FORWARDED_PROTO"=>"https", 
       "HTTP_X_FORWARDED_SSL"=>"on", "HTTP_X_FORWARDED_SSL"=>"1"); foreach( $server_opts 
       as $option => $value ) { if ((isset($_ENV["HTTPS"]) && ( "on" == $_ENV["HTTPS"] )) 
       || (isset( $_SERVER[ $option ] ) && ( strpos( $_SERVER[ $option ], $value ) !== 
       false )) ) {
       $_SERVER[ "HTTPS" ] = "on";
       }
       }
       //End Really Simple SSL
       ```
   
 * I restart Apache and reboot my server.
    I refresh the dashboard page – wp-admin/
   options-general.php?page=really-simple-security#dashboard
 * SSL progress is at 25% and NOT active, it is no longer at 45%.
    I tried the process
   multiple times and cannot keep it active. Are there any compatibility issues 
   with any plugins listed on the systems report?
    -  This reply was modified 3 years, 3 months ago by [Jessica](https://wordpress.org/support/users/leadstartorg/).

Viewing 15 replies - 1 through 15 (of 20 total)

1 [2](https://wordpress.org/support/users/leadstartorg/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/leadstartorg/replies/page/2/?output_format=md)