[GH-ISSUE #8194] MyIP Script Install Error

kerem commented

2026-02-26 12:50:05 +03:00

Owner

Originally created by @jwtoler on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/8194

✅ Have you read and understood the above guidelines?

yes

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

MyIP

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/myip.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.0.10

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

Seems to hang on last step

❌ Paste the full error output (if available).

` ✔️ Started LXC Container
💡 No network in LXC yet (try 1/10) – waiting...
✔️ Network in LXC is reachable (ping)
⠋ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
⠙ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: 10.0.40.67
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
✔️ Updated Container OS
✔️ Setup Node.js 22
✔️ Deployed: myip (5.0.6)
⠙ Configuring MyIP
[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1
/dev/stdin: line 2500: post_update_to_api: command not found
/dev/stdin: line 23: pop_var_context: head of shell_variables not a function context
/dev/stdin: line 288: local: can only be used in a function

[ERROR] in line 1344: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(cat "$(dirname "$CORE_DIR")/install/${var_install}.sh")"

[9:42:09 PM] ✅ SSH script execution finished with code: 1`

🖼️ Additional context (optional).

Originally created by @jwtoler on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/8194 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? MyIP ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/myip.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.0.10 ### 📝 Provide a clear and concise description of the issue. <img width="2750" height="620" alt="Image" src="https://github.com/user-attachments/assets/41ab3e93-c791-440e-8882-c9584c0cb2da" /> ### 🔄 Steps to reproduce the issue. Seems to hang on last step ### ❌ Paste the full error output (if available). ` ✔️ Started LXC Container 💡 No network in LXC yet (try 1/10) – waiting... ✔️ Network in LXC is reachable (ping) ⠋ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory ⠙ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 10.0.40.67 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Setup Node.js 22 ✔️ Deployed: myip (5.0.6) ⠙ Configuring MyIP [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 /dev/stdin: line 2500: post_update_to_api: command not found /dev/stdin: line 23: pop_var_context: head of shell_variables not a function context /dev/stdin: line 288: local: can only be used in a function [ERROR] in line 1344: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(cat "$(dirname "$CORE_DIR")/install/${var_install}.sh")" [9:42:09 PM] ✅ SSH script execution finished with code: 1` ### 🖼️ Additional context (optional). <img width="2750" height="620" alt="Image" src="https://github.com/user-attachments/assets/e5b7ad07-72f7-4c5c-aa37-fd6df5b26124" />

kerem

2026-02-26 12:50:05 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@olliemaller commented on GitHub (Oct 8, 2025):

Was just about to post this but you beat me to it! But hey I'm not complaining! Thanks for this. Looks like a really cool and advanced software! I can confirm I am also experiencing this issue with both the GitHub and gitea

@olliemaller commented on GitHub (Oct 8, 2025): Was just about to post this but you beat me to it! But hey I'm not complaining! Thanks for this. Looks like a really cool and advanced software! I can confirm I am also experiencing this issue with both the GitHub and gitea

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@tremor021 commented on GitHub (Oct 8, 2025):

Works fine here

@tremor021 commented on GitHub (Oct 8, 2025): <img width="699" height="568" alt="Image" src="https://github.com/user-attachments/assets/f8e25135-b55f-4129-a287-f2b8b79e8ef2" /> Works fine here

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

Well the only thing I've changed is used the advanced option and set a VLAN of 40. Everything else default

@jwtoler commented on GitHub (Oct 8, 2025): Well the only thing I've changed is used the advanced option and set a VLAN of 40. Everything else default

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@MickLesk commented on GitHub (Oct 8, 2025):

This is local over the new Tool or with ssh / Proxmox webui?

@MickLesk commented on GitHub (Oct 8, 2025): This is local over the new Tool or with ssh / Proxmox webui?

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

This is local over the new Tool or with ssh / Proxmox webui?

I first tried Proxmox Shell then discovered the new PVE Scripts Local and install then tried there. Both fail. This is what happens on the Proxmox Shell. It just hang on the "Configuring MyIP"

@jwtoler commented on GitHub (Oct 8, 2025): > This is local over the new Tool or with ssh / Proxmox webui? I first tried Proxmox Shell then discovered the new PVE Scripts Local and install then tried there. Both fail. This is what happens on the Proxmox Shell. It just hang on the "Configuring MyIP" <img width="2774" height="1742" alt="Image" src="https://github.com/user-attachments/assets/2835f455-0d34-4e4e-81d1-f54d154df320" />

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

This is local over the new Tool or with ssh / Proxmox webui?

I first tried Proxmox Shell then discovered the new PVE Scripts Local and install then tried there. Both fail. This is what happens on the Proxmox Shell. It just hang on the "Configuring MyIP"

Side question:
how can I fix that LC_ALL error on every install. @tremor021 did not seem to get that message. end up doing dpkg-reconfigure locales

@jwtoler commented on GitHub (Oct 8, 2025): > > This is local over the new Tool or with ssh / Proxmox webui? > > I first tried Proxmox Shell then discovered the new PVE Scripts Local and install then tried there. Both fail. This is what happens on the Proxmox Shell. It just hang on the "Configuring MyIP" > > <img alt="Image" width="2000" height="1742" src="https://private-user-images.githubusercontent.com/17133784/498716448-2835f455-0d34-4e4e-81d1-f54d154df320.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTk5MDY2OTcsIm5iZiI6MTc1OTkwNjM5NywicGF0aCI6Ii8xNzEzMzc4NC80OTg3MTY0NDgtMjgzNWY0NTUtMGQzNC00ZTRlLTgxZDEtZjU0ZDE1NGRmMzIwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEwMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMDA4VDA2NTMxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg3ZmJlN2I5ZjIxYWUwODJlYzQyNGZhZWNmZDJkZDQxMzQ5ZmJlNjAwNGRhNzg3N2U5NWQ5MGE3Njg5M2Y4NjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ARj5f5NPdQiI4HcLU_YUD0uponQXAtDwrbvYruP1BBA"> Side question: how can I fix that LC_ALL error on every install. @tremor021 did not seem to get that message. end up doing `dpkg-reconfigure locales`

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@tremor021 commented on GitHub (Oct 8, 2025):

Its not stuck, just let it finish. Its installing NodeJS packages at that stage and building the app

@tremor021 commented on GitHub (Oct 8, 2025): Its not stuck, just let it finish. Its installing NodeJS packages at that stage and building the app

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

Its not stuck, just let it finish. Its installing NodeJS packages at that stage and building the app

Well this is like my 4th time trying via the shell and just waiting. But I'll update in 15 mins or so w/ status

@jwtoler commented on GitHub (Oct 8, 2025): > Its not stuck, just let it finish. Its installing NodeJS packages at that stage and building the app Well this is like my 4th time trying via the shell and just waiting. But I'll update in 15 mins or so w/ status

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@MickLesk commented on GitHub (Oct 8, 2025):

Or just Run in verbose - so you see the Progress

@MickLesk commented on GitHub (Oct 8, 2025): Or just Run in verbose - so you see the Progress

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

Or just Run in verbose - so you see the Progress

Yeah, just thought of that. :)

