R3ap3r/nixpanel-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: resolve EADDRINUSE port conflict — Node.js now listens on internal port 4000

Browse Source 
Nginx listens publicly on 2087/2083 and reverse-proxies to 127.0.0.1:4000.
Previously both Nginx and Node.js were trying to bind port 2087 causing the
nixpanel service to crash-loop. HOST changed to 127.0.0.1 so the API is
not directly reachable from outside.

Bumps version to 0.3.1.
This commit is contained in:
NixReaper
2026-04-05 12:21:28 -05:00
parent d3ef236add
commit 75394fcaa5
10 changed files with 30 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
server/src/index.ts
+4 -3
View File
@@ -13,10 +13,11 @@ async function start() {
app = await buildApp()
// NixServer on port 2087
// Node.js listens on internal port (Nginx proxies public 2087/2083 → here)
await app.listen({ port: config.server.nixserverPort, host: config.server.host })
console.log(`NixServer running on port ${config.server.nixserverPort}`)
console.log(`NixClient API running on port ${config.server.nixserverPort} (/api/cpanel)`)
console.log(`NixPanel API running on ${config.server.host}:${config.server.nixserverPort}`)
console.log(`NixServer admin → http://127.0.0.1:${config.server.nixserverPort}/api/`)
console.log(`NixClient user → http://127.0.0.1:${config.server.nixserverPort}/api/cpanel/`)
} catch (err) {
console.error('Failed to start server:', err)