NestJS controller not mapped

Question

So I have an API that will be deployed in a docker container. This API has the authentications controller, simple and not something special.

When I start up the API in development mode on my local machine, the auth controller will be found and everything is working fine. Same for building and running it on my local machine. But when I'll dockerize the project and run it on a virtual machine, then I'll can't access the auth controller. Every other controller is working finde, but the auth controller doesn't exist.

Looking into the docker logs, no auth controller will be mapped. Both local and builded docker images should contain the same project files.

auth controller:

import {
  Controller,
  Post,
  Delete,
  UseGuards,
  Request,
  Body,
} from '@nestjs/common';

import { AuthenticationsService } from './authentications.service';
import { JwtAuthGuard } from '../shared/guards/jwtAuth.guard';
import { SignInDTO } from './dtos/addGraphNodeToGraphByGraphId.dto';

@Controller('authentications')
export class AuthenticationsController {
  constructor(
    private readonly authenticationsService: AuthenticationsService,
  ) {}

  @Post()
  public signIn(@Body() { username, password }: SignInDTO): Promise<string> {
    return this.authenticationsService.signIn(username, password);
  }

  @Delete()
  @UseGuards(JwtAuthGuard)
  public signOut(@Request() request): Promise<void> {
    return this.authenticationsService.signOut(
      request.encodedToken,
      request.user.tokenExpirationSinceEpochInMilliseconds,
    );
  }
}

Error:

{
    "statusCode": 404,
    "message": "Not Found",
    "error": "Cannot POST /authentications"
}

What could cause that the authentications controller will not be mapped?

If you modify an existing controller, does it repercutes the modification in the docker container ? — Marco
– Marco, Commented Jun 24, 2020 at 7:38
Put code of module which requires this controller into the question. Maybe there is something here. Also which operation systems do you have locally and in docker? — Yevhenii
– Yevhenii, Commented Jun 25, 2020 at 13:57

Utsav Barnwal · Accepted Answer · 2021-05-03 23:35:24Z

35

If you have already tried everything else and nothing worked, try deleting the dist folder. That's what worked for me.

answered May 3, 2021 at 23:35

Utsav Barnwal

1,21915 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Konstantin Schütte Over a year ago

I already found a solution: stackoverflow.com/a/62591471/8408576

Utsav Barnwal Over a year ago

The selected answer didn't work for me so, I shared mine just in case anybody else is facing the same thing.

Douglas Caina Over a year ago

turnout my build was not compiling so intellij was just using the last working version :facepalm: thanks!

bashleigh · Accepted Answer · 2020-06-18 14:59:10Z

7

Did you put the controller in the module?

@Module({
  controllers: [AuthenticationController],
})
export class AppModule {}

answered Jun 18, 2020 at 14:59

bashleigh

9,4245 gold badges33 silver badges50 bronze badges

1 Comment

Konstantin Schütte Over a year ago

Yes, I guess if I wouldn't have done that it would also not work on my local machine

befabry · Accepted Answer · 2022-12-09 10:57:24Z

5

Finally found out that some packages from NestJS had version 6 and 7. So they propably interrupted each other. An indicator was this flood of warnings:

After running nest update -f every controller was mapped as it was supposed.

Edit :

As of NestJS version 9, the update command has been removed.

See here : Migration Guide - CLI

edited Dec 9, 2022 at 10:57

befabry

8126 silver badges13 bronze badges

answered Jun 26, 2020 at 9:04

Konstantin Schütte

1,0192 gold badges18 silver badges50 bronze badges

Comments

micahhoover · Accepted Answer · 2020-10-29 15:48:10Z

2

I had the same problem as the OP, but it was because I didn't restart my NestJS server after I added that endpoint to the controller.

Also, I'm used to npm start in other contexts auto-updating the server without restart (React, React Native, I think node?).

answered Oct 29, 2020 at 15:48

micahhoover

2,1608 gold badges35 silver badges57 bronze badges

Comments

erevos13 · Accepted Answer · 2020-06-28 07:29:06Z

0

did you add it to your app module? The Module of auth.

answered Jun 28, 2020 at 7:29

erevos13

4114 silver badges14 bronze badges

Comments

AGD · Accepted Answer · 2022-04-19 01:08:44Z

0

I also encountered this problem on the server I deployed yesterday. After a day of research, I was using the master branch, and my code kept pushing to the dev branch, so I hope someone can check that as well.

answered Apr 19, 2022 at 1:08

AGD

1518 bronze badges

Comments

Adeoluwa Philip · Accepted Answer · 2022-06-19 11:23:23Z

0

You can also confirm for typo you're missing the @ for @Module() in any of the affected modules usually the app.module.ts

answered Jun 19, 2022 at 11:23

Adeoluwa Philip

3163 silver badges6 bronze badges

Comments

Mongoname · Accepted Answer · 2025-02-20 06:18:09Z

0

My issue was not correct log level. Routes mapped incorrectly (wrong path), and log level (use pino) was not debug, so i thought, that routes did not mapped at all.

answered Feb 20 at 6:18

Mongoname

639 bronze badges

Collectives™ on Stack Overflow

NestJS controller not mapped

8 Answers 8

3 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

8 Answers 8

3 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related