Was still stuck on that step so trying verbose now

@jwtoler commented on GitHub (Oct 8, 2025): > Or just Run in verbose - so you see the Progress Yeah, just thought of that. :) Was still stuck on that step so trying verbose now

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

🧩 Using Advanced Settings on node pve
🖥️ Operating System: debian
🌟 Version: 13
📦 Container Type: Unprivileged
🔐 Root Password: Automatic Login
🆔 Container ID: 126
🏠 Hostname: myip
💾 Disk Size: 4 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 512 MiB
🌉 Bridge: vmbr0
📡 IPv4: DHCP
📡 IPv6: SLAAC/AUTO
📡 APT-Cacher IP Address: Default
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: 40
📡 Tags: community-script;network
🔑 Root SSH Access: no
🗂️ Enable FUSE Support: no
🔍 Verbose Mode: yes
🚀 Creating a MyIP LXC using the above advanced settings
✔️ Storage local (Free: 47.1GB Used: 22.6GB) [Template]
✔️ Storage local-zfs (Free: 47.1GB Used: 118.7GB) [Container]
✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local]
✔️ LXC Container 126 was successfully created.
✔️ Started LXC Container
✔️ Network in LXC is reachable (ping)
⏳ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: 10.0.40.108
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
Hit:1 http://security.debian.org trixie-security InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
✔️ Updated Container OS
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'nodejs' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

removed 26 packages, and changed 78 packages in 6s

