GUI devices list not adding port to url

[Semicolon7645]

I have two docker containers running the image: instantlinux/nut-upsd. Which serves two NUT servers, one on port 34931 and another on 34932. One for each of the two UPSs connected to my server. In my nutcase.yaml I set the appropriate port for each of the entries in the servers section. But when loading up the web gui, the devices list does not add the port to the url, so it cannot connect to NUT server: http://nutcase.my.domain/?addr=192.168.50.4&dev=cyberpower_margo&mode=nut, but if I manually add the port in the address has l bar it works just fine: http://nutcase.my.domain/?addr=192.168.50.4&dev=cyberpower_margo&mode=nut&port=34931

Am I missing some sort of configuration to add the port to the url?

rework:
settings:
  log_level: info
  order_metrics: True
  coloured_log: True
  default_log_lines: 20
webhooks:
  ok: #http://nutcase.my.domain:80/api/push/xxxxxxxxxxxx?status=up&msg=OK&ping=
  fail: #http://nutcase.my.domain:80/api/push/yyyyyyyyyyyy?status=down&msg=OK&ping=
servers:
  - server: "192.168.50.4"
    port: 34932
    default: true
    mode: 'nut'
    devices:
      - device: 'apc_ont'
        power: 450
        displayname: 'APC Ont'
  - server: "192.168.50.5"
    port: 3493
    mode: 'nut'
    devices:
      - device: 'cyberpower_asus'
        power: 1000
        displayname: 'CyberPower Asus'
  - server: "192.168.50.3"
    port: 3493
    mode: 'nut'
    devices:
      - device: 'ups'
        power: 1000
        displayname: 'CyberPower Issac'
  - server: "192.168.50.4"
    port: 34931
    username: monuser
    devices:
      - device: 'cyberpower_margo'
        power: 1000
        displayname: 'CyberPower Margo'

[ArthurMitchell42]

hi Colin, What you’re doing is quite unusual, the nut daemon doesn’t usually get run twice on the same machine. If you have 2, or more, UPS’s on a machine it expects you to configure the daemon once, listing both/all devices. I’m not surprised nutcase isn’t doing quite the right thing here since this is an atypical setup. With out a deep dive I can’t say if I could adapt nutcase for this but what you're doing is so niche I’m not sure it would be a good idea to do so. Is there a specific reason you have to use this unusual configuration please? Arthur (Ô,Ô) ({::::}) =WW===- Sent by owl post

…

________________________________ From: Collin ***@***.***> Sent: Tuesday, November 26, 2024 4:23:35 PM To: ArthurMitchell42/nutcase ***@***.***> Cc: Subscribed ***@***.***> Subject: [ArthurMitchell42/nutcase] GUI devices list not adding port to url (Discussion #69) I have two docker containers running the image: instantlinux/nut-upsd. Which servers two NUT servers, one on port 34931 and another on 34932. One for each of the two UPSs connected to my server. In my nutcase.yaml I set the appropriate port for each of the entries in the servers section. But when loading up the web gui, the devices list does not add the port to the url, so it cannot connect to NUT server: http://nutcase.my.domain/?addr=192.168.50.4&dev=cyberpower_margo&mode=nut, but if I manually add the port it works just fine: http://nutcase.my.domain/?addr=192.168.50.4&dev=cyberpower_margo&mode=nut&port=34931 Am I missing some sort of configuration to add the port to the url? rework: settings: log_level: info order_metrics: True coloured_log: True default_log_lines: 20 webhooks: ok: #http://nutcase.my.domain:80/api/push/xxxxxxxxxxxx?status=up&msg=OK&ping= fail: #http://nutcase.my.domain:80/api/push/yyyyyyyyyyyy?status=down&msg=OK&ping= servers: - server: "192.168.50.4" port: 34932 default: true mode: 'nut' devices: - device: 'apc_ont' power: 450 displayname: 'APC Ont' - server: "192.168.50.5" port: 3493 mode: 'nut' devices: - device: 'cyberpower_asus' power: 1000 displayname: 'CyberPower Asus' - server: "192.168.50.3" port: 3493 mode: 'nut' devices: - device: 'ups' power: 1000 displayname: 'CyberPower Issac' - server: "192.168.50.4" port: 34931 username: monuser devices: - device: 'cyberpower_margo' power: 1000 displayname: 'CyberPower Margo' — Reply to this email directly, view it on GitHub<#69>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATTOABRW5X2S7Y3QPRODWYL2CSOAPAVCNFSM6AAAAABSQ2Z4YSVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGU2TSOBVG4>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Semicolon7645]

It definitely is an unusual setup. Initially I was going to setup NUT on the bare-metal, but something about it caused so many other issues with my Docker environment. So I switched to the dockerize version of nut-upsd: https://hub.docker.com/r/instantlinux/nut-upsd. In the documentation on the Docker Hub page, they state that the image is setup for only one device and to run multiple containers if you have multiple UPSs.

[Semicolon7645]

NUTCase works absolutely fine if I use the port parameter manually:

I haven't looked into the code at all, but would adding a condition if the port set in the nutcase.yaml isn't the default 3493 NUT port, add it to the link in the Devices list be possible?