Can't setup on Debian 13

[Mathildeuh]

Hello, i have an issue on your project,

➜  cloudnet-webinterface git:(main) pnpm run dev


> cloudnet-webinterface@0.8.2 dev /root/cloudnet-webinterface
> next dev --turbopack

⚠ Port 3000 is in use by process 710064
710066
710067
710068
710069
710070
710071, using available port 3001 instead.
▲ Next.js 16.2.6 (Turbopack)
- Local:         http://localhost:3001
- Network:       http://192.168.1.1:3001
- Environments: .env
✓ Ready in 347ms
⚠ Warning: Next.js inferred your workspace root, but it may not be correct.
 We detected multiple lockfiles and selected the directory of /root/yarn.lock as the root directory.
 To silence this warning, set `turbopack.root` in your Next.js config, or consider removing one of the lockfiles if it's not needed.
   See https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack#root-directory for more information.
 Detected additional lockfiles:
   * /root/cloudnet-webinterface/pnpm-lock.yaml

- Experiments (use with caution):
  · clientTraceMetadata
  ✓ rootParams
  · swcPlugins

⚠ Blocked cross-origin request to Next.js dev resource /_next/webpack-hmr from "192.168.1.1".
Cross-origin access to Next.js dev resources is blocked by default for safety.

To allow this host in development, add it to "allowedDevOrigins" in next.config.js and restart the dev server:

// next.config.js
module.exports = {
  allowedDevOrigins: ['192.168.1.1'],
}

Read more: https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins
 POST /en 200 in 1501ms (next.js: 568ms, proxy.ts: 205ms, application-code: 729ms)
 POST /en 200 in 88ms (next.js: 13ms, proxy.ts: 9ms, application-code: 65ms)
 POST /en 200 in 92ms (next.js: 12ms, proxy.ts: 8ms, application-code: 72ms)
 POST /en 200 in 92ms (next.js: 11ms, proxy.ts: 5ms, application-code: 76ms)
 POST /en 200 in 80ms (next.js: 11ms, proxy.ts: 6ms, application-code: 64ms)
 POST /en 200 in 81ms (next.js: 12ms, proxy.ts: 5ms, application-code: 64ms)
 POST /en 200 in 86ms (next.js: 11ms, proxy.ts: 7ms, application-code: 68ms)

When i login, the page reload and nothing appens. Did i do something wrong ?

Rest Module is configured like that:

{
  "maxContentLength": 5242880,
  "requestDispatchThreadLimit": 50,
  "disableNativeTransport": false,
  "corsConfig": {
    "allowedOrigins": [
      ".*"
    ],
    "allowedHeaders": [
      "*"
    ],
    "exposedHeaders": [],
    "allowCredentials": true,
    "allowPrivateNetworks": null,
    "maxAge": -1
  },
  "proxyMode": "DISABLED",
  "authConfig": {
    "jwtTokenLifetimeSeconds": 43200,
    "jwtRefreshTokenLifetimeSeconds": 259200,
    "ticketLifetimeSeconds": 15
  },
  "httpListeners": [
    {
      "host": "0.0.0.0",
      "port": 2812
    }
  ],
  "connectionInfoResolver": [],
  "sslConfiguration": null
}

[docimin]

Hi.

A few issues,

1. ⚠ Port 3000 is in use by process 710064, so you are forced to use port 3001 - please directly use the correct port instead of making the webinterface generate you one (this often causes issues)
2. ⚠ Blocked cross-origin request to Next.js dev resource /_next/webpack-hmr from "192.168.1.1".
   Cross-origin access to Next.js dev resources is blocked by default for safety.

To allow this host in development, add it to "allowedDevOrigins" in next.config.js and restart the dev server:

// next.config.js
module.exports = {
  allowedDevOrigins: ['192.168.1.1'],
}

[Mathildeuh]

Hi.

A few issues,