28 packages are looking for funding
run npm fund for details
✔️ Setup Node.js 22
✔️ Deployed: myip (5.0.6)
npm warn deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated source-map@0.8.0-beta.0: The work that was done in this beta branch won't be included in future versions

added 663 packages, and audited 664 packages in 1m

130 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

myip@5.0.0 build
vite build

[dotenv@17.2.3] injecting env (19) from .env -- tip: 👥 sync secrets across teammates & machines: https://dotenvx.com/ops
vite v7.1.9 building for production...
✓ 488 modules transformed.
rendering chunks (8)...

Seems to hang here. Using the new PVE Script Local tool was first time I got actual error trying to install (what I first posted).

@jwtoler commented on GitHub (Oct 8, 2025): > 🧩 Using Advanced Settings on node pve > 🖥️ Operating System: debian > 🌟 Version: 13 > 📦 Container Type: Unprivileged > 🔐 Root Password: Automatic Login > 🆔 Container ID: 126 > 🏠 Hostname: myip > 💾 Disk Size: 4 GB > 🧠 CPU Cores: 1 > 🛠️ RAM Size: 512 MiB > 🌉 Bridge: vmbr0 > 📡 IPv4: DHCP > 📡 IPv6: SLAAC/AUTO > 📡 APT-Cacher IP Address: Default > ⚙️ Interface MTU Size: Default > 🔍 DNS Search Domain: Host > 📡 DNS Server IP Address: Host > 🏷️ Vlan: 40 > 📡 Tags: community-script;network > 🔑 Root SSH Access: no > 🗂️ Enable FUSE Support: no > 🔍 Verbose Mode: yes > 🚀 Creating a MyIP LXC using the above advanced settings > ✔️ Storage local (Free: 47.1GB Used: 22.6GB) [Template] > ✔️ Storage local-zfs (Free: 47.1GB Used: 118.7GB) [Container] > ✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local] > ✔️ LXC Container 126 was successfully created. > ✔️ Started LXC Container > ✔️ Network in LXC is reachable (ping) > ⏳ Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory > bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory > ✔️ Customized LXC Container > ✔️ Set up Container OS > ✔️ Network Connected: 10.0.40.108 > ✔️ IPv4 Internet Connected > ✖️ IPv6 Internet Not Connected > ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) > Hit:1 http://security.debian.org trixie-security InRelease > Hit:2 http://deb.debian.org/debian trixie InRelease > Hit:3 http://deb.debian.org/debian trixie-updates InRelease > Reading package lists... Done > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > ✔️ Updated Container OS > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Package 'nodejs' is not installed, so not removed > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > removed 26 packages, and changed 78 packages in 6s > > 28 packages are looking for funding > run `npm fund` for details > ✔️ Setup Node.js 22 > ✔️ Deployed: myip (5.0.6) > npm warn deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead > npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. > npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported > npm warn deprecated source-map@0.8.0-beta.0: The work that was done in this beta branch won't be included in future versions > > added 663 packages, and audited 664 packages in 1m > > 130 packages are looking for funding > run `npm fund` for details > > found 0 vulnerabilities > > > myip@5.0.0 build > > vite build > > [dotenv@17.2.3] injecting env (19) from .env -- tip: 👥 sync secrets across teammates & machines: https://dotenvx.com/ops > vite v7.1.9 building for production... > ✓ 488 modules transformed. > rendering chunks (8)... Seems to hang here. Using the new PVE Script Local tool was first time I got actual error trying to install (what I first posted).

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@tremor021 commented on GitHub (Oct 8, 2025):

Its still in the building stage, its not stuck. What specs is your host?

@tremor021 commented on GitHub (Oct 8, 2025): Its still in the building stage, its not stuck. What specs is your host?

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

Its still in the building stage, its not stuck. What specs is your host?

Should be plenty. RAM usually isn't that high - I don't think. CPU is still low though. Maybe I'll reboot and retry.

@jwtoler commented on GitHub (Oct 8, 2025): > Its still in the building stage, its not stuck. What specs is your host? Should be plenty. RAM usually isn't that high - I don't think. CPU is still low though. Maybe I'll reboot and retry. <img width="2528" height="682" alt="Image" src="https://github.com/user-attachments/assets/4fbddef9-d1b2-459c-99fc-f572008a2176" />

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@tremor021 commented on GitHub (Oct 8, 2025):

It takes 4m30s to install this LXC on my crappy Xeon from 2013

