Comments (23)
@Vadorequest I found a solution. You need to move the version of n8n in the Dockerfile to 0.98.0 and redeploy the application.
Worked for me.
from n8n-heroku.
I forked this repository and fixed the Heroku integration following @fullbright trick.
https://github.com/UnlyEd/n8n-heroku-demo
Also made an online version available, hosted on heroku at https://unly-n8n-demo.herokuapp.com
from n8n-heroku.
There seem to be a couple of issues with this heroku deployment?
It cannot handle webhooks, triggers?
I tried with a trello one and got back 403, because it tried registering with a localhost url. Which is strange.
I also updated my heroku instance but ended up having to setup all my triggers all over again, as they we decrypted with a different key than available after the deploy.
Strange stuff
from n8n-heroku.
from n8n-heroku.
It seems that I found some variables thanks to you guys
Encryption key worked: https://docs.n8n.io/reference/configuration.html#encryption-key. No longer not problem with credentials
Then for webhook, I needed this: https://docs.n8n.io/reference/configuration.html#webhook-url. First thought i needed this: https://docs.n8n.io/reference/configuration.html#publish, but that did not work. So the webhook-url is important.
So all fixed for me now. I had to go via: https://github.com/UnlyEd/n8n-heroku-demo/ to deploy though.
from n8n-heroku.
I have the same error
from n8n-heroku.
Me too. I try to use PostgreSQL the It happened.
Could @sarveshpro please explain more about how to use PostgreSQL?
from n8n-heroku.
I find this error log
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: this library is no longer supported
/usr/local/bin/n8n -> /usr/local/lib/node_modules/n8n/bin/n8n[email protected] install /usr/local/lib/node_modules/n8n/node_modules/sqlite3
node-pre-gyp install --fallback-to-build
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.2.0/node-v83-linux-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v83 ABI, musl) (falling back to source compile with node-gyp)
make: Entering directory '/usr/local/lib/node_modules/n8n/node_modules/sqlite3/build'
ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3310100/sqlite3.c
TOUCH Release/obj.target/deps/action_before_build.stamp
CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3310100/sqlite3.o
from n8n-heroku.
Same, I basically clicked on the "Deploy to heroku button" and it got deployed, but I get the following when I go to the app:
Note that I changed the basic auth login/password, but that's it.
Logs:
heroku logs --tail --app=unly-n8n
[...]
2020-12-06T15:29:04.699249+00:00 heroku[web.1]: Starting process with command `/start.sh`
2020-12-06T15:29:06.764250+00:00 app[web.1]: N8N will start on '58444'
2020-12-06T15:29:06.764297+00:00 app[web.1]: postgres://wgenyjymnkdjnm:85e9523675340b5f866dc18afa36b14f841ecf1701a8021d569f757aff845dd8@ec2-54-247-70-127.eu-west-1.compute.amazonaws.com:5432/d62fc9j92lg1uo
2020-12-06T15:29:06.764300+00:00 app[web.1]: postgre config detected
2020-12-06T15:29:06.765536+00:00 app[web.1]: postgres://wgenyjymnkdjnm:85e9523675340b5f866dc18afa36b14f841ecf1701a8021d569f757aff845dd8@ec2-54-247-70-127.eu-west-1.compute.amazonaws.com:5432/d62fc9j92lg1uo
2020-12-06T15:29:06.767977+00:00 app[web.1]: indentified DB in use postgreSQL
2020-12-06T15:29:08.144153+00:00 app[web.1]: UserSettings got generated and saved to: /data/.n8n/config
2020-12-06T15:29:09.888779+00:00 heroku[web.1]: Process exited with status 0
2020-12-06T15:29:09.922281+00:00 heroku[web.1]: State changed from starting to crashed
2020-12-06T15:29:09.925661+00:00 heroku[web.1]: State changed from crashed to starting
2020-12-06T15:29:17.682825+00:00 heroku[web.1]: Starting process with command `/start.sh`
2020-12-06T15:29:19.858017+00:00 app[web.1]: N8N will start on '41378'
2020-12-06T15:29:19.858048+00:00 app[web.1]: postgres://wgenyjymnkdjnm:85e9523675340b5f866dc18afa36b14f841ecf1701a8021d569f757aff845dd8@ec2-54-247-70-127.eu-west-1.compute.amazonaws.com:5432/d62fc9j92lg1uo
2020-12-06T15:29:19.858051+00:00 app[web.1]: postgre config detected
2020-12-06T15:29:19.859350+00:00 app[web.1]: postgres://wgenyjymnkdjnm:85e9523675340b5f866dc18afa36b14f841ecf1701a8021d569f757aff845dd8@ec2-54-247-70-127.eu-west-1.compute.amazonaws.com:5432/d62fc9j92lg1uo
2020-12-06T15:29:19.861364+00:00 app[web.1]: indentified DB in use postgreSQL
2020-12-06T15:29:21.350517+00:00 app[web.1]: UserSettings got generated and saved to: /data/.n8n/config
2020-12-06T15:29:23.191713+00:00 heroku[web.1]: Process exited with status 0
2020-12-06T15:29:23.224363+00:00 heroku[web.1]: State changed from starting to crashed
2020-12-06T15:29:45.043603+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=unly-n8n.herokuapp.com request_id=f00efeec-d3f8-49fc-8c48-23bf262d6c85 fwd="176.158.114.162" dyno= connect= service= status=503 bytes= protocol=https
2020-12-06T15:29:45.047882+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/robots.txt" host=unly-n8n.herokuapp.com request_id=57bb117c-81df-43b2-9253-523bd1b8e46b fwd="176.158.114.162" dyno= connect= service= status=503 bytes= protocol=https
2020-12-06T15:29:47.130703+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=unly-n8n.herokuapp.com request_id=bc9751bd-03f7-42dd-9a54-b5fc24db106b fwd="176.158.114.162" dyno= connect= service= status=503 bytes= protocol=https
2020-12-06T15:30:39.798149+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=unly-n8n.herokuapp.com request_id=da4f12b0-e005-4ab2-9157-10b3902b47c1 fwd="176.158.114.162" dyno= connect= service= status=503 bytes= protocol=https
2020-12-06T15:30:41.422700+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=unly-n8n.herokuapp.com request_id=30d81874-cc95-41d2-907a-11d5e789354d fwd="176.158.114.162" dyno= connect= service= status=503 bytes= protocol=https
2020-12-06T15:34:46.662806+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=unly-n8n.herokuapp.com request_id=2e46bad2-0ba9-4bf5-a24f-24fa86ee5679 fwd="176.158.114.162" dyno= connect= service= status=503 bytes= protocol=https
2020-12-06T15:34:48.135301+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=unly-n8n.herokuapp.com request_id=875cb88e-01ed-4312-90f3-ca1e3707b158 fwd="176.158.114.162" dyno= connect= service= status=503 bytes= protocol=https
from n8n-heroku.
Same issue here. Did you find a solution?
from n8n-heroku.
@fullbright Nope, I haven't search much for one either, basically moved to the Cloud offering.
But it'd be great to have it for free and unlimited using Heroku!
from n8n-heroku.
@fullbright Awesome! I never used Heroku, could you share how to edit the Dockerfile?
Do you edit it prior to deploying? Can you change it after you deployed? (and if so, how)
Shouldn't the version be defined as a ENV variable? That might be much easier to update this way. 🤔
from n8n-heroku.
Also, I tried using another login/password for a proprietary project and I couldn't authenticate myself. Maybe I made a dumb mistake, but I feel like Basic Auth might have some restrictions like a password max length or so.
from n8n-heroku.
@Vadorequest I found a solution. You need to move the version of n8n in the Dockerfile to 0.98.0 and redeploy the application.
Worked for me.
What if the n8n upgrades to a newer version? Then if I make the change in Dockerfile and redeploy, will all the triggers I created wipe off?
from n8n-heroku.
from n8n-heroku.
@fullbright What about the triggers I created then? Should I re-create the triggers when I deploy a new version of the app?
from n8n-heroku.
from n8n-heroku.
@fullbright What if I create a new trigger in the heroku-hosted ngn instance and then I re-deploy the app, leaving the database add-ons as they are. Would that confirm?
from n8n-heroku.
from n8n-heroku.
@fullbright It's working!. I created a test trigger and re-deployed the app. I could still see the test trigger I created. Thanks!
By the way, how many triggers can I create before reaching the 1Gb database storage limit? Please forgive me if the question sounds silly. I have no knowledge of databases.
And, is 512Mb of RAM enough for ngn? Wouldn't that be a problem in the future after I create many workflows?
from n8n-heroku.
@capriciousduck 1GB data storage is huge, you might never reach it. I don't know what's stored in the DB, but if it's only the workflow files, then you could have thousands workflows without issue.
Regarding the RAM, hard to say, but I expect n8n to be really light considering it's a short-live process that only triggers when an event occurs. Basically, it might limit the number of workflows triggering in parallel, but that's it. I don't feel like you'd need more unless you have hundreds of workflows triggering at the same time.
You should probably ask on n8n forum https://community.n8n.io/ then might give you interesting feedback regarding how big your hosting server should be.
from n8n-heroku.
To solve "Credentials could not be decrypted. The reason is that probably a different", you can refer to the method in this article to set
https://community.n8n.io/t/credentials-error/181/4
from n8n-heroku.
I had same error and fixed it with dotenv
Heroku dont allow static ports
from n8n-heroku.
Related Issues (17)
- github trigger node complains about running on localhost HOT 4
- Get more node, trigger HOT 2
- Dyno restarts HOT 1
- Failed to deploy HOT 1
- App crashes after 4 Months of usage HOT 10
- Install external library HOT 1
- n8n is on 0.0.130 now and not 0.0.96 HOT 2
- How do I mount a folder to run scripts within the n8n container? HOT 1
- Can't deploy to Heroku: python (no such package): HOT 2
- Is this the latest N8N version HOT 1
- Heruko button fails in creating a new app HOT 2
- How to update? HOT 2
- Customize n8n HOT 4
- After heroku become idle, the app wont wake up HOT 1
- How to update this to the new n8n version HOT 1
- App doesnt start after setup HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from n8n-heroku.