github-actions[bot]
commented
2 years ago Closed cwesterfield closed 1 year ago
github-actions[bot]
commented
2 years ago github-actions[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
andyongxa
commented
2 years ago i have the same issues
github-actions[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
taintedkernel
commented
2 years ago I'm running on Kubernetes with the recommended Helm chart and running a similar problem:
root@hedgedoc-7746789df-gm5s8:/opt/hedgedoc/bin# ./manage_users --reset user@email.com
/bin/sh: 1: git: not found
(node:460) UnhandledPromiseRejectionWarning: SequelizeConnectionRefusedError: connect ECONNREFUSED 127.0.0.1:5432
at Client._connectionCallback (/opt/hedgedoc/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:170:24)
at Client._handleErrorWhileConnecting (/opt/hedgedoc/node_modules/pg/lib/client.js:305:19)
at Client._handleErrorEvent (/opt/hedgedoc/node_modules/pg/lib/client.js:315:19)
at Connection.emit (events.js:314:20)
at Socket.reportStreamError (/opt/hedgedoc/node_modules/pg/lib/connection.js:52:12)
at Socket.emit (events.js:314:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:460) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:460) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.In my case, it seems that the binary cannot connect to the webserver; I imagine running a k8s environment things may be different, but I did not see any option to specify a URL or host to override the default.
Edit: Scratch that, I was able to find a way with help from this comment.
github-actions[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
MikeRatcliffe
commented
1 year ago I have the same issue :(
blaa
commented
1 year ago It seems problem occurs when the domain doesn't contain at least one dot. At least in my case. @internal - hangs, @internal.poo - works.
Some weird, unnecessary assumptions in play.
aptalca
commented
1 year ago This really should be reported to upstream and tracked there as it seems to be an app issue rather than a container issue. We don't develop the app, but only publish the container
tao-zamorano
commented
1 year ago Using NODE_DEBUG=net hinted that some network values were missing.
Setting CMD_DB_URL=mysql://hedgedoc:some-pass@hedgedoc_mariadb:3306/hedgedoc, as suggested by taintedkernel, solved the problem for me.
github-actions[bot]
commented
1 year ago This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
SteveDinn
commented
1 year ago I think this should be fixed. It seems really weird and very non-intuitive that the CMD_DB_URL environment variable is required when it could be composed from the other environment variables already required by the docker container.
github-actions[bot]
commented
1 year ago This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
github-actions[bot]
commented
1 year ago This issue is locked due to inactivity
Expected Behavior
root@bc4413c963ad:/app/hedgedoc/bin# ./manage_users --add test@test
It should ask for a password and create an account
Current Behavior
root@bc4413c963ad:/app/hedgedoc/bin# ./manage_users --add test@test
just hangs indefinitely
Steps to Reproduce
/app/hedgedoc/bin./manage_users --add test@testEnvironment
OS: Debian CPU architecture: x86_64 How docker service was installed: from debian repo
Command used to create docker container (run/create/compose/screenshot)
Docker logs