Title: cannot activate return fatal error Last modified: August 20, 2016 --- # cannot activate return fatal error * Resolved [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/) * cannot activate return fatal error * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/) Viewing 13 replies - 1 through 13 (of 13 total) * Thread Starter [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185295) * Any updates on this my site is community.mis.temple.edu, we are using the genesis theme. This is very critical for our department, please provide any assistance possible. * Thanks Manoj * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185326) * Uninstall the plugin and reinstall through the dashboard. If the plugin still produces an error, you will have to check your server’s error log for the actual error. * Thread Starter [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185352) * This is the error * Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 57 bytes) in E:\xampp\htdocs\wp-includes\meta.php on line 571 * [esmi](https://wordpress.org/support/users/esmi/) * (@esmi) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185353) * Try [increasing the memory available to PHP](http://wordpress.org/support/topic/253495#post-1017842). * Thread Starter [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185354) * still did not work * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185365) * If the error is the same, you either didn’t increase the memory limit enough, or you did not increase the memory limit. * Thread Starter [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185371) * My memory limit is currently set to 256M, I had increased it to 384M. * But my question is why would it require that much memory to run this? * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185372) * The more plugins you use, the more memory is used. The more links and elements that are on your site, the more memory WordPress HTTPS will use. * Thread Starter [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185376) * I still get a similar error. I think I figured out the problem. * The wordpress admin memory limit, limiting it. Why would this script take more than the admin memory limit. * Thread Starter [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185377) * I increased it from 256 (which was the admin memory limit) to 384 * message changed, looks like even that was not enough.I am kind worried increasing it because it might cause a performance issue? * Any suggestion? * Thread Starter [Manoj Chacko](https://wordpress.org/support/users/mjc82in/) * (@mjc82in) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185378) * I increased it from 256 (which was the admin memory limit) to 384 * message changed, looks like even that was not enough.I am kind worried increasing it because it might cause a performance issue? * Any suggestion? * [Michael](https://wordpress.org/support/users/eizzumdm/) * (@eizzumdm) * [13 years, 7 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185384) * I was using WordPress 3.4.2 and WordPress HTTPS 3.2.2. * After upgrading from WordPress HTTPS 3.2 to 3.2.2, I started getting error 500s when I tried to create new sites in a WordPress multisite environment. Even though the site was created, my custom settings defaults were not carried over to the new sites (I use the wpmu-new-blog-defaults plugin for that). I confirmed the problem only occurred when WordPress HTTPS was active in my dev environment, so I de-activated the plugin on our production environment, and confirmed the same thing there. * We bumped up the memory via php.ini, but I could not re-activate the WordPress HTTPS plugin. On our QA system, I got the error “Fatal error: Allowed memory size of 268435456 bytes exhausted,” so I figured that had to be default WP_MAX_MEMORY_LIMIT of 256M. I added the WP_MAX_MEMORY_LIMIT directive to my wp-config file and increased the value to 512M, and got another fatal error, 536870912 bytes exhausted. I increased the value 1024M, and I was finally able to activate the plugin. * I tried the same thing on our production environment with a memory limit of 1024M; however, I got a “504 Gateway Time-out” error from our nginx proxy server after 120 seconds. * My question is whether the new Network Settings feature causes the WordPress HTTPS to utilize an extraordinary amount of memory and time to activate if there are many sites in the network. My QA environment database hasn’t been synched in awhile and only has 72 sites. My Production environment has 107 sites. * Similarly, on the Network Settings page for WordPress HTTPS, I was able to set the “New Site Defaults” on an environment with only a dozen blogs. However, trying to set the “New Site Defaults” on my aforementioned QA and Prod environments caused the little spinner donut to spin and spin. I even let it spin for 10 minutes, but still could not change those settings. * I downgraded WordPress HTTPS to version 3.2 on my production environment. I was able to activate the plugin with WP_MAX_MEMORY_LIMIT set to only 256M. I was also able to create new sites once again without error. * I really love this plugin. It is the only one that reliably knocks out the secure and insecure content warnings over https. I hope that my lengthy issue report can help with the further development of this plugin. * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 6 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185417) * I don’t see any reason that the plugin should be using that much memory just to set settings on multiple blogs. The code I’m using is pretty straight forward, so I’m not sure what’s going on. I’ll set up some tests on my site and see what I can figure out. Thanks for the feedback. Viewing 13 replies - 1 through 13 (of 13 total) The topic ‘cannot activate return fatal error’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/wordpress-https_bec2c9.svg) * [WordPress HTTPS (SSL)](https://wordpress.org/plugins/wordpress-https/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-https/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-https/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-https/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-https/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-https/reviews/) * 13 replies * 4 participants * Last reply from: [mvied](https://wordpress.org/support/users/mvied/) * Last activity: [13 years, 6 months ago](https://wordpress.org/support/topic/cannot-activate-return-fatal-error/#post-3185417) * Status: resolved