mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3714] [bug]: Selfhosted hoppscotch backend container retrun an error with mail #1287
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1287
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AhmedmmAli on GitHub (Jan 3, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3714
Is there an existing issue for this?
Current behavior
I'm trying to deploy hoppscotch self hosted on a VM, I configured the .env file and build the containers but the backend container keeps restarting and retrun this error with the email feature
Backend Server | [Nest] 45 - 01/03/2024, 4:08:36 PM ERROR [ExceptionHandler] Cannot create property 'mailer' on string 'XXXXXX' Backend Server | TypeError: Cannot create property 'mailer' on string 'XXXX' Backend Server | at new Mail (/usr/src/app/node_modules/.pnpm/nodemailer@6.9.1/node_modules/nodemailer/lib/mailer/index.js:45:33) Backend Server | at module.exports.createTransport (/usr/src/app/node_modules/.pnpm/nodemailer@6.9.1/node_modules/nodemailer/lib/nodemailer.js:53:14) Backend Server | at MailerTransportFactory.createTransport (/usr/src/app/node_modules/.pnpm/@nestjs-modules+mailer@1.9.1_@nestjs+common@10.2.7_@nestjs+core@10.2.7_nodemailer@6.9.1/node_modules/@nestjs-modules/mailer/dist/mailer-transport.factory.js:13:49) Backend Server | at new MailerService (/usr/src/app/node_modules/.pnpm/@nestjs-modules+mailer@1.9.1_@nestjs+common@10.2.7_@nestjs+core@10.2.7_nodemailer@6.9.1/node_modules/@nestjs-modules/mailer/dist/mailer.service.js:55:54) Backend Server | at Injector.instantiateClass (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/injector/injector.js:365:19) Backend Server | at callback (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/injector/injector.js:65:45) Backend Server | at async Injector.resolveConstructorParams (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/injector/injector.js:144:24) Backend Server | at async Injector.loadInstance (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/injector/injector.js:70:13) Backend Server | at async Injector.loadProvider (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/injector/injector.js:97:9) Backend Server | at async /usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/injector/instance-loader.js:56:13 Exiting process because Backend Server exited with code nullSteps to reproduce
add .env file
docker-compose up -d
Environment
Production
Version
Self-hosted
@AhmedmmAli commented on GitHub (Jan 8, 2024):
@liyasthomas
@balub commented on GitHub (Jan 11, 2024):
@AhmedmmAli Can you share your
.envfile so that it may help us identify any issues in it?