Just adding to Septa's response, I believe this plugin is being disabled right on startup, which then prevents you from re-enabling it via Confluence Admin > Plugins. If that's the case, you're probably hitting some sort of timeout upon starting up Confluence as explained here.
So if the above suggestions does not work, you may want to increase the timeout value for plugins to a higher value by adding the JVM parameter
-Datlassian.plugins.enable.wait=300 in the <confluence-install>/bin/setenv.bat or .sh (if using linux). Please restart Confluence to reflect the changes.
Hope it helps.
First and foremost, we would need to ensure that the issue is not caused by corrupted plugin cache by refreshing it. Please try to clear plugin cache and see if it helps.
Another troubleshooting steps to try if the above does not help is to enable plugin safe mode. If the above steps still not help we recommend you to create a support ticket on our support channel so that we could review your logs, and configuration privately.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
To anyone who doubts that Atlassians are a little too obsessed with collaboration, and tools related thereto, let me describe a recent discussion we had (which took place on our internal Confluence, ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs