# MU Plugin do not pushed from DevKinsta to staging environment

**URL:** <https://community.kinsta.com/t/mu-plugin-do-not-pushed-from-devkinsta-to-staging-environment/1538>\
**Category:** Bug Reports\
**Created:** [June 8, 2022, 10:14pm UTC](https://community.kinsta.com/t/mu-plugin-do-not-pushed-from-devkinsta-to-staging-environment/1538 "2022-06-08T22:14:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zemove](https://avatars.discourse-cdn.com/v4/letter/z/dec6dc/32.png) [@zemove](https://community.kinsta.com/u/zemove)\
**Post date:** [June 8, 2022, 10:14pm UTC](https://community.kinsta.com/t/mu-plugin-do-not-pushed-from-devkinsta-to-staging-environment/1538/1 "2022-06-08T22:14:37Z")

</div>

**Q: Date/Time this occurred (Provide your time zone also)**  
**A:** 8/6/22 23:15 CEST

**Q: DevKinsta Version**  
**A:** 2.6.0

**Q: OS Version**  
**A:** MacOS 10.15.7

**Q: Docker Desktop Version**  
**A:** 4.8.2

**Q: Were any error codes or messages observed? If so, what were they?**  
**A:** No, I do not see any error codes on DevKinsta log

**Q: Detailed Description of the Problem**  
**A:** As I described on the brief sentence, I’ve Kinsta MU Plugin installed on local DevKinsta. When I push local DevKinsta to staging environment I do not find MU Plugin files into the folder. I have only the folder without the files.

---

<div class="post-metadata">

**Author:** ![Kevin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/kevin/32/808_2.png) [@Kevin](https://community.kinsta.com/u/Kevin)\
**Post date:** [June 8, 2022, 11:02pm UTC](https://community.kinsta.com/t/mu-plugin-do-not-pushed-from-devkinsta-to-staging-environment/1538/2 "2022-06-08T23:02:32Z")

</div>

Hi @zemove, thanks for reaching out. For a few updates now, Pushing from Local to MyKinsta/Staging ignores the mu-plugin directory in order to avoid version mismatch issues.

You can[manually add the current MU Plugin files](https://kinsta.com/help/kinsta-mu-plugin/#install-kinsta-mu-plugin) in Staging or contact our Live Support in MyKinsta to reinstall it for you.

It’s remaining empty in Staging because those files were likely deleted at some point.

---

<div class="post-metadata">

**Author:** ![zemove](https://avatars.discourse-cdn.com/v4/letter/z/dec6dc/32.png) [@zemove](https://community.kinsta.com/u/zemove)\
**Post date:** [June 8, 2022, 11:05pm UTC](https://community.kinsta.com/t/mu-plugin-do-not-pushed-from-devkinsta-to-staging-environment/1538/3 "2022-06-08T23:05:22Z")

</div>

Ok ty David.

So, every time I push from DevKinsta to remote staging environment I need to manually re-install Kinsta MU Plugin, right?

---

<div class="post-metadata">

**Author:** ![Kevin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/kevin/32/808_2.png) [@Kevin](https://community.kinsta.com/u/Kevin)\
**Post date:** [June 8, 2022, 11:07pm UTC](https://community.kinsta.com/t/mu-plugin-do-not-pushed-from-devkinsta-to-staging-environment/1538/4 "2022-06-08T23:07:49Z")

</div>

Correct; if your remote environment does not already have the mu-plugin installed, you will need to reinstall it. That is currently the only directory that is ignored when you Push from DevKinsta to Kinsta.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/8/80f8c4e56fecc02327a0964e6bf63a716483529f.png) [@system](https://community.kinsta.com/u/system)\
**Post date:** [June 11, 2022, 11:08pm UTC](https://community.kinsta.com/t/mu-plugin-do-not-pushed-from-devkinsta-to-staging-environment/1538/5 "2022-06-11T23:08:10Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.