![]() However, switching “Verify SSL certificate (optional)” off allowed the dashboard to connect so it’s finally all working, even if I don’t really understand what the issue was in the first place.Working solo on a project or working with a team locally, it may make sense to run WordPress locally on your PC.ĭevelopment environments have grown in parallel with technology growth, between improved internet speeds and the remote teams a lot of development and testing environments have gone to the cloud. I wondered if this was being blocked by Wordfence on the child site so I temporarily deactivated it but that wasn’t the cause. For additional help, contact the MainWP Support.” “MainWP Child Plugin not detected! Please make sure that the MainWP Child plugin is installed and activated on the child site. However, I reinstalled Local for all users and after adding Local.exe as an exclusion in Kaspersky, I copied the openssl.cnf file I found in WPVivid (I reckoned this might do as a starting point) and placed it in C:\Users\\Local Sites and pointed the Quick Setup Wizard to that file, it all seems to work – I no longer get that error. I realised that Local was installed just for me rather than for all users – I’m not sure why I did that when I installed it. If C:\usr\local\ssl/openssl.cnf is actually the path MainWP wants to use, can I create that directory and copy an openssl.cnf file into it? Is there a way of creating that file? I have also posted on the Local by Flywheet support forum as I don’t really know where the issue lies but not had a definitive answer yet, just someone on a mac with the same error. I think a fundamental question is whether I should be selecting Linux or Windows. If I try to add a site without using a Unique security ID, I still get the same error and the same dashboard warning. If I continue anyway, I get the same error on the MainWP dashboard pages. If I disable the ‘valid SSL’ option, I get the same (the site does have a valid SSL cert – and all the parameters are correct). For additional help, contact the MainWP Support. MainWP Child Plugin not detected! Please make sure that the MainWP Child plugin is installed and activated on the child site. Just to see what happens, I did enter that as the location of the openssl.cnf file but when I click on Connect, I get: If I look at the phpinfo page (linked to in Local), it tells me the location should be C:\usr\local\ssl/openssl.cnf but there is no such location – that’s a Linux path. I’d found that page but none of the options seems to apply: there is no xampp/wampp directory. To save me running around in circles, has anyone come across this and can you tell me what I’m missing? ![]() However, I think Windows Defender may have taken over instead. I did wonder if my Kaspersky security was blocking Local but I added Local as a trusted application (I’ve tried many combinations of the various options) and even with Kaspersky disabled, I get the same error. I assume the reason I can’t connect to the child has something to do with this warning but I’m stuck. However, if I choose Windows, it asks for the location of the OpenSSL.cnf file, which I cannot locate – I’ve seen several threads on this but they didn’t seem to answer it for me. I’m running it on a W10 PC but I *think* Local provides a Linux environment, that’s what I chose in the wizard. I don’t get this on the wp-admin dashboard. ( ! ) Warning: openssl_pkey_export(): cannot get key from parameter 1 in C:\Users\livec\Local Sites\mainwp\app\public\wp-content\plugins\mainwp\pages\page-mainwp-server-information-handler.php on line 216 I can install the MainWP dashboard but when I run through the Quick Setup Wizard and try to add a site, it says the child plugin can’t be found but when I finish the wizard, I get this warning at the top of the dashboard regardless of which MainWP page I’m on: I have other sites running perfectly well. ![]() I have created a local site to run MainWP in Local by Flywheel.
0 Comments
Leave a Reply. |