global prefix doesn't work

[codeweb05]

if I set global prefix on the api, the bull board ui doesn't work

app.setGlobalPrefix('api')

[Kirkify]

Had a similar problem, but this was fixed in version 5.5.2 (See this PR) Follow this example here. When he sets the base path of the server adapter here Line 58. Update it with your base path (so if it's 'api' like you wrote above then /api/queues and it should work.

Or another way is just modify your app.setGlobalPrefix to have a slash in front so app.setGlobalPrefix('/api') in your case.

[VaZark]

~~I'm using the with-nestjs-module example.~~

~~Is it not possible to use the routes & boardOptions in the BullBoardModule.forRoot params along with the global prefix instead of creating a separate module just for config?~~

~~going through the package, this line, implies that global prefix is respected but I get the same loading error too :(~~

I just missed an "s"

[felixmosh]

@codeweb05 does @Kirkify response solved your issue?

[felixmosh]

@codeweb05, does #639 solves your issue?

[henrysachs]

this issue is still present for me today. I just set the / beforeapi and now it works :)

[NatashkinAlex]

I have some problem( I use @bull-board/nestjs with fastify

[vvtri]

~I'm using the with-nestjs-module example.~

~Is it not possible to use the routes & boardOptions in the BullBoardModule.forRoot params along with the global prefix instead of creating a separate module just for config?~

~going through the package, this line, implies that global prefix is respected but I get the same loading error too :(~

I just missed an "s"

I have the same problem when using nestjs with fastify adapter, global prefix and nestjs bull board module. Can you show me how you fix this ?

[selabie68]

I have this same issue when using fastify.

Adding / before api does not fix the issue for fastify, it might fix it for express only.

Seems related to this line where on the fastify adapter we are overriding the prefix option.

PR #639 does resolve the issue for me though.

[Ttou]

have this same issue when using fastify.

my plan is using pnpm patch to modity the package.

[felixmosh]

@codeweb05, can you check if #704 solves this issue?