Env variable to disable Telemetry that is automatically enabled.

[mariushosting]

We should have an env variable to Disable Telemetry from the beginning in the docker compose.
Also the docker it starts but unable to registry any account the registry button doesn't work at all.
In the logs only the following:

---

Attention: Next.js now collects completely anonymous telemetry regarding usage.

This information is used to shape Next.js' roadmap and prioritize features.

You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:

https://nextjs.org/telemetry

✓ Ready in 1892ms

⚠ Webpack is configured while Turbopack is not, which may cause problems.

⚠ See instructions if you need to configure Turbopack:

https://nextjs.org/docs/app/api-reference/next-config-js/turbopack

○ Compiling / ...

✓ Compiled / in 5.7s

GET / 200 in 6243ms

⚠ Cross origin request detected from 192.168.1.18 to /_next/* resource. In a future major version of Next.js, you will need to explicitly configure "allowedDevOrigins" in next.config to allow this.

Read more: https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins

✓ Compiled /favicon.ico in 269ms

GET /favicon.ico?favicon.45db1c09.ico 200 in 589ms
°°°°°°°°°°°°°°°°

[yousbot]

Thank you so much for pointing that out. I wrote that issue somewhere and forgot to solve it.
You should get inside the docker containers (frontend, backend) : docker exec -it <container_name_or_id> /bin/bash
and add "frontend", "backend", "localhost" to /etc/hosts
Or renaming the containers would do the trick, but not sure if it will solve it. Next update will take care of that. I'll let you know.

[pqpxo]

Hey there!

I believe I have the same issue. I've created an account but attempting to 'Login' does nothing.

Can you confirm what needs adding to /etc/hosts file in order to resolve this?

[emhl]

as far as i can tell, the login request is currenlty being attempted by the client and not the server (frontend container).
if you look in your network dev-tools in the browser, you see a request being sent to http://backend:8000/user/register
which wouldn't resolve, since the client does not know where backend is and probably should not be able to access it anyways.

i can access backend:8000 from the frontend container, since the docker networking adds the routes for containers in the same network

$ curl backend:8000
{"message":"Hello World!"}

docker log:
paperion-backend   | INFO:     192.168.64.3:45252 - "GET / HTTP/1.1" 200 OK