Failed to deploy on Heroku #241

christophwolff · 2015-06-28T18:28:19Z

The buildprocess failed with:

$ROOT_URL, if specified, must be an URL.
! Push rejected, failed to compile Node.js app

Sing-Li · 2015-06-28T18:56:05Z

@pixelpoesie - Are you using the ONE-CLICK-DEPLOY button?

In any case, you must set a config var Settings -> Config varaibles named ROOT_URL with

https://<your app name>.herokuapp.com/

Without it, the server side will not start.

More info at the Rocket.Chat deployment project

engelgabriel · 2015-06-28T23:15:55Z

I've tried for hours to get the ROOT_URL information from the environment, with no luck. :(

christophwolff · 2015-06-29T11:23:35Z

Now it works. Didnt do any thing special since yesterday. Thx!

kohenkatz · 2015-07-02T14:56:12Z

I got the same error today when using the one-click deploy button. Here is the entire log:

-----> Fetching custom git buildpack... done
-----> Node.js app detected
-----> Installing node
-----> Installing meteor
Downloading Meteor distribution
                                                                  0.6%
        1.3%
                                                                      1.8%
                                                 2.3%
#########################################                                 57.8%
###################################################################       94.3%
#####################################################################     95.9%
####################################################################     96.4%
####################################################################     97.0%
#####################################################################    97.6%
Meteor 1.1.0.2 has been installed in your home directory (~/.meteor).
Now you need to do one of the following:
  (1) Add "$HOME/.meteor" to your path, or
  (2) Run this command as root:
        cp "/tmp/buildpack_442b8f6cd26288e0efd13128791ed182/meteor-D2gR/.meteor/packages/meteor-tool/1.1.3/mt-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor
Then to get started, take a look at 'meteor --help' or see the docs at
docs.meteor.com.
-----> Bundling bundle
$ROOT_URL, if specified, must be an URL.
 !     Push rejected, failed to compile Node.js app

kohenkatz · 2015-07-02T15:02:57Z

I figured out my issue. I chose to create a new Heroku account for this app, and the first time that I clicked the "Deploy" button, Heroku interrupted the deployment to ask for credit card info in order to verify my account. The deployment was left in "half-configured" state, so future clicks of the "deploy" button failed too.

After I deleted the old half-configured deployment and started totally fresh, it seems to have worked.

engelgabriel · 2015-07-02T15:19:51Z

Yes, Meteor needs the $ROOT_URL variable.

tkdjex · 2015-12-16T14:59:10Z

hello, how do you delete the "half-configured" deployment? I'm totally new to this and have same issue as you. Thanks

Sing-Li · 2015-12-16T15:12:35Z

Sign into the dashboard and delete the app.

tkdjex · 2015-12-16T18:56:45Z

Thanks for your answer. Unfortunately I can't see any apps installed. See
screenshot. What else can I do?

Sent from mobile.
16 gru 2015 16:13 "SingLi" [email protected] napisał(a):

Sign into the dashboard and delete the app.

—
Reply to this email directly or view it on GitHub
#241 (comment)
.

tkdjex · 2015-12-16T21:06:50Z

Hi, thanks, I've managed that, cheers

antonpopov · 2016-07-31T09:16:58Z

