[Bug]: impossible to access to the tuono web app for apps/documentation

[spacecodeur]

Description

I want to access to the tuono's documentation web app but after clone and configure the repo I got an NS_ERROR_CONNECTION_REFUSED in my browser.

My PC specs :

The OS: Debian 12 (Bookworm)
node -v: 22.11.0
pnpm -v: 9.14.2
cargo -V: 1.83.0 (5ffbef321 2024-10-29)

Before to run anything :

• the command sudo netstat -pln | grep "3000\|3001" doesn't return anything (no app listen ports 3000 or 3001)
• the output of sudo iptables -L -n -v :

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination 

Expected behaviour

After clone and configure the tuono source code's repo, I expect to load the main page of the documentation when I run it in local with the urls :

• http://localhost:3000
• http://127.0.0.1:3000

How to reproduce

The case where tuono-cli doesn't work as expected :

Case 1 : I build the tuono-cli and try to run the dev server in tuono-source-code/apps/documentation

• clone and move into repo
• run pnpm install and cargo build
• add tuono new binary to global PATH
• go to "apps/documentation" dir
• run tuono dev

Then open my favorite browser on "http://localhost:3000" (I try also with another browsers like chrome or brave during my tests ;) )
=> I got a page when the error "Unable to connect"

The commands :

git clone [email protected]:tuono-labs/tuono.git && cd tuono && \
pnpm install && cargo build && \
export PATH=$(pwd)/target/debug:$PATH && \
cd apps/documentation && \
tuono dev

The cases where tuono-cli works well :

Case 2 : I build the tuono-cli and try to run the dev server in a new project

• clone and move into repo
• run pnpm install and cargo build
• add tuono new binary to global PATH
• go outside the repo dir and create a new tuono project and move inside
• run pnpm install and tuono dev

Then open my browser on "http://localhost:3000" => I got the expected page !

The commands :

git clone [email protected]:tuono-labs/tuono.git && cd tuono && \
pnpm install && cargo build && \
export PATH=$(pwd)/target/debug:$PATH && \
cd .. && tuono new tempProject && cd tempProject && \
pnpm install && tuono dev

Case 3 : I install tuono-cli and try to run the dev server in a new project

• install tuono via cargo
• create a new tuono project and move inside
• run pnpm install and tuono dev

Then open my browser on "http://localhost:3000"

The commands :

cargo install tuono

Then :

tuono new tempProject2 && cd tempProject2 && \
pnpm install && tuono dev

Then open my browser on "http://localhost:3000" => I got the expected page !

Screenshots

No response

System Info

System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900K
    Memory: 53.09 GB / 62.55 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 22.11.0 - ~/apps/nodejs/bin/node
    npm: 10.9.0 - ~/apps/nodejs/bin/npm
    pnpm: 9.14.2 - ~/apps/nodejs/bin/pnpm
  Browsers:
    Brave Browser: 131.1.73.104
    Chrome: 131.0.6778.204

System info (Rust)

rustc 1.83.0 (90b35a623 2024-11-26)
cargo 1.83.0 (5ffbef321 2024-10-29)
bash: tuono: command not found (if I install tuono with `cargo install tuono`, its 0.17.0)

Additional context

Initially, I had proposed adding a Docker image via a pull request.
This PR is almost complete: the last issue on my machine is that when I try to start the web server for the Tuono documentation from my container, my browser fails to display the expected page.

I then configured my host machine to try reproducing the problem, and it persists (so I can rule out Docker as a potential cause).

[Valerioageno]

Thanks for the detailed issue! Will investigate on this asap!

[spacecodeur]

I have another laptop on Debian Bookworm and I have the same issue..
But this issue is not urgent for me, though. I have a dual boot with Windows, and it works perfectly on this OS. I can work on Windows... despite my strong preference for Debian. ;)

[Valerioageno]

That is weird because the docker image you are developing is Debian bookworm and works on our computers. Let me know if you find the rootcause!