Development Error - "Compiled Successfully" but connection times out when trying to load the app. #29

Closed
opened 2026-02-04 16:40:24 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @jontstaz on GitHub (Sep 13, 2020).

I followed the steps listed under development. Successfully initialised a Postgresql DB using the docker-compose-dev.yml script. Installed all the dependencies in /server and /client with npm install, then ran 'npm run server:db:init' and finally 'npm start'. However when I visit my url:3000 in the browser, it says "ERR_CONNECTION_TIMED_OUT". I'm stumped.

I edited the .env file and put a secret key inside. Otherwise, everything was left as-is.

The only strange output after executing 'npm start' is "error: Ignoring attempt to bind route ('/*/') to unknown view: 'index'".

Screenshot of 'npm start' output below:

image

Originally created by @jontstaz on GitHub (Sep 13, 2020). I followed the steps listed under development. Successfully initialised a Postgresql DB using the docker-compose-dev.yml script. Installed all the dependencies in /server and /client with npm install, then ran 'npm run server:db:init' and finally 'npm start'. However when I visit my url:3000 in the browser, it says "ERR_CONNECTION_TIMED_OUT". I'm stumped. I edited the .env file and put a secret key inside. Otherwise, everything was left as-is. The only strange output after executing 'npm start' is "error: Ignoring attempt to bind route ('/*/') to unknown view: 'index'". Screenshot of 'npm start' output below: ![image](https://user-images.githubusercontent.com/6379873/93010332-c8411d00-f5ce-11ea-80d2-14fb7f6c707d.png)
Author
Owner

@meltyshev commented on GitHub (Sep 24, 2020):

Hi! Sorry for the long answer. The error about the «unknown view» is ok in development mode. Do you try to connect to http://localhost:3000 after start? Can you check if the port is open?

@meltyshev commented on GitHub (Sep 24, 2020): Hi! Sorry for the long answer. The error about the «unknown view» is ok in development mode. Do you try to connect to `http://localhost:3000` after start? Can you check if the port is open?
Author
Owner

@jontstaz commented on GitHub (Sep 25, 2020):

I did try to visit the URL but to no avail - it times out. Port 3000 is fine on my machine as I was able to run a different application within Docker after I experienced this issue with Planka. It also runs fine on 3000 when using the docker-compose file to pull the images from the external source, just doesn't work when pulling and compile the files directly in development mode.

@jontstaz commented on GitHub (Sep 25, 2020): I did try to visit the URL but to no avail - it times out. Port 3000 is fine on my machine as I was able to run a different application within Docker after I experienced this issue with Planka. It also runs fine on 3000 when using the docker-compose file to pull the images from the external source, just doesn't work when pulling and compile the files directly in development mode.
Author
Owner

@meltyshev commented on GitHub (May 12, 2025):

https://docs.planka.cloud/docs/development/set-up-environment

@meltyshev commented on GitHub (May 12, 2025): https://docs.planka.cloud/docs/development/set-up-environment
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#29