#2289 - [GH-ISSUE #10588] phpIPAM: After installation - Unsupported PHP version detected: 8.4.16 >= 8.4 - starred/ProxmoxVE

kerem commented

2026-02-26 12:51:55 +03:00

Owner

Originally created by @dartus95 on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10588

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No (this issue will likely be closed automatically)

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

phpIPAM

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

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

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/8.4.16/368e3c45c15b895c (running kernel: 6.8.12-17-pve)

📝 Provide a clear and concise description of the issue.

After installation, when I want to access the application over IP in browser, I will get error regarding unsupported version of PHP installed as per screenshot bellow.

🔄 Steps to reproduce the issue.

Just use the script and then try to access the app via browser

❌ Paste the full error output (if available).

phpIPAM requirements error

Unsupported PHP version!

Detected PHP version: 8.4.16 >= 8.4

phpIPAM is not yet compatible with this version of php. You may encounter issues & errors.

Please set $allow_untested_php_versions=true; in config.php to continue at your own risk.

Lastest version can be downloaded from GitHub.

🖼️ Additional context (optional).

Screenshot of error:

Originally created by @dartus95 on GitHub (Jan 6, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10588 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? No (this issue will likely be closed automatically) ### 📜 What is the name of the script you are using? phpIPAM ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/phpipam.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/8.4.16/368e3c45c15b895c (running kernel: 6.8.12-17-pve) ### 📝 Provide a clear and concise description of the issue. After installation, when I want to access the application over IP in browser, I will get error regarding unsupported version of PHP installed as per screenshot bellow. ### 🔄 Steps to reproduce the issue. Just use the script and then try to access the app via browser ### ❌ Paste the full error output (if available). phpIPAM requirements error Unsupported PHP version! Detected PHP version: 8.4.16 >= 8.4 phpIPAM is not yet compatible with this version of php. You may encounter issues & errors. Please set $allow_untested_php_versions=true; in config.php to continue at your own risk. Lastest version can be downloaded from [GitHub](https://github.com/phpipam/phpipam/releases). ### 🖼️ Additional context (optional). Screenshot of error: <img width="1190" height="392" alt="Image" src="https://github.com/user-attachments/assets/897773f5-a0f6-4157-a00f-468e5fa84b34" />

kerem

2026-02-26 12:51:55 +03:00

closed this issue
added the
not a script issue

external
labels

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@MickLesk commented on GitHub (Jan 6, 2026):

Its Not the First time, you need to Report it at there repo, because they use static Version Numbers (really stupid)

@MickLesk commented on GitHub (Jan 6, 2026): Its Not the First time, you need to Report it at there repo, because they use static Version Numbers (really stupid)

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@dartus95 commented on GitHub (Jan 6, 2026):

I don't think that it is the repo problem. When I'm checking install script: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/phpipam-install.sh
there is following line: PHP_VERSION="8.4" PHP_APACHE="YES" PHP_FPM="YES" PHP_MODULE="mysql,gmp,snmp,ldap,apcu" setup_php

And when I raised the issue in phpIPAM repo I got following reply:

Hello,

The PHP requirements are listed in README.md. 1.7.4 has been tested with PHP8.3

MASTER: See latest 1.x.y release version
DEVELOP: PHP versions 7.2 to 8.4
1.7.x: PHP versions 7.2 to 8.3
1.6.x: PHP versions 7.2 to 8.3
1.5.x: PHP versions 5.4 to 7.4
1.4.x: PHP versions 5.4 to 7.4
1.3.x: PHP versions 5.4 to 7.1

@dartus95 commented on GitHub (Jan 6, 2026): I don't think that it is the repo problem. When I'm checking install script: _https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/phpipam-install.sh_ there is following line: PHP_VERSION="8.4" PHP_APACHE="YES" PHP_FPM="YES" PHP_MODULE="mysql,gmp,snmp,ldap,apcu" setup_php And when I raised the issue in phpIPAM repo I got following reply: > Hello, > > The PHP requirements are listed in README.md. 1.7.4 has been tested with PHP8.3 > > MASTER: See latest 1.x.y release version > DEVELOP: PHP versions 7.2 to 8.4 > 1.7.x: PHP versions 7.2 to 8.3 > 1.6.x: PHP versions 7.2 to 8.3 > 1.5.x: PHP versions 5.4 to 7.4 > 1.4.x: PHP versions 5.4 to 7.4 > 1.3.x: PHP versions 5.4 to 7.1

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@tremor021 commented on GitHub (Jan 6, 2026):

echo "\$allow_untested_php_versions=true;" >>/opt/phpipam/config.php

here, i fixed it for you.
Just wanna skip this "its a repo issue, i think its not a repo issue, i think its a repo issue" back and forth.

@tremor021 commented on GitHub (Jan 6, 2026): `echo "\$allow_untested_php_versions=true;" >>/opt/phpipam/config.php` here, i fixed it for you. Just wanna skip this "its a repo issue, i think its not a repo issue, i think its a repo issue" back and forth.

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@dartus95 commented on GitHub (Jan 8, 2026):

echo "\$allow_untested_php_versions=true;" >>/opt/phpipam/config.php

here, i fixed it for you. Just wanna skip this "its a repo issue, i think its not a repo issue, i think its a repo issue" back and forth.

Thank you, this helped.

@dartus95 commented on GitHub (Jan 8, 2026): > `echo "\$allow_untested_php_versions=true;" >>/opt/phpipam/config.php` > > here, i fixed it for you. Just wanna skip this "its a repo issue, i think its not a repo issue, i think its a repo issue" back and forth. Thank you, this helped.

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@gaston-senac commented on GitHub (Jan 19, 2026):

allow_untested

Thanks @tremor021 for your help. I'm kind of getting sick of MickLesk attitude towards reported bugs or issues. Make me want to stop using these scripts to be honest.

@gaston-senac commented on GitHub (Jan 19, 2026): > allow_untested Thanks @tremor021 for your help. I'm kind of getting sick of MickLesk attitude towards reported bugs or issues. Make me want to stop using these scripts to be honest.

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@MickLesk commented on GitHub (Jan 19, 2026):

lol

@MickLesk commented on GitHub (Jan 19, 2026): lol

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@tremor021 commented on GitHub (Jan 19, 2026):

allow_untested

Thanks @tremor021 for your help. I'm kind of getting sick of MickLesk attitude towards reported bugs or issues. Make me want to stop using these scripts to be honest.

The workaround i suggested is just a bandaid, as this app is very finicky and prone to breakage for some reason. I'm not really sure why the developer has put these hard restrictions to specific PHP versions, as if PHP is introducing breaking changes within minor versions or something... That's definitely not the case.

Anyway, phpIPAM is a discussion topic for some time in our discord, internally and publicly. We have decided to not support this app any more.

@tremor021 commented on GitHub (Jan 19, 2026): > > allow_untested > > Thanks [@tremor021](https://github.com/tremor021) for your help. I'm kind of getting sick of MickLesk attitude towards reported bugs or issues. Make me want to stop using these scripts to be honest. The workaround i suggested is just a bandaid, as this app is very finicky and prone to breakage for some reason. I'm not really sure why the developer has put these hard restrictions to specific PHP versions, as if PHP is introducing breaking changes within minor versions or something... That's definitely not the case. Anyway, phpIPAM is a discussion topic for some time in our discord, internally and publicly. We have decided to not support this app any more.

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@gaston-senac commented on GitHub (Jan 19, 2026):

lol

Well, you shouldn't be laughing when the PHPIMAP script cannot even set up the correct memory on the LXC container. But why should I bother to create a bug report when I have this attitude from you?
My LXC was crapping out because the LXC is set up to use 512MB, PHP is set up to use 512MB and mariadb is using another 150MB or so.

@gaston-senac commented on GitHub (Jan 19, 2026): > lol Well, you shouldn't be laughing when the PHPIMAP script cannot even set up the correct memory on the LXC container. But why should I bother to create a bug report when I have this attitude from you? My LXC was crapping out because the LXC is set up to use 512MB, PHP is set up to use 512MB and mariadb is using another 150MB or so.

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@MickLesk commented on GitHub (Jan 19, 2026):

What kind of genius are you? You've never created an issue before and now you're looking for confrontation instead of reading through the old issues? Do you think we have all 450 scripts running on the latest version all the time? By the way, it deploys great for me. tteck would probably have simply closed the issue again without any feedback, but we are the bad guys. If your hardware can't handle it, then an issue is created, which takes us 2 minutes to fix. OR you can just make a FORK and adjust it and make a PR, but you'd rather just whine and be offended. Plus, there's a reason why I say upstream issue. But no user ever considers creating an “issue” elsewhere. To be honest, we don't need users like you. Like a stubborn child saying, “Why should I create an issue when mimimi” – then go get yourself a lollipop, honestly. No one is stopping you from using the scripts. But one sensible issue would have been possible. So far, the script is being completely removed due to mixed content.

@MickLesk commented on GitHub (Jan 19, 2026): What kind of genius are you? You've never created an issue before and now you're looking for confrontation instead of reading through the old issues? Do you think we have all 450 scripts running on the latest version all the time? By the way, it deploys great for me. tteck would probably have simply closed the issue again without any feedback, but we are the bad guys. If your hardware can't handle it, then an issue is created, which takes us 2 minutes to fix. OR you can just make a FORK and adjust it and make a PR, but you'd rather just whine and be offended. Plus, there's a reason why I say upstream issue. But no user ever considers creating an “issue” elsewhere. To be honest, we don't need users like you. Like a stubborn child saying, “Why should I create an issue when mimimi” – then go get yourself a lollipop, honestly. No one is stopping you from using the scripts. But one sensible issue would have been possible. So far, the script is being completely removed due to mixed content.

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@tremor021 commented on GitHub (Jan 19, 2026):

lol

Well, you shouldn't be laughing when the PHPIMAP script cannot even set up the correct memory on the LXC container. But why should I bother to create a bug report when I have this attitude from you? My LXC was crapping out because the LXC is set up to use 512MB, PHP is set up to use 512MB and mariadb is using another 150MB or so.

I'm not really sure whats the issue with your LXC, but this app doesn't reach any of the limits we set initially:

Anyway, if the app starts requiring more resources than we initially set for the LXC, its really your problem, you're the administrator monitoring your own containers. I'm not really sure why users complain about "i need more disk space or more RAM". You're in control of your homelab. Also, not a single complaint was ever made about resource usage by this app since we started supporting it. It's only you at the moment.

Anyway, once developer irons out these PHP issues, we might consider supporting this app again.

@tremor021 commented on GitHub (Jan 19, 2026): > > lol > > Well, you shouldn't be laughing when the PHPIMAP script cannot even set up the correct memory on the LXC container. But why should I bother to create a bug report when I have this attitude from you? My LXC was crapping out because the LXC is set up to use 512MB, PHP is set up to use 512MB and mariadb is using another 150MB or so. I'm not really sure whats the issue with your LXC, but this app doesn't reach any of the limits we set initially: <img width="348" height="304" alt="Image" src="https://github.com/user-attachments/assets/a24d6336-e83a-4e62-b4ca-dd1a12b92322" /> Anyway, if the app starts requiring more resources than we initially set for the LXC, its really your problem, you're the administrator monitoring your own containers. I'm not really sure why users complain about "i need more disk space or more RAM". You're in control of your homelab. Also, not a single complaint was ever made about resource usage by this app since we started supporting it. It's only you at the moment. Anyway, once developer irons out these PHP issues, we might consider supporting this app again.

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@MickLesk commented on GitHub (Jan 19, 2026):

Script is removed for now, because mixed content issues (php8.3 but need 2 8.4 deps) - maybe if the dev branch is stable, we can take a look again.

https://github.com/community-scripts/ProxmoxVE/pull/10939#issue-3828613948

@MickLesk commented on GitHub (Jan 19, 2026): Script is removed for now, because mixed content issues (php8.3 but need 2 8.4 deps) - maybe if the dev branch is stable, we can take a look again. https://github.com/community-scripts/ProxmoxVE/pull/10939#issue-3828613948

kerem commented

2026-02-26 12:51:56 +03:00

Author

Owner

@CrazyWolf13 commented on GitHub (Jan 19, 2026):

relax a bit guys.

I agreed, sadly we had way too much issues with PHPipam recently, so I think it's a good decision to remvoe it.

Regarding comments from @gaston-senac, keep in mind while we try to make everything perfect, we spend a lot, really a lot of time on these scripts in our free time for no money, keeping track of all updates, especially the new vibe-coded section, that change the whole app in a bugfix version is exhausting, we always welcome PRs.

As far as I know the PHPipam script, by default it does not reach the limit after installation, but yeah if exposed to further load it will eat up more ram, so it's needed to increase the ram.

@CrazyWolf13 commented on GitHub (Jan 19, 2026): relax a bit guys. I agreed, sadly we had way too much issues with PHPipam recently, so I think it's a good decision to remvoe it. Regarding comments from @gaston-senac, keep in mind while we try to make everything perfect, we spend a lot, really a lot of time on these scripts in our free time for no money, keeping track of all updates, especially the new vibe-coded section, that change the whole app in a bugfix version is exhausting, we always welcome PRs. As far as I know the PHPipam script, by default it does not reach the limit after installation, but yeah if exposed to further load it will eat up more ram, so it's needed to increase the ram.

kerem referenced this issue

2026-02-26 13:34:17 +03:00

[PR #2289] [MERGED] Paperless-AI: add dependency "make" #3669

Rows
Columns

[GH-ISSUE #10588] phpIPAM: After installation - Unsupported PHP version detected: 8.4.16 >= 8.4 #2289

✅ Have you read and understood the above guidelines?

🔎 Did you run the script with verbose mode enabled?

📜 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).