[GH-ISSUE #3491] [bug]: continuous error print in log #1182

New issue

Open

opened 2026-03-16 19:01:01 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 19:01:01 +03:00

Owner

Originally created by @pankajmyt on GitHub (Nov 3, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3491

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I am seeing following log snippet constantly being dumped by the backend docker container.

docker container logs a9f650acf92a --follow

[Nest] 19  - 10/30/2023, 7:30:34 AM   ERROR [ExceptionsHandler] team/member_not_found
Error: team/member_not_found
    at GqlTeamMemberGuard.canActivate (/usr/src/app/dist/team/guards/gql-team-member.guard.js:37:19)
    at async GuardsConsumer.tryActivate (/usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/guards/guards-consumer.js:16:17)
    at async canActivateFn (/usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-context-creator.js:158:33)
    at async target (/usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-context-creator.js:76:31)
    at async /usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-proxy.js:9:24

Steps to reproduce

Try to follow backend docker container logs

Environment

Production

Version

Self-hosted

Originally created by @pankajmyt on GitHub (Nov 3, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3491 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I am seeing following log snippet constantly being dumped by the backend docker container. ``` docker container logs a9f650acf92a --follow ``` ``` [Nest] 19 - 10/30/2023, 7:30:34 AM ERROR [ExceptionsHandler] team/member_not_found Error: team/member_not_found at GqlTeamMemberGuard.canActivate (/usr/src/app/dist/team/guards/gql-team-member.guard.js:37:19) at async GuardsConsumer.tryActivate (/usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/guards/guards-consumer.js:16:17) at async canActivateFn (/usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-context-creator.js:158:33) at async target (/usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-context-creator.js:76:31) at async /usr/src/app/node_modules/.pnpm/@nestjs+core@9.2.1_@nestjs+common@9.2.1_@nestjs+platform-express@9.2.1_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-proxy.js:9:24 ``` ### Steps to reproduce Try to follow backend docker container logs ### Environment Production ### Version Self-hosted

kerem added the

bug

need testing

self-host

labels

2026-03-16 19:01:01 +03:00

kerem commented

2026-03-16 19:01:12 +03:00

Author

Owner

@nicklasring commented on GitHub (Jul 3, 2025):

We also encountered this, might have been triggered by adding a workspace with owner (email) that does not exist

@nicklasring commented on GitHub (Jul 3, 2025): We also encountered this, might have been triggered by adding a workspace with owner (email) that does not exist

kerem commented

2026-03-16 19:01:17 +03:00

Author

Owner

@syorito-hatsuki commented on GitHub (Jul 25, 2025):

I see same issue. I have only 1 namespace and 1 user authorized using Github OAuth (else disabled)

UPD: Removed all workspace, error stay. Removed user, error stops

@syorito-hatsuki commented on GitHub (Jul 25, 2025): I see same issue. I have only 1 namespace and 1 user authorized using Github OAuth (else disabled) UPD: Removed all workspace, error stay. Removed user, error stops