@tremor021 commented on GitHub (Oct 8, 2025): It takes 4m30s to install this LXC on my crappy Xeon from 2013 <img width="357" height="325" alt="Image" src="https://github.com/user-attachments/assets/646f9e5c-343f-4c43-9431-ed8c2d924fb1" />

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

It takes 4m30s to install this LXC on my crappy Xeon from 2013

I think a simple restart just fixed it....

@jwtoler commented on GitHub (Oct 8, 2025): > It takes 4m30s to install this LXC on my crappy Xeon from 2013 > > <img alt="Image" width="357" height="325" src="https://private-user-images.githubusercontent.com/58952836/498733583-646f9e5c-343f-4c43-9431-ed8c2d924fb1.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTk5MTAyNTcsIm5iZiI6MTc1OTkwOTk1NywicGF0aCI6Ii81ODk1MjgzNi80OTg3MzM1ODMtNjQ2ZjllNWMtMzQzZi00YzQzLTk0MzEtZWQ4YzJkOTI0ZmIxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEwMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMDA4VDA3NTIzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBhMzJhMjIxZWJkNjZlNTE1ZDU3MThlMDhlMTM0MzJiMTJmYTM2ZGEwZGJhNWQ2ZTNjNTlkOWRjN2UxOTgxZjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.kQ1W_s3EhnxYMd6NPsGh1YCFxJn6o8tIRQxQPQSRpA4"> I think a simple restart just fixed it....

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

It takes 4m30s to install this LXC on my crappy Xeon from 2013

I think a simple restart just fixed it....

Yes, it did! It's amazing how easy it is to forget simple restarting, sometimes fixes everything!! But first thing we telll other people!

Any idea about LC_All though? happens every where

@jwtoler commented on GitHub (Oct 8, 2025): > > It takes 4m30s to install this LXC on my crappy Xeon from 2013 > > <img alt="Image" width="357" height="325" src="https://private-user-images.githubusercontent.com/58952836/498733583-646f9e5c-343f-4c43-9431-ed8c2d924fb1.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTk5MTAyNTcsIm5iZiI6MTc1OTkwOTk1NywicGF0aCI6Ii81ODk1MjgzNi80OTg3MzM1ODMtNjQ2ZjllNWMtMzQzZi00YzQzLTk0MzEtZWQ4YzJkOTI0ZmIxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEwMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMDA4VDA3NTIzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBhMzJhMjIxZWJkNjZlNTE1ZDU3MThlMDhlMTM0MzJiMTJmYTM2ZGEwZGJhNWQ2ZTNjNTlkOWRjN2UxOTgxZjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.kQ1W_s3EhnxYMd6NPsGh1YCFxJn6o8tIRQxQPQSRpA4"> > > I think a simple restart just fixed it.... Yes, it did! It's amazing how easy it is to forget simple restarting, sometimes fixes everything!! But first thing we telll other people! Any idea about LC_All though? happens every where

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@michelroegl-brunner commented on GitHub (Oct 8, 2025):

Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

That seams to be some sort of missconfiguration on your Host regarding the Localisation settings. This is not a script issie per se.

@michelroegl-brunner commented on GitHub (Oct 8, 2025): `Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)` That seams to be some sort of missconfiguration on your Host regarding the Localisation settings. This is not a script issie per se.

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

That seams to be some sort of missconfiguration on your Host regarding the Localisation settings. This is not a script issie per se.

Yes I def know it is not a script related issue because I have been dealing without for a while. Always just end up recnfiguring locales when need or after install script manually. But what I don't understand... this is my host:

root@pve:# locale-gen
Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
root@pve:# echo "export LC_ALL=en_US.UTF-8" >> /.bashrc
root@pve:# echo "export LANG=en_US.UTF-8" >> /.bashrc
root@pve:# echo "export LANGUAGE=en_US.UTF-8" >> /.bashrc
root@pve:#
root@pve:~# source /.bashrc
root@pve:# locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

Made sure LC_ALL, etc was set. Still get error.

**Also I realize this should probably be posted on Proxmox forum and apologies for asking this on here

