# Cannot push to Remote Origin; Environments not showing

**URL:** https://community.kinsta.com/t/cannot-push-to-remote-origin-environments-not-showing/3174
**Category:** Bug Reports
**Created:** [March 18, 2024, 10:28pm UTC](https://community.kinsta.com/t/cannot-push-to-remote-origin-environments-not-showing/3174 "2024-03-18T22:28:43Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![ghsangoma](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/ghsangoma/32/3133_2.png) [@ghsangoma](https://community.kinsta.com/u/ghsangoma)
#### Post date: [March 18, 2024, 10:28pm UTC](https://community.kinsta.com/t/cannot-push-to-remote-origin-environments-not-showing/3174/1 "2024-03-18T22:28:43Z")

</div>

I’m trying to push my local to Remote. The list of Sites in my Kinsta account shows, but the environments don’t show up (Live, Staging, etc.). It’s asking to create a new environment, but they already exist. I’ve updated Docker and logged out/logged in to my Kinsta account. I restarted everything, and it’s still not loading. This happens to all the sites in my account, not just the new one I’ve created.

\*\*DevKinsta Version: Version 2.13.1 (2.13.1.8585)  
\*\*OS Version: Mac M1 13.5.2  
\*\*Docker Desktop Version: 4.28.0

 ![Screenshot 2024-03-18 at 5.27.45 PM](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/9/970e5a35c2dbbb2d0eba97f61c03e6355413f8c0.png)

---

<div class="post-metadata">

### Author: ![Agus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/agus/32/1515_2.png) [@Agus](https://community.kinsta.com/u/Agus)
#### Post date: [March 19, 2024, 3:58am UTC](https://community.kinsta.com/t/cannot-push-to-remote-origin-environments-not-showing/3174/3 "2024-03-19T03:58:42Z")

</div>

Hello @ghsangoma 👋 and welcome to our Community forum!

Thank you for reaching us out here!

First of all, please allow me to inform you that when pushing the local site to Kinsta , the Live environments won’t be shown there (in the “Select target site” list in DevKinsta) - so only the Staging environment(s) will be shown there - if available, either the [Standard](https://kinsta.com/docs/wordpress-hosting/staging-environment/#creating-the-standard-staging-environment) and/or [Premium](https://kinsta.com/docs/wordpress-hosting/staging-environment/#add-a-premium-staging-environment) one - and you can only push the site from local to Staging environment only, as also [mentioned here](https://kinsta.com/docs/devkinsta/devkinsta-integration/#push-changes-to-staging)

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

I’ve also just checked into your MyKinsta control panel for that `Sangoma US` site for example - and could see that you’ve already created a Staging environment for that site (just today? so that’s why it was not shown in that target site list in DevKinsta previously)

So now when you check on your DevKinsta again, if you try to push the local site to your Kinsta site, you should now be able to see the _Staging environment_ of that “ **Sangoma US** ” site . Then you can just click that `Sangoma US * Staging` name from the list, then on the next screen/modal window, you can push the local site to that staging site in question.

Another example would be for that `APIdaze.io * Staging` , if you click on that staging site name from the list :

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/0/0d48c11e25337a4cb62490681f8978bad68c08ea.png)  
on the next screen/modal window, you will be able to see the “Confirm changes” modal - before you can click the “Push site” button (to push the local site to that staging site on your hosting server).

Please give it a try and do let us know again if something is still not working properly as expected (and provide more screenshots about the issue in details, etc.) - We will be happy to help and assist you!

Best regards  
Agus Utomo

---

<div class="post-metadata">

### Author: ![ghsangoma](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/ghsangoma/32/3133_2.png) [@ghsangoma](https://community.kinsta.com/u/ghsangoma)
#### Post date: [April 26, 2024, 5:00pm UTC](https://community.kinsta.com/t/cannot-push-to-remote-origin-environments-not-showing/3174/4 "2024-04-26T17:00:52Z")

</div>

Sorry for the late reply but what you said was correct. It fixed my issue. Thank you!!

---

<div class="post-metadata">

### Author: ![Agus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/agus/32/1515_2.png) [@Agus](https://community.kinsta.com/u/Agus)
#### Post date: [April 29, 2024, 3:37am UTC](https://community.kinsta.com/t/cannot-push-to-remote-origin-environments-not-showing/3174/5 "2024-04-29T03:37:05Z")

</div>

That’s alright @ghsangoma ! 😃  
Glad that the issue has now fixed , and you’re most welcome!

Best regards,  
Agus Utomo

---

<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: [May 1, 2024, 3:37pm UTC](https://community.kinsta.com/t/cannot-push-to-remote-origin-environments-not-showing/3174/6 "2024-05-01T15:37:55Z")

</div>

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