Hi, there! I got a similar "error" when using the one-click deploy button. Here is the log:
-----> Node.js app detected
-----> Listing HEROKU_ environment variables
HEROKU_APP_ID:
HEROKU_APP_NAME:
HEROKU_DYNO_ID:
HEROKU_RELEASE_VERSION:
HEROKU_SLUG_COMMIT:
HEROKU_SLUG_DESCRIPTION:
-----> Installing node
-----> Installing meteor
Downloading Meteor distribution
Meteor 1.4.0.1 has been installed in your home directory (~/.meteor).
Now you need to do one of the following:
(1) Add "$HOME/.meteor" to your path, or
(2) Run this command as root:
cp "/app/tmp/buildpacks/ec95e5d1b974435c5c7157ba6fcb0d6323f4e70beb6f90c5dc8e2248948ff950dfcd73ff00896ded7938ceb333a80d48f2db8558e376c5c760eb8d9eb9b681d3/meteor-CXRy/.meteor/packages/meteor-tool/1.4.0-1/mt-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor
Then to get started, take a look at 'meteor --help' or see the docs at
docs.meteor.com.
-----> Bundling bundle
-----> Checking if this meteor version supports --server-only
! command='cytokine run-buildpacks /tmp/build_11cbda07e556a704e7b187fdf604dc8d/RocketChat-Rocket.Chat-98b0e28 /app/tmp/cache /tmp/d20160731-54-rokpzs /app/tmp/buildpacks --request-id=140195bd-db3a-4723-483a-64b655fa523b --buildpack=https://github.com/RocketChat/heroku-buildpack-meteor.git --log-file=/tmp/20160731-54-1stvg4n' exit_status=0 at=timeout elapsed=3588.6292831897736
! See https://devcenter.heroku.com/articles/slug-compiler#time-limit

ravimallya · 2017-07-26T16:00:05Z

Hi.

I'm also having the same issue with heroku CLI. I followed the procedure mentioned at: https://rocket.chat/docs/installation/paas-deployments/heroku/ . Here is the log:

remote: -----> Building Meteor app with ROOT_URL: https://ravimallya-dev.herokuapp.com/
remote: => Errors while initializing project:
remote:
remote: While loading emojione:[email protected]...:
remote: error: Command failed:
remote: /app/tmp/cache/meteor/.meteor/packages/meteor-tool/.1.5.1.puot9a++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm
remote: rebuild --update-binary
remote: Phantom installation failed { [Error: EACCES: permission denied, open
remote: '/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/location.js']
remote: errno: -13,
remote: code: 'EACCES',
remote: syscall: 'open',
remote: path:
remote: '/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/location.js'
remote: } Error: EACCES: permission denied, open
remote: '/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/location.js'
remote: at Error (native)
remote: at Object.fs.openSync (fs.js:549:18)
remote: at Object.fs.writeFileSync (fs.js:1156:15)
remote: at writeLocationFile
remote: (/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/install.js:108:6)
remote: at Promise._successFn
remote: (/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/install.js:80:5)
remote: at nextTickCallback
remote: (/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/node_modules/kew/kew.js:47:28)
remote: at nextTickCallbackWith0Args (node.js:489:9)
remote: at process._tickCallback (node.js:418:13)
remote: npm ERR! code ELIFECYCLE
remote: npm ERR! errno 1
remote: npm ERR! [email protected] install: `node install.js`
remote: npm ERR! Exit status 1
remote: npm ERR!
remote: npm ERR! Failed at the [email protected] install script.
remote: npm ERR! This is probably not a problem with npm. There is likely additional
remote: logging output above.
remote:
remote: npm ERR! A complete log of this run can be found in:
remote: npm ERR!
remote: /app/tmp/cache/meteor/.meteor/packages/meteor-tool/.1.5.1.puot9a++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/.npm/_logs/2017-07-26T15_55_06_957Z-debug.log
remote: Phantom installation failed { [Error: EACCES: permission denied, open
remote: '/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/location.js']
remote: errno: -13,
remote: code: 'EACCES',
remote: syscall: 'open',
remote: path:
remote: '/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/location.js'
remote: } Error: EACCES: permission denied, open
remote: '/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/location.js'
remote: at Error (native)
remote: at Object.fs.openSync (fs.js:549:18)
remote: at Object.fs.writeFileSync (fs.js:1156:15)
remote: at writeLocationFile
remote: (/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/install.js:108:6)
remote: at Promise._successFn
remote: (/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/install.js:80:5)
remote: at nextTickCallback
remote: (/tmp/mt-cde1xa/npm/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/node_modules/kew/kew.js:47:28)
remote: at nextTickCallbackWith0Args (node.js:489:9)
remote: at process._tickCallback (node.js:418:13)
remote: npm ERR! code ELIFECYCLE
remote: npm ERR! errno 1
remote: npm ERR! [email protected] install: `node install.js`
remote: npm ERR! Exit status 1
remote: npm ERR!
remote: npm ERR! Failed at the [email protected] install script.
remote: npm ERR! This is probably not a problem with npm. There is likely additional
remote: logging output above.
remote:
remote: npm ERR! A complete log of this run can be found in:
remote: npm ERR!
remote: /app/tmp/cache/meteor/.meteor/packages/meteor-tool/.1.5.1.puot9a++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/.npm/_logs/2017-07-26T15_55_06_957Z-debug.log
remote:
remote:
remote:  !     Push rejected, failed to compile Node.js app.
remote:
remote:  !     Push failed
remote: Verifying deploy...
remote:
remote: !       Push rejected to ravimallya-dev.
remote:
To https://git.heroku.com/ravimallya-dev.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/ravimallya-dev.git'

