'Not Found' when trying to access localhost

Had an issue with my initial install, and now when I try and run .bp again it looks like localhost:3000 is listening, but when I go there I just get redirected to http://localhost:3000/admin/ and get the error ‘Not Found’. In the console I just get: Failed to load resource: the server responded with a status of 404 (Not Found).

Any ideas?

hi @workingjb and welcome,

Can you please share the output log of Botpress this would help investigate the issue.

Thanks,
Seb

Hi @Seb,

Here is the output log:

Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) CMS (info)  Loaded 9 content types
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) Server (warn)  Botpress Pro must be enabled to use a custom theme and customize the branding.
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) Server (error)  Error deploying assets [Error, EACCES: permission denied, open '/Users/username/Library/Application Support/botpress/pre-trained/lid.176.ftz']
STACK TRACE
Error: EACCES: permission denied, open '/Users/username/Library/Application Support/botpress/pre-trained/lid.176.ftz'
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) HTTP (warn)  External URL is not configured. Using default value of http://localhost:3000. Some features may not work properly
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) Server (info)  Discovered 0 bots
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) Server (info)  Local Action Server will only run in experimental mode
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) Server (info)  Started in 1238ms
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) Launcher (info)  Botpress is listening at: http://localhost:3000
Fri May 14 2021 09:39:48 GMT-0700 (Pacific Daylight Time) Launcher (info)  Botpress is exposed at: http://localhost:3000

However, looking at the lid.176.ftz file it appears that everyone should have write access to it:

Thoughts?

Seems like running ./bp with sudo from the terminal seemed to solve the issue :? Really not sure why, but must have been some permissions disconnect along the path.

Thanks!

Hey @workingjb

Yes from the error log it look like the issue is caused by permissions but I’m not sure I know why.

Have you found the solution?

Thanks,

Seb

@Seb never did find the root cause. Just opened up all the permissions and now it’s working as expected.

Thanks!

1 Like