ProxmoxVE: Internal Error when configuring streams in NPM LXC installation

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

nginxproxymanager.sh

📂 What was the exact command used to execute the script?

bash -c “$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/nginxproxymanager.sh)”

📝 Provide a clear and concise description of the issue.

When attempting to configure streams in Nginx Proxy Manager (NPM) LXC, the UI consistently returns an “Internal Error” message. The system logs indicate a structuredClone is not defined error, probably a potential Node.js version compatibility issue(?)

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. Install NPM in a Proxmox LXC container using the community scripts
  2. Navigate to Streams configuration on the NPM web interface
  3. Configure any new stream, for example:

Incoming Port: 25565 Forward Host: crafty.home.arpa Forward Port: 25565 TCP Forwarding enabled

  1. Click Save

Expected Behavior:

Image

Actual Behavior:

Image

❌ Paste the full error output (if available).

System logs (journalctl -u npm -f): Feb 19 07:25:29 nginx-manager node[3594]: [2/19/2025] [7:25:29 AM] [Express ] › ⚠ warning structuredClone is not defined

🖼️ Additional context (optional).

  1. Issue has been verified on fresh NPM LXC installation. The only change from default settings was the configuration of VLAN during LXC creation and disabling IPv6, which was necessary for network connectivity in my environment. All other settings were left at their defaults.
  2. Tested with different stream configurations (Minecraft/Crafty server ports, RustDesk ports) - same error persists
  3. HOWEVER, it was SUCCESSFULLY tested on a fresh Alpine Docker LXC created using the proxmox script with the following docker-compose configuration:
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    network_mode: "host"
    environment:
      DISABLE_IPV6: 'true'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    healthcheck:
      test: ["CMD", "/usr/bin/check-health"]
      interval: 10s
      timeout: 3s

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 17 (6 by maintainers)

Most upvoted comments

I had exactly the same issue. The problem was the Node.js version (16). structuredClone is added as of version 17.

Here is how I fixed it. Type in your LXC console:

  • npm install n -g
  • n stable

Restart your LXC. Hope this helps you as well.

@akhdanfadh I’m gonna go ahead and disappoint you right off the bat, majority of apps here turned into LXC’s are Dockerfiles/Makefiles translated into bare metal installs. Are you gonna call them all workarounds? 😃

The support i’m talking about, the one you call “better” is the one who produced the problem you have. The streams issue has been reported countless time on THEIR OFFICIAL GIHTUB and its not fixed for people who have it, so it CAN’T BE FIXED HERE BECAUSE OF THAT. Have to write it in caps, because you seem to refuse to accept facts for some reason. Not sure why you’re so defensive about this.

I tested @timtjtim service file fix, it didnt fix the issue at my test LXC, so the issue is not in Node. Its in the app source. Nowhere in their source code is said that you have to use NVM, or that they use it… As there is a saying “Doing more of the same and expecting different result is definition of insanity”, meaning that we can install the same Node version from every possible repo out there, its gonna work the same.

I’m sorry that you feel you’re wasting your mental, but thats how life is. I’m just saying that your issue won’t go away because official docker install got that same issue reported