Windows VPS Node Deployment Fix
Budget: $10 – $30 USD
The code for my web-based gaming bot panel is complete—Next.js on the frontend, Node.js on the backend, a custom Node.js agent, all talking to a MySQL database—yet the current deployment on my Windows VPS is anything but clean. Nginx is supposed to reverse-proxy the traffic, but port clashes among XAMPP, the Node services, and Nginx keep breaking the stack and the dashboard never reaches our domain without throwing 502s.
I need someone who is fluent in Windows Server administration, Node.js, Next.js and Nginx to reinstall everything from scratch and hand the server back in a “zero-error” state. Environment variables must be consolidated into a single .env file, the three services (frontend on :3000, backend on :3001, agent on :3002) need to talk to each other flawlessly, and the public site must load on our custom domain without a hitch.
Deliverables I will use to accept the job:
• Conflict-free port mapping among XAMPP, Node apps and Nginx
• Working Nginx reverse-proxy rules that load the dashboard on the root domain and route API traffic correctly
• Verified API connectivity between the three services (manual test calls will return 200 OK)
• A single, well-documented .env file with all variables referenced in code
• Written deployment steps or a small script so I can replicate the setup on a fresh VPS if needed
If you can jump in quickly and leave me with a bullet-proof deployment, let’s get started.
I need someone who is fluent in Windows Server administration, Node.js, Next.js and Nginx to reinstall everything from scratch and hand the server back in a “zero-error” state. Environment variables must be consolidated into a single .env file, the three services (frontend on :3000, backend on :3001, agent on :3002) need to talk to each other flawlessly, and the public site must load on our custom domain without a hitch.
Deliverables I will use to accept the job:
• Conflict-free port mapping among XAMPP, Node apps and Nginx
• Working Nginx reverse-proxy rules that load the dashboard on the root domain and route API traffic correctly
• Verified API connectivity between the three services (manual test calls will return 200 OK)
• A single, well-documented .env file with all variables referenced in code
• Written deployment steps or a small script so I can replicate the setup on a fresh VPS if needed
If you can jump in quickly and leave me with a bullet-proof deployment, let’s get started.