@jwtoler commented on GitHub (Oct 8, 2025): > `Customizing LXC Containerbash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)` > > That seams to be some sort of missconfiguration on your Host regarding the Localisation settings. This is not a script issie per se. Yes I def know it is not a script related issue because I have been dealing without for a while. Always just end up recnfiguring locales when need or after install script manually. But what I don't understand... this is my host: > root@pve:~# locale-gen Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. root@pve:~# echo "export LC_ALL=en_US.UTF-8" >> ~/.bashrc root@pve:~# echo "export LANG=en_US.UTF-8" >> ~/.bashrc root@pve:~# echo "export LANGUAGE=en_US.UTF-8" >> ~/.bashrc root@pve:~# root@pve:~# source ~/.bashrc root@pve:~# locale LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8 Made sure LC_ALL, etc was set. Still get error. **Also I realize this should probably be posted on Proxmox forum and apologies for asking this on here

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@olliemaller commented on GitHub (Oct 8, 2025):

The issue why it was taking so long for me was because for some reason the default settings only give it 1 core and 512mb of ram and that is what was casuing it to stall. I uppeed it to 5 cores and added 32gb to the lxc and boom instantly it works. I was like no ways its a resource issue becuase i have 40 cores and 400gb of ram and low and behold i go to my monitoring software and its at 99.9 percent usage for that one core and 512mb of ram

@olliemaller commented on GitHub (Oct 8, 2025): The issue why it was taking so long for me was because for some reason the default settings only give it 1 core and 512mb of ram and that is what was casuing it to stall. I uppeed it to 5 cores and added 32gb to the lxc and boom instantly it works. I was like no ways its a resource issue becuase i have 40 cores and 400gb of ram and low and behold i go to my monitoring software and its at 99.9 percent usage for that one core and 512mb of ram

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@tremor021 commented on GitHub (Oct 8, 2025):

Yea, it has 1c/512mb of RAM because the app itself uses very little resources, so it makes no sense to give it 10 cores and 32GB of RAM just to install. Its a tradeoff i decided to put in. I can increase it to 2c/2GB RAM, it would speed up the process

@tremor021 commented on GitHub (Oct 8, 2025): Yea, it has 1c/512mb of RAM because the app itself uses very little resources, so it makes no sense to give it 10 cores and 32GB of RAM just to install. Its a tradeoff i decided to put in. I can increase it to 2c/2GB RAM, it would speed up the process

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

Before I close this, I will just add that it does feel likes something eats up the RAM sometimes during install and doesn't properly exit and free up that RAM. It was not till I fully rebooted my host and my total RAM usage drastically decreased (with all LXC and VM's booted). Thinking it fully closed out process that was "stuck".

Me personally....whatever reason I think I could have lost connection to host potentially during first install and failed. Every proceeding install I tried failed bc of that process not properly exited and I was unaware. Restart properly closed it. Worked after.

@jwtoler commented on GitHub (Oct 8, 2025): Before I close this, I will just add that it does feel likes something eats up the RAM sometimes during install and doesn't properly exit and free up that RAM. It was not till I fully rebooted my host and my total RAM usage drastically decreased (with all LXC and VM's booted). Thinking it fully closed out process that was "stuck". Me personally....whatever reason I think I could have lost connection to host potentially during first install and failed. Every proceeding install I tried failed bc of that process not properly exited and I was unaware. Restart properly closed it. Worked after.

kerem commented

2026-02-26 12:50:06 +03:00

Author

Owner

@jwtoler commented on GitHub (Oct 8, 2025):

Yea, it has 1c/512mb of RAM because the app itself uses very little resources, so it makes no sense to give it 10 cores and 32GB of RAM just to install. Its a tradeoff i decided to put in. I can increase it to 2c/2GB RAM, it would speed up the process

I didn't have to increase the RAM from default setting after I rebooted and everything was fresh.

@jwtoler commented on GitHub (Oct 8, 2025): > Yea, it has 1c/512mb of RAM because the app itself uses very little resources, so it makes no sense to give it 10 cores and 32GB of RAM just to install. Its a tradeoff i decided to put in. I can increase it to 2c/2GB RAM, it would speed up the process I didn't have to increase the RAM from default setting after I rebooted and everything was fresh.

kerem referenced this issue

2026-02-26 13:33:11 +03:00

[PR #1749] [MERGED] Revert "[Github Action] Update CHANGELOG.md" #3332

Rows
Columns

[GH-ISSUE #8194] MyIP Script Install Error #1749

✅ Have you read and understood the above guidelines?

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

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

⚙️ What settings are you using?

🖥️ Which Linux distribution are you using?

📈 Which Proxmox version are you on?

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).