IP-TAG No Ip Detected for LXC #1383

Closed
opened 2026-02-05 00:35:09 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @Veeau on GitHub (Aug 2, 2025).

Have you read and understood the above guidelines?

Yes

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

IP-TAG

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

iptag-run

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📝 Provide a clear and concise description of the issue.

Hello getting this on all my LXC 4 different host in 2 different datacenters. However they all have IP's and communicating to the network fine.

  • All on Vlans.

root@pveau01:~# iptag-run

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ IP-Tag service started successfully
ℹ Loop interval: 300 seconds
ℹ Debug mode: false
ℹ Tag format: full
ℹ Allowed CIDRs: 192.168.0.0/16 10.0.0.0/8 100.64.0.0/10
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

⚠ LXC status changes detected
⚠ VM status changes detected
⚠ Network interface changes detected
ℹ Scheduled LXC update (every 120 minutes)
ℹ Scheduled VM update (every 120 minutes)
ℹ Processing 5 LXC container(s) in parallel
= LXC 101: No IP detected, tags unchanged
= LXC 105: No IP detected, tags unchanged
= LXC 106: No IP detected, tags unchanged
= LXC 108: No IP detected, tags unchanged
= LXC 109: No IP detected, tags unchanged
✓ Completed processing LXC containers

🔄 Steps to reproduce the issue.

iptag-run

Paste the full error output (if available).

= LXC 101: No IP detected, tags unchanged
= LXC 105: No IP detected, tags unchanged
= LXC 106: No IP detected, tags unchanged
= LXC 108: No IP detected, tags unchanged
= LXC 109: No IP detected, tags unchanged

🖼️ Additional context (optional).

No response

Originally created by @Veeau on GitHub (Aug 2, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? IP-TAG ### 📂 What was the exact command used to execute the script? iptag-run ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 📝 Provide a clear and concise description of the issue. Hello getting this on all my LXC 4 different host in 2 different datacenters. However they all have IP's and communicating to the network fine. - All on Vlans. root@pveau01:~# iptag-run ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✓ IP-Tag service started successfully ℹ Loop interval: 300 seconds ℹ Debug mode: false ℹ Tag format: full ℹ Allowed CIDRs: 192.168.0.0/16 10.0.0.0/8 100.64.0.0/10 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ⚠ LXC status changes detected ⚠ VM status changes detected ⚠ Network interface changes detected ℹ Scheduled LXC update (every 120 minutes) ℹ Scheduled VM update (every 120 minutes) ℹ Processing 5 LXC container(s) in parallel = LXC 101: No IP detected, tags unchanged = LXC 105: No IP detected, tags unchanged = LXC 106: No IP detected, tags unchanged = LXC 108: No IP detected, tags unchanged = LXC 109: No IP detected, tags unchanged ✓ Completed processing LXC containers ### 🔄 Steps to reproduce the issue. iptag-run ### ❌ Paste the full error output (if available). = LXC 101: No IP detected, tags unchanged = LXC 105: No IP detected, tags unchanged = LXC 106: No IP detected, tags unchanged = LXC 108: No IP detected, tags unchanged = LXC 109: No IP detected, tags unchanged ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 00:35:09 +03:00
Author
Owner

@MickLesk commented on GitHub (Aug 2, 2025):

LXC_SKIP_SLOW_METHODS=false
LXC_ALLOW_FORCED_COMMANDS=true

change this and try again - next time read the Guide

@MickLesk commented on GitHub (Aug 2, 2025): LXC_SKIP_SLOW_METHODS=false LXC_ALLOW_FORCED_COMMANDS=true change this and try again - next time read the Guide
Author
Owner

@7200rpm commented on GitHub (Aug 11, 2025):

LXC_SKIP_SLOW_METHODS=false LXC_ALLOW_FORCED_COMMANDS=true

change this and try again - next time read the Guide

I don't see this info in the guide, or at least it's not clear. Can you update to clarify what is required to tag LXC ips? thanks!

@7200rpm commented on GitHub (Aug 11, 2025): > LXC_SKIP_SLOW_METHODS=false LXC_ALLOW_FORCED_COMMANDS=true > > change this and try again - next time read the Guide I don't see this info in the guide, or at least it's not clear. Can you update to clarify what is required to tag LXC ips? thanks!
Author
Owner

@Veeau commented on GitHub (Aug 12, 2025):

LXC_SKIP_SLOW_METHODS=false LXC_ALLOW_FORCED_COMMANDS=true
change this and try again - next time read the Guide

I don't see this info in the guide, or at least it's not clear. Can you update to clarify what is required to tag LXC ips? thanks!

Yeah one of these commands I couldn't even see in the guide and the other doesnt really explain anything.

@Veeau commented on GitHub (Aug 12, 2025): > > LXC_SKIP_SLOW_METHODS=false LXC_ALLOW_FORCED_COMMANDS=true > > change this and try again - next time read the Guide > > I don't see this info in the guide, or at least it's not clear. Can you update to clarify what is required to tag LXC ips? thanks! Yeah one of these commands I couldn't even see in the guide and the other doesnt really explain anything.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1383