<p>The issue for this case was something related to my composer not installing it correctly. I downloaded the most recent version of Craft straight from the site and I don't face any of the above issues.</p>

CC BY-SA 4.0
2019-03-08T22:27:24.190Z
I believe it may have been your ```composer.lock``` file
bshelling
CC BY-SA 4.0
2019-03-12T16:03:45.967Z
I did think this also, but again this gave me a deadend
Amy
CC BY-SA 4.0
2019-03-07T12:23:26.723Z
2019-03-07T12:23:26.723Z
Amy
<p>For future reference, I had the same error and resolved it with Craft Support.</p>

<p>In my case the project.yaml file got out of sync with what was in the database.</p>

<p>Running craft project-config/rebuild from the project's root resolved the issue and allowed us to re-enable the plugins</p>

CC BY-SA 4.0
2019-06-02T16:04:06.063Z
Thanks. That resolved my issue.
Fred
CC BY-SA 4.0
2019-06-26T10:09:29.423Z
This fixed my issue. Setting the option `useProjectConfigFile` to `false` in `general.php` and running `./craft project-config/rebuild` fixed my issue with installing Craft 3 plugins, when upgrading from Craft 2
Jason Mayo
CC BY-SA 4.0
2019-04-02T23:48:44.153Z
2019-04-02T23:48:44.153Z
mjr
<p>Also wanted to chime in here, that you should try running <code>./craft project-config/rebuild</code> even if you're not using <code>project.yaml</code>. Internally, Craft uses the project config functionality even if you're not using the yaml file. </p>

<p>Just solved a case of this issue where I'm not using the yaml file, nuked the vendor folder and the deleted the <code>composer.lock</code> file to no avail. Running this command was the only thing that worked!</p>

CC BY-SA 4.0
2019-11-03T01:25:26.703Z
2019-11-03T01:25:26.703Z
crawf
<p>Happened to me - a mixture of <a href="https://github.com/craftcms/feed-me/issues/578#issuecomment-557688154" rel="nofollow noreferrer">this</a> and <a href="https://github.com/craftcms/feed-me/issues/519#issuecomment-541003248" rel="nofollow noreferrer">this</a> helped me.</p>