1. ⚠ Port 3000 is in use by process 710064, so you are forced to use port 3001 - please directly use the correct port instead of making the webinterface generate you one (this often causes issues)
2. ⚠ Blocked cross-origin request to Next.js dev resource /_next/webpack-hmr from "192.168.1.1".
   Cross-origin access to Next.js dev resources is blocked by default for safety.

To allow this host in development, add it to "allowedDevOrigins" in next.config.js and restart the dev server:

// next.config.js
module.exports = {
allowedDevOrigins: ['192.168.1.1'],
}

➜  cloudnet-webinterface git:(main) ✗ pnpm run dev

> cloudnet-webinterface@0.8.2 dev /root/cloudnet-webinterface
> next dev --turbopack

▲ Next.js 16.2.6 (Turbopack)
- Local:         http://localhost:3000
- Network:       http://192.168.1.1:3000
- Environments: .env
✓ Ready in 302ms
⨯ Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error
ReferenceError: module is not defined in ES module scope
This file is being treated as an ES module because it has a '.js' file extension and '/root/cloudnet-webinterface/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
    at <unknown> (next.config.js:1:1)

 ELIFECYCLE  Command failed with exit code 1.
➜  cloudnet-webinterface git:(main) ✗

➜  cloudnet-webinterface git:(main) ✗ cat next.config.js
module.exports = {
  allowedDevOrigins: ['192.168.1.1'],
}
➜  cloudnet-webinterface git:(main) ✗

192.168.1.1 is my VM ip

And 192.168.1.254 is my router

[docimin]

Well I know that, based from the Information I already sent you.

1. Why do you have a next.config.js? That's not part of the official repo.
2. I just updated the repo. Please clone this repository again as I don't know what other changes you have done.

• My guess is that you have a very old version which has vulnerabilities.

[Mathildeuh]

Well I know that, based from the Information I already sent you.

1. Why do you have a next.config.js? That's not part of the official repo.
2. I just updated the repo. Please clone this repository again as I don't know what other changes you have done.

• My guess is that you have a very old version which has vulnerabilities.

You told me to do it:

To allow this host in development, add it to "allowedDevOrigins" in next.config.js and restart the dev server:

// next.config.js
module.exports = {
  allowedDevOrigins: ['192.168.1.1'],
}

[Mathildeuh]

➜  cloudnet-webinterface git:(main) ✗ pnpm run dev

> cloudnet-webinterface@0.8.2 dev /root/cloudnet-webinterface
> next dev --turbopack

▲ Next.js 16.2.6 (Turbopack)
- Local:         http://localhost:3000
- Network:       http://192.168.1.1:3000
- Environments: .env
✓ Ready in 312ms
⚠ Warning: Next.js inferred your workspace root, but it may not be correct.
 We detected multiple lockfiles and selected the directory of /root/yarn.lock as the root directory.
 To silence this warning, set `turbopack.root` in your Next.js config, or consider removing one of the lockfiles if it's not needed.
   See https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack#root-directory for more information.
 Detected additional lockfiles:
   * /root/cloudnet-webinterface/pnpm-lock.yaml

- Experiments (use with caution):
  · clientTraceMetadata
  ✓ rootParams
  · swcPlugins

 GET /en 200 in 1420ms (next.js: 560ms, proxy.ts: 196ms, application-code: 664ms)
⚠ Blocked cross-origin request to Next.js dev resource /_next/webpack-hmr from "192.168.1.1".
Cross-origin access to Next.js dev resources is blocked by default for safety.

To allow this host in development, add it to "allowedDevOrigins" in next.config.js and restart the dev server:

// next.config.js
module.exports = {
  allowedDevOrigins: ['192.168.1.1'],
}

Read more: https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins
 POST /en 200 in 101ms (next.js: 17ms, proxy.ts: 9ms, application-code: 75ms)
 POST /en 200 in 88ms (next.js: 14ms, proxy.ts: 7ms, application-code: 67ms)

Still stuck on the login page

[docimin]

Again, 2 errors:

1. You need to add your IP in here: https://github.com/docimin/cloudnet-webinterface/blob/main/next.config.ts#L49
2. You also did not install the packages using pnpm

For proper installation, please check out the README