# Can't push to Kinsta from local

**URL:** https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522
**Category:** Application Support
**Created:** [December 6, 2024, 1:54pm UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522 "2024-12-06T13:54:15Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![etienne\_clerc](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/etienne_clerc/32/3646_2.png) [@etienne\_clerc](https://community.kinsta.com/u/etienne_clerc)
#### Post date: [December 6, 2024, 1:54pm UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522/1 "2024-12-06T13:54:15Z")

</div>

Hi there,

After successfully pulling my website from Kinsta, I encountered this screen when trying to push:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/d/d4a8c0216a8e2532d9c3acd788910d947747a0c7.png)

I’m not sure why the website appears twice, but both instances prompt me to create a new environment, even though there’s already a production environment from which I pulled:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/c/c52c1af610146d0067b4ad42c214f32b06d8e990.png)

Regardless of which one I click on, the “Create new environment” link redirects me to my Kinsta account. However, the production environment already exists. Is it not possible to push directly to production?

Thanks in advance for your help! 🙂

---

<div class="post-metadata">

### Author: ![jackirish](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/jackirish/32/1361_2.png) [@jackirish](https://community.kinsta.com/u/jackirish)
#### Post date: [December 6, 2024, 9:35pm UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522/2 "2024-12-06T21:35:00Z")

</div>

Hi @etienne_clerc ! 👋

Unfortunately, it is not possible to push changes directly to a Production environment that is in MyKinsta. All pushes from DevKinsta must be sent to a Staging environment first: [DevKinsta - Kinsta Integration - Kinsta® Docs](https://kinsta.com/docs/devkinsta/devkinsta-integration/#push-changes-to-staging)

 ![push-changes](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/5/5c8b9be81c69c977687f476e28684f5e1e26bddf.png)

---

<div class="post-metadata">

### Author: ![etienne\_clerc](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/etienne_clerc/32/3646_2.png) [@etienne\_clerc](https://community.kinsta.com/u/etienne_clerc)
#### Post date: [December 9, 2024, 6:49pm UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522/3 "2024-12-09T18:49:36Z")

</div>

Hi @jackirish,

Thanks for the answer, is this a feature that could be added in the future? We sometimes push directly to production when making minor changes or doing hotfixes, so this adds an unnecessary step in our workflow.

Thanks! 🙂

---

<div class="post-metadata">

### Author: ![jackirish](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/jackirish/32/1361_2.png) [@jackirish](https://community.kinsta.com/u/jackirish)
#### Post date: [December 9, 2024, 9:56pm UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522/4 "2024-12-09T21:56:35Z")

</div>

Hi @etienne_clerc,

While I can certainly put it in as a feature request, the reason this has not been put in, historically speaking, is because it’s considered potentially dangerous to the Live site. An accidental push from the local environment to the Live site could be problematic, or cause issues with the Live site that could result in data loss, particularly in the case of e-commerce sites.

---

<div class="post-metadata">

### Author: ![etienne\_clerc](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/etienne_clerc/32/3646_2.png) [@etienne\_clerc](https://community.kinsta.com/u/etienne_clerc)
#### Post date: [December 9, 2024, 10:12pm UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522/5 "2024-12-09T22:12:15Z")

</div>

Hi @jackirish

You make a completely valid point, and I agree that, in most cases, pushing directly to production is not a good practice. However, I believe that ultimately, the decision should be left to the user.

---

<div class="post-metadata">

### Author: ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [December 10, 2024, 9:59am UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522/6 "2024-12-10T09:59:04Z")

</div>

Hello @etienne_clerc 👋

Thanks for writing back. We will add this to our Feature Request list. Kinsta is currently in maintenance and security updates mode, so we can’t provide any information in regards to whether this will be implemented and when, but we will send it to our developers for consideration 👍

Kind regards

---

<div class="post-metadata">

### Author: ![etienne\_clerc](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/etienne_clerc/32/3646_2.png) [@etienne\_clerc](https://community.kinsta.com/u/etienne_clerc)
#### Post date: [December 10, 2024, 2:14pm UTC](https://community.kinsta.com/t/cant-push-to-kinsta-from-local/4522/7 "2024-12-10T14:14:18Z")

</div>

Hi @VladimirM,

Perfect, thank you for the update! 🙂