<p>Specifically I did the following (as I wasn't using <code>project.yaml</code>):</p>

<ol>
<li>Uninstall plugin via control panel</li>
<li>Remove the plugin's table row from <code>plugins</code> table in database</li>
<li>Remove any <code>the-plugin-name_</code> prefixed tables from database</li>
<li>Reinstall plugin</li>
</ol>

<p><strong><em>Note:</strong> you will lose any plugin settings :(</em></p>

<p>Still curious what caused this for me...</p>

CC BY-SA 4.0
2019-11-22T22:00:10.570Z
2019-11-22T22:00:10.570Z
iamkeir
<p>Have you tried running the <code>./craft update</code> command? They describe this command here <a href="https://docs.craftcms.com/v3/updating.html#updating-from-the-control-panel" rel="nofollow noreferrer">https://docs.craftcms.com/v3/updating.html#updating-from-the-control-panel</a>. That's one solution, the other thing you could try is for the plugins is removing the vendor folder and executing the <code>composer install</code> command</p>

<p><a href="https://medium.com/@bshelling/craft-mac-n-cheez-creates-a-craftcms-docker-dev-environment-in-seconds-33731a1aa685" rel="nofollow noreferrer">Install CraftCMS and Docker Environment in seconds</a></p>

CC BY-SA 4.0
2019-03-07T09:32:00.723Z
I'm afraid neither of these worked. Removing the vendor folder and executing composer install comes back with `nothing to install or update`. Updating from command line actually gives me the same error as the control panel. - `*** failed to install plugin-slug: No plugin exists with the handle "plugin-slug".`
Amy
CC BY-SA 4.0
2019-03-07T09:40:47.887Z
On top of this, I tried changing my craft version in `composer.json` to 3.1.14 (which I know is a working version), then ran the `composer install`. It said it had installed this version, but nothing changed.
Amy
CC BY-SA 4.0
2019-05-23T14:36:10.367Z
Any solution on this? I'm also getting this problem after installing a plugin then bringing the database from the live site to my local site. It doesn't want to install due to the error plugin handle.
mateostabio
CC BY-SA 4.0
2019-03-07T02:30:13.453Z
2019-03-07T02:30:13.453Z
bshelling
<p>My fix for this error was to manually remove the offending row from the plugins table in the database. Match the handle name in the error to the handle name for the row.</p>

CC BY-SA 4.0
2019-05-30T00:51:12.607Z
2019-05-30T00:51:12.607Z
Anna_MediaGirl
<p>I had a similar error and found a solution!</p>

<p>Let me explain what went wrong with my plugin. I downloaded a plugin locally, installed it and all was good. So I pushed all my files to the live site, went to live admin panel to install the plugin and an error happened. I then tried bringing that database to my local site to install the plugin but it would give me: <code>Internal Server Error: No plugin exists with the handle "plugin-slug"</code> no matter what I did. I tried uninstalling it and reinstalling it with no luck.</p>

<p>I then decided to look at a DIFF of my local database backup (of two days ago without the plugin ever installed) and my newest database I just tried installing that would throw me that error. I searched in the files the plugin handle name and deleted the line of code that had been added. </p>

<p>I deleted the database, imported the edited database and installed the plugin with no issue.</p>

<p>Hope this helps someone!</p>

CC BY-SA 4.0
2019-05-23T15:27:00.873Z
2019-05-24T14:14:18.313Z
2019-05-24T14:14:18.313Z
mateostabio
<p>I had an issue with my site running Craft 3.1.15 where I wasn't able to update the site to the most recent 3.1.16, and also wasn't able to install any plugins. Every plugin I tried would throw this error:</p>

<blockquote>
  <p>Blockquote Invalid plugin: No plugin exists with the handle "plugin-slug"</p>
</blockquote>

<p>I tried creating a fresh install of craft through composer, this time running 3.1.16, and I'm faced with the same error. All my other craft sites run locally seem to update fine and have no issues installing new plugins. Is there an issue with the latest craft updates? Or is there something I need to do to resolve this?</p>

<craft3><plugins><updates>
Invalid plugin: No plugin exists with the handle - Craft 3
# Invalid plugin: No plugin exists with the handle - Craft 3

(Asked by: username_0 on 2019-03-06)

I had an issue with my site running Craft 3.1.15 where I wasn't able to update the site to the most recent 3.1.16, and also wasn't able to install any plugins. Every plugin I tried would throw this error:

> Blockquote Invalid plugin: No plugin exists with the handle "plugin-slug"

I tried creating a fresh install of craft through composer, this time running 3.1.16, and I'm faced with the same error. All my other craft sites run locally seem to update fine and have no issues installing new plugins. Is there an issue with the latest craft updates? Or is there something I need to do to resolve this?

**Tags:** craft3, plugins, updates


---

## 7 answers

### Answer by username_0 on 2019-03-07. Score: 1 | Accepted answer

The issue for this case was something related to my composer not installing it correctly. I downloaded the most recent version of Craft straight from the site and I don't face any of the above issues.

> **Comments:**
> **username_1**: I believe it may have been your ```composer.lock``` file  
> **username_0**: I did think this also, but again this gave me a deadend  

---

### Answer by username_2 on 2019-04-02. Score: 17

For future reference, I had the same error and resolved it with Craft Support.

In my case the project.yaml file got out of sync with what was in the database.

Running craft project-config/rebuild from the project's root resolved the issue and allowed us to re-enable the plugins

> **Comments:**
> **username_3**: Thanks. That resolved my issue.  
> **username_4**: This fixed my issue. Setting the option `useProjectConfigFile` to `false` in `general.php` and running `./craft project-config/rebuild` fixed my issue with installing Craft 3 plugins, when upgrading from Craft 2  

---

### Answer by username_5 on 2019-11-03. Score: 5

Also wanted to chime in here, that you should try running `./craft project-config/rebuild` even if you're not using `project.yaml`. Internally, Craft uses the project config functionality even if you're not using the yaml file.

Just solved a case of this issue where I'm not using the yaml file, nuked the vendor folder and the deleted the `composer.lock` file to no avail. Running this command was the only thing that worked!


---

### Answer by username_6 on 2019-11-22. Score: 2

Happened to me - a mixture of [this](https://github.com/craftcms/feed-me/issues/578#issuecomment-557688154) and [this](https://github.com/craftcms/feed-me/issues/519#issuecomment-541003248) helped me.

Specifically I did the following (as I wasn't using `project.yaml`):

1. Uninstall plugin via control panel
2. Remove the plugin's table row from `plugins` table in database
3. Remove any `the-plugin-name_` prefixed tables from database
4. Reinstall plugin

***Note:*** you will lose any plugin settings :(

Still curious what caused this for me...


---

### Answer by username_1 on 2019-03-07. Score: 1

Have you tried running the `./craft update` command? They describe this command here <https://docs.craftcms.com/v3/updating.html#updating-from-the-control-panel>. That's one solution, the other thing you could try is for the plugins is removing the vendor folder and executing the `composer install` command

[Install CraftCMS and Docker Environment in seconds](https://medium.com/@username_1/craft-mac-n-cheez-creates-a-craftcms-docker-dev-environment-in-seconds-33731a1aa685)

> **Comments:**
> **username_0**: I'm afraid neither of these worked. Removing the vendor folder and executing composer install comes back with `nothing to install or update`. Updating from command line actually gives me the same error as the control panel. - `*** failed to install plugin-slug: No plugin exists with the handle "plugin-slug".`  
> **username_0**: On top of this, I tried changing my craft version in `composer.json` to 3.1.14 (which I know is a working version), then ran the `composer install`. It said it had installed this version, but nothing changed.  
> **username_7**: Any solution on this? I'm also getting this problem after installing a plugin then bringing the database from the live site to my local site. It doesn't want to install due to the error plugin handle.  

---

### Answer by username_8 on 2019-05-30. Score: 0

My fix for this error was to manually remove the offending row from the plugins table in the database. Match the handle name in the error to the handle name for the row.


---

### Answer by username_7 on 2019-05-23. Score: 0

I had a similar error and found a solution!

Let me explain what went wrong with my plugin. I downloaded a plugin locally, installed it and all was good. So I pushed all my files to the live site, went to live admin panel to install the plugin and an error happened. I then tried bringing that database to my local site to install the plugin but it would give me: `Internal Server Error: No plugin exists with the handle "plugin-slug"` no matter what I did. I tried uninstalling it and reinstalling it with no luck.

I then decided to look at a DIFF of my local database backup (of two days ago without the plugin ever installed) and my newest database I just tried installing that would throw me that error. I searched in the files the plugin handle name and deleted the line of code that had been added.

I deleted the database, imported the edited database and installed the plugin with no issue.

Hope this helps someone!


---