Is this the issue related to Rocket.Chat or Heroku itself?

Merge Rocket.Chat 0.61.1

Popover does not close on system back button

engelgabriel closed this as completed Jun 28, 2015

engelgabriel modified the milestone: v0.5 Jun 30, 2015

tkurz pushed a commit to redlink-gmbh/Rocket.Chat that referenced this issue Mar 13, 2018

Merge pull request RocketChat#241 from assistify/port/0.61.1

88975b8

Merge Rocket.Chat 0.61.1

bhardwajaditya pushed a commit to bhardwajaditya/Rocket.Chat that referenced this issue Apr 30, 2020

Merge pull request RocketChat#241 from bhardwajaditya/issue235

dfcc382

Popover does not close on system back button

sitedata mentioned this issue Mar 8, 2021

[Snyk] Security upgrade @google-cloud/vision from 0.23.0 to 0.24.0 sitedata/Rocket.Chat#30

Open

toshanmugaraj mentioned this issue Mar 8, 2021

[Snyk] Security upgrade @google-cloud/vision from 0.23.0 to 0.24.0 toshanmugaraj/Rocket.Chat#46

Open

timtheguy mentioned this issue Mar 8, 2021

[Snyk] Security upgrade @google-cloud/vision from 0.23.0 to 0.24.0 timtheguy/Rocket.Chat#46

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Failed to deploy on Heroku #241

Failed to deploy on Heroku #241

christophwolff commented Jun 28, 2015

Sing-Li commented Jun 28, 2015

engelgabriel commented Jun 28, 2015

christophwolff commented Jun 29, 2015

kohenkatz commented Jul 2, 2015

kohenkatz commented Jul 2, 2015

engelgabriel commented Jul 2, 2015

tkdjex commented Dec 16, 2015

Sing-Li commented Dec 16, 2015

tkdjex commented Dec 16, 2015

tkdjex commented Dec 16, 2015

antonpopov commented Jul 31, 2016 •

edited

Loading

ravimallya commented Jul 26, 2017

Failed to deploy on Heroku #241

Failed to deploy on Heroku #241

Comments

christophwolff commented Jun 28, 2015

Sing-Li commented Jun 28, 2015

engelgabriel commented Jun 28, 2015

christophwolff commented Jun 29, 2015

kohenkatz commented Jul 2, 2015

kohenkatz commented Jul 2, 2015

engelgabriel commented Jul 2, 2015

tkdjex commented Dec 16, 2015

Sing-Li commented Dec 16, 2015

tkdjex commented Dec 16, 2015

tkdjex commented Dec 16, 2015

antonpopov commented Jul 31, 2016 • edited Loading

ravimallya commented Jul 26, 2017

antonpopov commented Jul 31, 2016 •

edited

Loading