"Re-detect IP/Port" returns incorrect port for Web UI.

[MadsBen]

✅ Have you read and understood the above guidelines?

Yes

📝 Provide a clear and concise description of the issue.

In version 0.5.1, new install, the "Re-detect IP/Port" function always returns port ":80" for the LXC Web UI and not the actual port of the Web UI.

🔄 Steps to reproduce the issue.

Step 1: Select a LXC in the "Installed Scripts" section.
Step 2: For the chosen LXC, select "Action" -> "Re-detect IP/Port".

Result: Script returns correct IP-address, but port = 80, not the actual port of the Web UI.

❌ Paste the full error output (if available).

For example, PeaNUT is port 3000. Script detects port 80, which is incorrect.

The same applies to all LXC and scripts.

🖼️ Additional context (optional).

No response

[michelroegl-brunner]

I am not able to recreate the issue, can you Re-Detect the IP via the Actions button and post the logs from journalctl -u pvescriptslocal (Press space to go to the bottom).

[MadsBen]

I have PVE Scripts Local behind a reverse proxy, Nginx Proxy Manager, if that makes a difference.

journalctl -u pvescriptslocal:

Dec 01 11:15:29 lxcpvesl npm[4754]: 🔍 Auto-detect WebUI called with id: 11
Dec 01 11:15:29 lxcpvesl npm[4754]: 📋 Script data: { id: 11, execution_mode: 'ssh', server_id: 4, container_id: '213' }
Dec 01 11:15:29 lxcpvesl npm[4754]: 🖥️ Server found: { id: 4, name: 'REDACTED', ip: REDACTED' }
Dec 01 11:15:29 lxcpvesl npm[4754]: 🔌 Testing SSH connection...
Dec 01 11:15:29 lxcpvesl npm[4754]: ✅ SSH connection successful
Dec 01 11:15:29 lxcpvesl npm[4754]: 🚀 Running command: pct exec 213 -- hostname -I
Dec 01 11:15:30 lxcpvesl npm[4754]: 📤 Command output chunk: 192.168.20.13
Dec 01 11:15:30 lxcpvesl npm[4754]: 🏁 Command finished with exit code: 0
Dec 01 11:15:30 lxcpvesl npm[4754]: 📝 Full command output: 192.168.20.13
Dec 01 11:15:30 lxcpvesl npm[4754]: 🔍 Parsed IPs: [ '192.168.20.13' ]
Dec 01 11:15:30 lxcpvesl npm[4754]: 🎯 Detected IP: 192.168.20.13
Dec 01 11:15:30 lxcpvesl npm[4754]: 🔍 Looking for script with slug: lxcpeanut
Dec 01 11:15:30 lxcpvesl npm[4754]: 📋 No interface_port found in metadata, using default port 80
Dec 01 11:15:30 lxcpvesl npm[4754]: 🎯 Final detected port: 80
Dec 01 11:15:30 lxcpvesl npm[4754]: 💾 Updating database with IP: 192.168.20.13 Port: 80
Dec 01 11:15:30 lxcpvesl npm[4754]: ✅ Successfully updated database

[michelroegl-brunner]

Thank you for the logs, that helped me track the issue down. The "problem" is the hostname you gave the lxc. You named it lxcpeanut, so it is no longer called peanut. The Port detection logic looks at the Hostname, converts it to a slug an searches all JSON metadatafiles for that slug. now the slug no longer matches so it falls back to port 80 as default. I was no able to reacreate the Problem. I need to come up with a way on how we can reliably detect wich App is running on the lxc to get the slug to compare with the JSON. (Reminder for my self: Look at the update command, it has the script name in it and is availible on all LXC).

I will dig into that later this week, for now you can manually edit the Port with the edit button and enter the correct one to use the Open UI button correctly.

[white-rabbit07]

I can confirm this problem with v.0.5.2.
Since the upgrade I see this:

Before these buttons worked (-> WebUI)

When I try to edit the IP and the port these settings won't be saved: