Proxmox VE LXC IP-Tag breaks what worked before #1107

Closed
opened 2026-02-04 23:07:28 +03:00 by OVERLORD · 7 comments
Owner

Originally created by @anyblabla on GitHub (Jun 16, 2025).

Have you read and understood the above guidelines?

Yes

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

Proxmox VE LXC IP-Tag

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/add-iptag.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

I used this script on all my Proxmox VE hosts when it was released: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/add-lxc-iptag.sh)"

Everything always worked fine.

I saw that a new script had just been released, allowing you to update a previous installation.
This new script correctly detects the previous installation.
It correctly asks if you want to proceed with the update.
The script ends with a message saying it's ok.
But since then, when creating an LXC, or when changing the IP address of an existing LXC, the automatic addition or modification of the IP tag no longer occurs.
In /opt/iptag, there is an iptag file.
This file does indeed contain the configuration mentioned in the script. But on the site, you're talking about an iptag.conf configuration file!
The iptag.service file in /lib/systemd/system/ contains the line ExecStart=/opt/iptag/iptag.

I did, of course, restart the service (systemctl restart iptag.service), but nothing worked.
I didn't restart the PVE hosts because I can't right now.

PS: The source code link (https://community-scripts.github.io/ProxmoxVE/scripts?id=add-iptag) returns a "404: Not Found".

THANK YOU.

🔄 Steps to reproduce the issue.

Open the Proxmox VE shell, paste and run the script: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/add-iptag.sh)"

Paste the full error output (if available).

No error message!

Image

🖼️ Additional context (optional).

No response

Originally created by @anyblabla on GitHub (Jun 16, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Proxmox VE LXC IP-Tag ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/add-iptag.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. I used this script on all my Proxmox VE hosts when it was released: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/add-lxc-iptag.sh)" Everything always worked fine. I saw that a new script had just been released, allowing you to update a previous installation. This new script correctly detects the previous installation. It correctly asks if you want to proceed with the update. The script ends with a message saying it's ok. But since then, when creating an LXC, or when changing the IP address of an existing LXC, the automatic addition or modification of the IP tag no longer occurs. In /opt/iptag, there is an iptag file. This file does indeed contain the configuration mentioned in the script. But on the site, you're talking about an iptag.conf configuration file! The iptag.service file in /lib/systemd/system/ contains the line ExecStart=/opt/iptag/iptag. I did, of course, restart the service (systemctl restart iptag.service), but nothing worked. I didn't restart the PVE hosts because I can't right now. PS: The source code link (https://community-scripts.github.io/ProxmoxVE/scripts?id=add-iptag) returns a "404: Not Found". THANK YOU. ### 🔄 Steps to reproduce the issue. Open the Proxmox VE shell, paste and run the script: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/add-iptag.sh)" ### ❌ Paste the full error output (if available). No error message! ![Image](https://github.com/user-attachments/assets/79d792d8-c336-4a41-aa62-1991cc8440d6) ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 23:07:28 +03:00
Author
Owner

@anyblabla commented on GitHub (Jun 16, 2025):

I rebooted a Proxmox VE host, but nothing changed. The problem persists. I'm sending you some logs from the Proxmox VE host.
We can see that IP-TAG correctly finds the number of LXCs and VMs, and that it forces the IP addresses to be updated, but nothing works.

Jun 16 17:23:37 pvenocl5 iptag[1063]: Force updating lxc tags...
Jun 16 17:23:38 pvenocl5 iptag[1063]: Found 14 running lxcs
Jun 16 17:23:41 pvenocl5 iptag[1063]: Force updating vm tags...
Jun 16 17:23:42 pvenocl5 iptag[1063]: Found 16 running vms
Jun 16 17:24:58 pvenocl5 iptag[1063]: Force updating lxc tags...
Jun 16 17:25:00 pvenocl5 iptag[1063]: Found 14 running lxcs
Jun 16 17:25:03 pvenocl5 iptag[1063]: Force updating vm tags...
Jun 16 17:25:04 pvenocl5 iptag[1063]: Found 16 running vms
Jun 16 17:26:20 pvenocl5 iptag[1063]: Force updating lxc tags...
Jun 16 17:26:21 pvenocl5 iptag[1063]: Found 14 running lxcs
Jun 16 17:26:25 pvenocl5 iptag[1063]: Force updating vm tags...
Jun 16 17:26:26 pvenocl5 iptag[1063]: Found 16 running vms
Jun 16 17:27:42 pvenocl5 iptag[1063]: Force updating lxc tags...
Jun 16 17:27:43 pvenocl5 iptag[1063]: Found 14 running lxcs
Jun 16 17:27:46 pvenocl5 iptag[1063]: Force updating vm tags...
Jun 16 17:27:47 pvenocl5 iptag[1063]: Found 16 running vms
Jun 16 17:29:04 pvenocl5 iptag[1063]: Force updating lxc tags...
Jun 16 17:29:05 pvenocl5 iptag[1063]: Found 14 running lxcs
Jun 16 17:29:08 pvenocl5 iptag[1063]: Force updating vm tags...
Jun 16 17:29:09 pvenocl5 iptag[1063]: Found 16 running vms
Jun 16 17:30:26 pvenocl5 iptag[1063]: Force updating lxc tags...
Jun 16 17:30:27 pvenocl5 iptag[1063]: Found 14 running lxcs
Jun 16 17:30:30 pvenocl5 iptag[1063]: Force updating vm tags...
Jun 16 17:30:31 pvenocl5 iptag[1063]: Found 16 running vms

@anyblabla commented on GitHub (Jun 16, 2025): I rebooted a Proxmox VE host, but nothing changed. The problem persists. I'm sending you some logs from the Proxmox VE host. We can see that IP-TAG correctly finds the number of LXCs and VMs, and that it forces the IP addresses to be updated, but nothing works. Jun 16 17:23:37 pvenocl5 iptag[1063]: Force updating lxc tags... Jun 16 17:23:38 pvenocl5 iptag[1063]: Found 14 running lxcs Jun 16 17:23:41 pvenocl5 iptag[1063]: Force updating vm tags... Jun 16 17:23:42 pvenocl5 iptag[1063]: Found 16 running vms Jun 16 17:24:58 pvenocl5 iptag[1063]: Force updating lxc tags... Jun 16 17:25:00 pvenocl5 iptag[1063]: Found 14 running lxcs Jun 16 17:25:03 pvenocl5 iptag[1063]: Force updating vm tags... Jun 16 17:25:04 pvenocl5 iptag[1063]: Found 16 running vms Jun 16 17:26:20 pvenocl5 iptag[1063]: Force updating lxc tags... Jun 16 17:26:21 pvenocl5 iptag[1063]: Found 14 running lxcs Jun 16 17:26:25 pvenocl5 iptag[1063]: Force updating vm tags... Jun 16 17:26:26 pvenocl5 iptag[1063]: Found 16 running vms Jun 16 17:27:42 pvenocl5 iptag[1063]: Force updating lxc tags... Jun 16 17:27:43 pvenocl5 iptag[1063]: Found 14 running lxcs Jun 16 17:27:46 pvenocl5 iptag[1063]: Force updating vm tags... Jun 16 17:27:47 pvenocl5 iptag[1063]: Found 16 running vms Jun 16 17:29:04 pvenocl5 iptag[1063]: Force updating lxc tags... Jun 16 17:29:05 pvenocl5 iptag[1063]: Found 14 running lxcs Jun 16 17:29:08 pvenocl5 iptag[1063]: Force updating vm tags... Jun 16 17:29:09 pvenocl5 iptag[1063]: Found 16 running vms Jun 16 17:30:26 pvenocl5 iptag[1063]: Force updating lxc tags... Jun 16 17:30:27 pvenocl5 iptag[1063]: Found 14 running lxcs Jun 16 17:30:30 pvenocl5 iptag[1063]: Force updating vm tags... Jun 16 17:30:31 pvenocl5 iptag[1063]: Found 16 running vms
Author
Owner

@MickLesk commented on GitHub (Jun 16, 2025):

@DesertGamer Idea? My Install works

@MickLesk commented on GitHub (Jun 16, 2025): @DesertGamer Idea? My Install works
Author
Owner

@DesertGamer commented on GitHub (Jun 16, 2025):

@MickLesk, @anyblabla There's still an incorrect link to the script on the website. As for the fact that tags are not given, it happens when the config is not updated.

Use the command:
cat /opt/iptag/iptag.conf
and:
ls /opt/iptag

Image
@DesertGamer commented on GitHub (Jun 16, 2025): @MickLesk, @anyblabla There's still an incorrect link to the script on the website. As for the fact that tags are not given, it happens when the config is not updated. Use the command: `cat /opt/iptag/iptag.conf` and: `ls /opt/iptag` <img width="624" alt="Image" src="https://github.com/user-attachments/assets/ca5e1629-e0a3-486a-92b3-9530ecdb0d7f" />
Author
Owner

@DesertGamer commented on GitHub (Jun 16, 2025):

Also, if your internal IP differs from the specified mask in the config, then you also need to change it in the config.

CIDR_LIST is responsible for this function.

@DesertGamer commented on GitHub (Jun 16, 2025): Also, if your internal IP differs from the specified mask in the config, then you also need to change it in the config. CIDR_LIST is responsible for this function.
Author
Owner

@MickLesk commented on GitHub (Jun 16, 2025):

Whats wrong on json?

https://community-scripts.github.io/ProxmoxVE/scripts?id=add-iptag

Its the same Like your Code before, or iam a little bit blind? 😅

Ah you mean the source, okay, thats fixed now

@MickLesk commented on GitHub (Jun 16, 2025): Whats wrong on json? https://community-scripts.github.io/ProxmoxVE/scripts?id=add-iptag Its the same Like your Code before, or iam a little bit blind? 😅 Ah you mean the source, okay, thats fixed now
Author
Owner

@anyblabla commented on GitHub (Jun 17, 2025):

Re.
Exactly, I don't have an iptag.conf file!
I only have one iptag file.
That's what I was saying in my first message.
And when I used the old script, I never had to create a configuration file manually.
So, I understand now.
Okay, I created iptag.conf with what works for me.
Thanks for wasting your time :)
Sorry for my bad English :)

Image

Image

Image

@anyblabla commented on GitHub (Jun 17, 2025): Re. Exactly, I don't have an iptag.conf file! I only have one iptag file. That's what I was saying in my first message. And when I used the old script, I never had to create a configuration file manually. So, I understand now. Okay, I created iptag.conf with what works for me. Thanks for wasting your time :) Sorry for my bad English :) ![Image](https://github.com/user-attachments/assets/fc482124-3fd3-4b85-976b-89d02bee0c9c) ![Image](https://github.com/user-attachments/assets/dad2ddcc-bea8-480d-98b1-73616c8e405e) ![Image](https://github.com/user-attachments/assets/fb3dd0dc-fdba-46db-b841-05c25953d661)
Author
Owner

@anyblabla commented on GitHub (Jun 17, 2025):

On the other hand, I just used the script to install iptag, so no upgrade since it's not installed yet, and everything works fine. The iptag.conf file is created correctly.

@anyblabla commented on GitHub (Jun 17, 2025): On the other hand, I just used the script to install iptag, so no upgrade since it's not installed yet, and everything works fine. The iptag.conf file is created correctly.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1107