[Support request] Multisite all sites down after activating ssl on main site

Home Forums Multisite Multisite all sites down after activating ssl on main site

Tagged: 

This topic contains 10 replies, has 3 voices, and was last updated by  allansoll4@gmail.com 3 months, 1 week ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #225573 Reply

    Hi there,

    our multisite main domain is wpmss-multisite.com and sub domain is wpmss.wpmss-multisite.com. We had activated really simeple ssl plugin and activated it site by site for most of our sites(5). All worked well and no major issues besides mixed content. However, after activating your ssl plugin on our main domain(wpmss-multisite.com) the whole network went down. We have tried force-deactivate.php option but still no luck. We get simple http 500 error with no option to inspect. What could have gone wrong? needless to say we need a quick fix to this. Help, please!

    #225588 Reply

    Hi,

    When I check your main domain, I get a certificate error. If you add the main domain as common name to your certificate, I would expect the issue to be fixed.

    #225631 Reply

    Hi Rogier, thank you for your quick reply. That is the issue, here is the list of certificates we have. these are all per site certificates, no wildcard certificates. We can’t see any issue with certificates though. A

    Found the following certs:
    Certificate Name: wpmss-multisite.com
    Domains: wpmss-multisite.com
    Expiry Date: 2019-08-13 11:53:26+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/wpmss-multisite.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/wpmss-multisite.com/privkey.pem
    Certificate Name: wpmss.com
    Domains: wpmss.com http://www.wpmss.com
    Expiry Date: 2019-08-13 12:04:18+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/wpmss.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/wpmss.com/privkey.pem
    Certificate Name: flyharmony.com
    Domains: flyharmony.com http://www.flyharmony.com
    Expiry Date: 2019-08-13 12:02:19+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/flyharmony.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/flyharmony.com/privkey.pem
    Certificate Name: sydone.com
    Domains: sydone.com sydone.wpmss-multisite.com http://www.sydone.com
    Expiry Date: 2019-08-13 12:06:47+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/sydone.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/sydone.com/privkey.pem
    Certificate Name: cool2fly.com
    Domains: cool2fly.com
    Expiry Date: 2019-08-13 11:41:59+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/cool2fly.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/cool2fly.com/privkey.pem

    #225649 Reply

    Hi,

    When I check your main domain I see this:
    https://www.ssllabs.com/ssltest/analyze.html?d=wpmss-multisite.com

    It looks like the certificate is not installed correctly somehow.

    #225802 Reply

    Hi,

    Yes, there was a server name mismatch and we have changed now the server name on vm. It seems to be now configured correctly. Still, no change in accessing the site or being able to deactivate really simeple ssl plugin.

    #225804 Reply

    Mark Wolters
    Keymaster

    Since the main domain (wpmss-multisite.com) now returns an http 500 error, you can try to enable debugging in WordPress by adding the following lines to your wp-config.php file:

    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_LOG’, true);

    This will write any possible PHP/WordPress errors to a debug.log file in your /wp-content/ folder and might provide more information about the cause of your issue.

    #225805 Reply

    Thank you. We have these lines already in our wp-config file
    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );
    define( ‘WP_DEBUG_DISPLAY’, true);
    However, no log created. A

    #225815 Reply

    Hi again,

    do you have any ideas what might have gone wrong? The last time we were able to access the sites through wp-admin and last click was to activate really simple ssl plugin on our main site. All the other sites had the plugin activated for few days. We need to solve this but are running out of ideas? A

    #225824 Reply

    Mark Wolters
    Keymaster

    If the debug.log file remains empty it’s possible something else is causing your issue, likely on the server level. PHP/WordPress related errors should be written to the debug.log file. Do you have an error_log file in your websites main folder? Or can you access the Apache/Nginx error logs from your hosting provider?

    Mark

    #225828 Reply

    we don’t have error_log file on our website main folder but we have access to Apache error logs. Any particulars you might suggest? We have not made any changes to the system though? A

    #225831 Reply

    Never mind. The issue was solved with a full server restart together with db restarts. Sites are now available. Now we need to roll back to the old version and recreate the sll activation. Thank you!

Viewing 11 posts - 1 through 11 (of 11 total)
Reply To: Multisite all sites down after activating ssl on main site
Your information: