# Forge deploy failing **URL:** \ **Category:** Forge\ **Tags:** forge-deploy, forge-cli, codegeist-2021, forge-lint, forge-connect\ **Created:** [September 2, 2021, 1:32pm UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599 "2021-09-02T13:32:33Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![danielwester](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/danielwester/32/36730_2.png) [@danielwester](https://community.developer.atlassian.com/u/danielwester)\ **Post date:** [September 2, 2021, 1:32pm UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/1 "2021-09-02T13:32:33Z")
I’m sure it’s something I did - but… when I do forge deploy I get: ```auto ℹ Packaging app files ℹ Uploading app ℹ Validating manifest ℹ Snapshotting functions ℹ Deploying to environment Error: Deployment failed ``` With verbose flag I see ```auto { "description": "Deploying to environment", "events": [ { "__typename": "AppDeploymentTransitionEvent", "stepName": "Validate hosted resource upload step", "createdAt": "2021-09-02T13:18:46.474Z", "newStatus": "STARTED" }, { "__typename": "AppDeploymentLogEvent", "stepName": "Validate hosted resource upload step", "createdAt": "2021-09-02T13:18:48.135Z", "message": "Deployment failed with unknown error", "level": "ERROR" }, { "__typename": "AppDeploymentTransitionEvent", "stepName": "Validate hosted resource upload step", "createdAt": "2021-09-02T13:18:48.137Z", "newStatus": "FAILED" } ] } ``` Help? ---
**Author:** ![danielwester](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/danielwester/32/36730_2.png) [@danielwester](https://community.developer.atlassian.com/u/danielwester)\ **Post date:** [September 2, 2021, 1:39pm UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/2 "2021-09-02T13:39:37Z")
And of course right after this I send my manifest through a yaml lint checker and the connect fragment is not validating according to it. Lesson learned - forge lint is not the same between the cli and the deployment mechanism… ---
**Author:** ![danielwester](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/danielwester/32/36730_2.png) [@danielwester](https://community.developer.atlassian.com/u/danielwester)\ **Post date:** [September 2, 2021, 2:17pm UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/3 "2021-09-02T14:17:26Z")
Well I take that back - not all is well. Managed to get my forge app “installed” but needing upgrading according to the upm - the update button doesn’t work. Forge CLI doesn’t show the installation anymore. Going to the app I get a 500 after I go through the oauth dance… Works fine if I create a new Confluence instance. ---
**Author:** ![clement\_garin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/clement_garin/32/38126_2.png) [@clement\_garin](https://community.developer.atlassian.com/u/clement_garin)\ **Post date:** [September 2, 2021, 3:52pm UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/4 "2021-09-02T15:52:51Z")
I have similar troubles, currently `forge install --upgrade` is not working: > Error: request to [GraphQL Gateway](https://api.atlassian.com/graphql) failed, reason: connect ETIMEDOUT 18.184.99.131:443 I’m wondering if some webservicse are down at Atlassian ? ---
**Author:** ![YongFeiLim](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yongfeilim/32/43417_2.png) [@YongFeiLim](https://community.developer.atlassian.com/u/YongFeiLim)\ **Post date:** [September 2, 2021, 11:40pm UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/5 "2021-09-02T23:40:35Z")
Hi @danielwester can I get the forge cli version you were using? You find it by running `forge --version`. Can I also request admin access to your site to further investigate? Otherwise, if you could provide me the site url that should be sufficient for now 🙂 ---
**Author:** ![YongFeiLim](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yongfeilim/32/43417_2.png) [@YongFeiLim](https://community.developer.atlassian.com/u/YongFeiLim)\ **Post date:** [September 2, 2021, 11:41pm UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/6 "2021-09-02T23:41:38Z")
Hey @clement_garin , are you still experiencing the issue? ---
**Author:** ![danielwester](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/danielwester/32/36730_2.png) [@danielwester](https://community.developer.atlassian.com/u/danielwester)\ **Post date:** [September 3, 2021, 7:14am UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/7 "2021-09-03T07:14:43Z")
I’m running 2.0.0. I was able to uninstall the forge “proper” app - but the companion connect app still exists. ---
**Author:** ![clement\_garin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/clement_garin/32/38126_2.png) [@clement\_garin](https://community.developer.atlassian.com/u/clement_garin)\ **Post date:** [September 3, 2021, 7:34am UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/8 "2021-09-03T07:34:42Z")
It’s working again on my side, thanks! ---
**Author:** ![danielwester](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/danielwester/32/36730_2.png) [@danielwester](https://community.developer.atlassian.com/u/danielwester)\ **Post date:** [September 3, 2021, 8:52am UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/9 "2021-09-03T08:52:56Z")
I think I’ve tracked down my issue to that the name attribute and the remote app key was the same so I’ve ended up with 2 apps installed into an instance with the same key… ---
**Author:** ![YongFeiLim](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yongfeilim/32/43417_2.png) [@YongFeiLim](https://community.developer.atlassian.com/u/YongFeiLim)\ **Post date:** [September 6, 2021, 5:09am UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/10 "2021-09-06T05:09:47Z")
Hey @danielwester , glad that you were able to track down the issue. Was there anything that lead to apps with the same remote app key being installed? ---
**Author:** ![jhazelwood](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/jhazelwood/32/44414_2.png) [@jhazelwood](https://community.developer.atlassian.com/u/jhazelwood)\ **Post date:** [September 8, 2021, 12:00am UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/11 "2021-09-08T00:00:01Z")
Hey @danielwester , 2 apps with the same key will do it. Sorry for your bad experience; you’re on the cutting edge here - we’re working on the migration experience right now so that soon, a Forge app will be able to replace a Connect app with the same key, and if you try and install two Forge apps with the same connect key you’ll get a helpful error message. Let me know if you’d like to set up a meeting to debug connect-on-forge or chat about the internals and our plans for it! Cheers, James ---
**Author:** ![jhazelwood](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/jhazelwood/32/44414_2.png) [@jhazelwood](https://community.developer.atlassian.com/u/jhazelwood)\ **Post date:** [September 9, 2021, 1:05am UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/12 "2021-09-09T01:05:33Z")
Hi all, from the reports coming in we suspect there might be an issue with connect-on-forge besides just the inability to rename a key. We’re investigating now. You can follow [this ticket](https://ecosystem.atlassian.net/browse/FRGE-372) for updates. ---
**Author:** ![jhazelwood](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/jhazelwood/32/44414_2.png) [@jhazelwood](https://community.developer.atlassian.com/u/jhazelwood)\ **Post date:** [September 9, 2021, 7:59am UTC](https://community.developer.atlassian.com/t/forge-deploy-failing/51599/13 "2021-09-09T07:59:58Z")
Please see the public issue for [an update](https://ecosystem.atlassian.net/browse/FRGE-372?focusedCommentId=652865). It includes a workaround, which is to let us know your app ID so we can let you know your app’s randomly-generated key, in order to set `app.connect.key` to match.