poolConfig.json & poolState.json copied to new install can not be viewed by dashPanel

[2delarosa]

I suspect that I have a file entry missing or incorrect. I did a fresh installed and copied the files from data folder. In dashPanel, I can search and find my nodejspoolcontroller but it errors out when I select it. Also manually entering the IP address errors it out. It appears that it appends /upnp.xml. I go to that address and it doesn't load so I figured it must be a configuration entry in nodejs-poolcontroller. Here is the error log from dashPanel

`192.168.100.3 GET /config/findPoolControllers?null

URL {
href: 'http://192.168.100.39:4201/upnp.xml',
origin: 'http://192.168.100.39:4201',
protocol: 'http:',
username: '',
password: '',
host: '192.168.100.39:4201',
hostname: '192.168.100.39',
port: '4201',
pathname: '/upnp.xml',
search: '',
searchParams: URLSearchParams {},
hash: ''
}
http://192.168.100.39:4201/upnp.xml
error: Error resolving host names: getHostByAddr ENOTFOUND 192.168.100.39
done searching for poolController`

I search the discussions but I didn't find anything yet. I appreciate if you can point me where I should look.

[tagyoureit]

Error resolving host names: getHostByAddr ENOTFOUND 192.168.100.39

This means that nodejs-poolController isn't running at that address or dashPanel can't access it. njsPC typically runs on port 4200, not 4201.

When njsPC starts up, you can see what ports it is listening on in the logs. ie [10/22/2025, 5:33:58 PM] info: Server is now listening on 0.0.0.0:4200 - 10.0.0.225:4200.

You should be able to access the njsPC endpoint directly. http://10.0.0.250:4200/state/all or http://10.0.0.250:4200/config/all which will be what's currently in the state and config json files, respectively.

In short, it looks like you have a networking issue.

[2delarosa]

Sure enough, njsPC is advertising on 4201. I must have enabled the https under the web section in the config.json file some time ago. So I should set it to false and it will stop advertising on 4201. Is that correct?

[10/22/2025, 9:47:42 AM] info: Server is now listening on 0.0.0.0:4200 - 192.168.100.39:4201

  "web": {
    "servers": {
      "http2": {
        "enabled": false,
        "uuid": "dc2682c8-6b75-4b69-9d56-1b6a74b9412d"
      },
      "http": {
        "enabled": true,
        "ip": "0.0.0.0",
        "port": 4200,
        "httpsRedirect": false,
        "authentication": "none",
        "authFile": "/users.htpasswd",
        "uuid": "cf5d3225-f755-4136-b748-e2b2d7a685e2"
      },
      "https": {
        "enabled": true,
        "ip": "0.0.0.0",
        "port": 4201,
        "authentication": "none",
        "authFile": "/users.htpasswd",
        "sslKeyFile": "",
        "sslCertFile": "",
        "uuid": "08dbcc25-85a5-4411-883a-e1d55f5c6b43"
      },
      "mdns": {
        "enabled": false,
        "uuid": "753162c9-3abd-4a2c-8809-c84e75c45d94"
      },
      "ssdp": {
        "enabled": true,
        "uuid": "96ec3ad6-c8f8-4f7d-9eff-4775582876e0"
      }
    },

[tagyoureit]

4201 is the port for https. Most people don't use that as this app is best run in your own personal network. I would just use the http 4200 port unless you have very specific requirements for https.