Rikudou_Sage

I only ever used SSH, so I don’t know.

IIRC, that’s exactly it. You can either use their GUI (which is not half bad) or you can use the docker command in the terminal after you install the package.

The easiest would be using docker, you can set up the container to always restart, that way it will be started automatically on NAS restart.

You can also download node.js from the Synology software center and manually add a cronjob to run after reboot, but the docker way is probably the best way to go.

IIRC, you can’t control to which port it’s bound which is not that useful.

As others have said, you have bound your host port 8080 to container port 9090 and then you use caddy to reverse proxy to container port 8080, which doesn’t exist.

As for DNS, it’s just a translation system - you send a domain, it returns its IP (for A or AAAA), everything else is done on server. So your current setup works.

Yes, you can deactivate the port, if you’re not gonna use it on the host, you don’t need it. Since you’re connecting via the internal network, you’re not using the bound ports.

As a side note, use some firewall and disable everything but 80, 443 and 22, you should not leave other ports open, especially if you’re binding all the ports in docker like that.

And perhaps make it a good habit to bind ports to 127.0.0.1 by default, that way no one outside the local server can access them. You can do it like this: “127.0.0.1:8080:9090”