Unable to install Snipe-it #616

Closed
opened 2026-02-04 20:20:15 +03:00 by OVERLORD · 27 comments
Owner

Originally created by @creative0100 on GitHub (Mar 10, 2025).

Have you read and understood the above guidelines?

yes

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

Snipe-It

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/snipeit.sh)"

📝 Provide a clear and concise description of the issue.

As per requested there is an issue with the script for snipe-it. Creates the container fine but when it comes to install it either errors out as below using the default settings:

⚙️ Using Default Settings on node Office
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
💾 Disk Size: 4 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🆔 Container ID: 101
🚀 Creating a SnipeIT LXC using the above default settings

✔️ Using local for Template Storage.
✔️ Using VM1 for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 101 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.224
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 4.237.22.38
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Set up database
⠸ Installing Snipe-IT
[ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')

or it times out when using the advanced method with the current github error:

✔️ Installed Dependencies
✔️ Set up database
⠏Loading composer repositories with package information
⠇GitHub API limit (60 calls/hr) is exhausted, could not fetch a4731a834f. Create a GitHub OAuth token to go over the API rate limit. You can also wait until 2025-03-09 23:17:36 for the rate limit to reset.

When working with public GitHub repositories only, head to https://github.com/settings/tokens/new?scopes=&description=Composer+on+snipeit-production+2025-03-09+2217 to retrieve a token.
This token will have read-only permission for public information only.
When you need to access private GitHub repositories as well, go to https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+snipeit-production+2025-03-09+2217
Note that such tokens have broad read/write permissions on your behalf, even if not needed by Composer.
Tokens will be stored in plain text in "/root/.config/composer/auth.json" for future use by Composer.
For additional information, check https://getcomposer.org/doc/articles/authentication-for-private-packages.md#github-oauth
⠇ken (hidden):

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

just following the script. Nothing different from the prompts within the installer.

Paste the full error output (if available).

not available

🖼️ Additional context (optional).

Tested this on 3 different machines in 2 different locations with the same results using both the advanced and default settings.

Originally created by @creative0100 on GitHub (Mar 10, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Snipe-It ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/snipeit.sh)" ### 📝 Provide a clear and concise description of the issue. As per requested there is an issue with the script for snipe-it. Creates the container fine but when it comes to install it either errors out as below using the default settings: ⚙️ Using Default Settings on node Office 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🆔 Container ID: 101 🚀 Creating a SnipeIT LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using VM1 for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.224 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 4.237.22.38 ✔️ Updated Container OS ✔️ Installed Dependencies ✔️ Set up database ⠸ Installing Snipe-IT [ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }') or it times out when using the advanced method with the current github error: ✔️ Installed Dependencies ✔️ Set up database ⠏Loading composer repositories with package information ⠇GitHub API limit (60 calls/hr) is exhausted, could not fetch https://api.github.com/repos/grokability/html/commits/a4731a834fd2f98ebdb4e8c11b08181e5ee3c652. Create a GitHub OAuth token to go over the API rate limit. You can also wait until 2025-03-09 23:17:36 for the rate limit to reset. When working with _public_ GitHub repositories only, head to https://github.com/settings/tokens/new?scopes=&description=Composer+on+snipeit-production+2025-03-09+2217 to retrieve a token. This token will have read-only permission for public information only. When you need to access _private_ GitHub repositories as well, go to https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+snipeit-production+2025-03-09+2217 Note that such tokens have broad read/write permissions on your behalf, even if not needed by Composer. Tokens will be stored in plain text in "/root/.config/composer/auth.json" for future use by Composer. For additional information, check https://getcomposer.org/doc/articles/authentication-for-private-packages.md#github-oauth ⠇ken (hidden): ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. just following the script. Nothing different from the prompts within the installer. ### ❌ Paste the full error output (if available). not available ### 🖼️ Additional context (optional). Tested this on 3 different machines in 2 different locations with the same results using both the advanced and default settings.
OVERLORD added the bug label 2026-02-04 20:20:15 +03:00
Author
Owner

@tremor021 commented on GitHub (Mar 10, 2025):

GitHub API limit (60 calls/hr) is exhausted.

Try again later

@tremor021 commented on GitHub (Mar 10, 2025): `GitHub API limit (60 calls/hr) is exhausted.` Try again later
Author
Owner

@creative0100 commented on GitHub (Mar 10, 2025):

@MickLesk requested the bug post https://github.com/community-scripts/ProxmoxVE/discussions/2883 from this discussion.

@creative0100 commented on GitHub (Mar 10, 2025): @MickLesk requested the bug post [https://github.com/community-scripts/ProxmoxVE/discussions/2883](url) from this discussion.
Author
Owner

@larsassink commented on GitHub (Mar 10, 2025):

I have the same issue, except for me it is just stuck on "Installing SnipeIT" and doesn't do anything.

Update: I am 30 minutes in the process and it still says that it's "Installing SnipeIT"

@larsassink commented on GitHub (Mar 10, 2025): I have the same issue, except for me it is just stuck on "Installing SnipeIT" and doesn't do anything. Update: I am 30 minutes in the process and it still says that it's "Installing SnipeIT"
Author
Owner

@MickLesk commented on GitHub (Mar 10, 2025):

Yeah, thats an Strange REPO Thing. IDK whats faulty with Snipe-IT. It looks as if someone is querying the repo all the time, making it inaccessible to Github. Solution? I have no idea. Probably report directly to the repo.

@MickLesk commented on GitHub (Mar 10, 2025): Yeah, thats an Strange REPO Thing. IDK whats faulty with Snipe-IT. It looks as if someone is querying the repo all the time, making it inaccessible to Github. Solution? I have no idea. Probably report directly to the repo.
Author
Owner

@larsassink commented on GitHub (Mar 10, 2025):

There might be more users stuck on "Installing Snipe-IT", maybe that keeps querying the repo? No idea to be honest.

@larsassink commented on GitHub (Mar 10, 2025): There might be more users stuck on "Installing Snipe-IT", maybe that keeps querying the repo? No idea to be honest.
Author
Owner

@tremor021 commented on GitHub (Mar 10, 2025):

Its stuck at that point because in the background its telling you that you've reached maximum API calls per hour, but you cant see it because all output messages are suppressed in normal install mode

@tremor021 commented on GitHub (Mar 10, 2025): Its stuck at that point because in the background its telling you that you've reached maximum API calls per hour, but you cant see it because all output messages are suppressed in normal install mode
Author
Owner

@MickLesk commented on GitHub (Mar 10, 2025):

Yes, that's probably true, but even for me it doesn't work today only with this repo. Although I have an API token on my proxmox and can therefore make significantly more queries.

@MickLesk commented on GitHub (Mar 10, 2025): Yes, that's probably true, but even for me it doesn't work today only with this repo. Although I have an API token on my proxmox and can therefore make significantly more queries.
Author
Owner

@larsassink commented on GitHub (Mar 10, 2025):

Yeah, same situation for me. I also have an API token. But still, very strange that it's still limited. Other scripts work perfectly fine.

@larsassink commented on GitHub (Mar 10, 2025): Yeah, same situation for me. I also have an API token. But still, very strange that it's still limited. Other scripts work perfectly fine.
Author
Owner

@MickLesk commented on GitHub (Mar 10, 2025):

ive created an issue in there repo. Let's see, maybe we can find a solution together

@MickLesk commented on GitHub (Mar 10, 2025): ive created an issue in there repo. Let's see, maybe we can find a solution together
Author
Owner

@MickLesk commented on GitHub (Mar 10, 2025):

Can anyone of you try it again?

https://github.com/community-scripts/ProxmoxVE/pull/2963

@MickLesk commented on GitHub (Mar 10, 2025): Can anyone of you try it again? https://github.com/community-scripts/ProxmoxVE/pull/2963
Author
Owner

@larsassink commented on GitHub (Mar 10, 2025):

Let me try! I'll update you in a bit

✔️ Set up database ⠋Loading composer repositories with package information ⠹GitHub API limit (60 calls/hr) is exhausted, could not fetch https://api.github.com/repos/grokability/html/contents/composer.json?ref=a4731a834fd2f98ebdb4e8c11b08181e5ee3c652. Create a GitHub OAuth token to go over the API rate limit. You can also wait until 2025-03-10 21:54:56 for the rate limit to reset.

@larsassink commented on GitHub (Mar 10, 2025): Let me try! I'll update you in a bit ` ✔️ Set up database ⠋Loading composer repositories with package information ⠹GitHub API limit (60 calls/hr) is exhausted, could not fetch https://api.github.com/repos/grokability/html/contents/composer.json?ref=a4731a834fd2f98ebdb4e8c11b08181e5ee3c652. Create a GitHub OAuth token to go over the API rate limit. You can also wait until 2025-03-10 21:54:56 for the rate limit to reset.`
Author
Owner

@creative0100 commented on GitHub (Mar 11, 2025):

Can confirm that this now installed without issue.... and the spelling mistake in the label asset was fixed. :)

INFO Application key set successfully.

✔️ Installed SnipeIT
✔️ Configured Service
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
⠼0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
✔️ Cleaned
✔️ Completed Successfully!

🚀 SnipeIT setup has been successfully initialized!
💡 Access it using the following URL:

@creative0100 commented on GitHub (Mar 11, 2025): Can confirm that this now installed without issue.... and the spelling mistake in the label asset was fixed. :) INFO Application key set successfully. ✔️ Installed SnipeIT ✔️ Configured Service Reading package lists... Done Building dependency tree... Done Reading state information... Done ⠼0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Done Building dependency tree... Done Reading state information... Done ✔️ Cleaned ✔️ Completed Successfully! 🚀 SnipeIT setup has been successfully initialized! 💡 Access it using the following URL:
Author
Owner

@creative0100 commented on GitHub (Mar 11, 2025):

Correction:

Just tried to install again, this time using the default option and I get the error message again. This time a slightly different error:

⠧Processing triggers for mariadb-server (1:10.11.6-0+deb12u1) ...
✔️ Installed Dependencies
✔️ Set up database
⠹ Installing Snipe-IT
[ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep '"tag_name"' | sed -E 's/."tag_name": "v([^"]+)./\1/')

Edit 2:
Did another advanced install and snipe-it installed fine.

@creative0100 commented on GitHub (Mar 11, 2025): Correction: Just tried to install again, this time using the default option and I get the error message again. This time a slightly different error: ⠧Processing triggers for mariadb-server (1:10.11.6-0+deb12u1) ... ✔️ Installed Dependencies ✔️ Set up database ⠹ Installing Snipe-IT [ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep '"tag_name"' | sed -E 's/.*"tag_name": "v([^"]+).*/\1/') Edit 2: Did another advanced install and snipe-it installed fine.
Author
Owner

@larsassink commented on GitHub (Mar 11, 2025):

I tried it again as well in advanced mode:

⠋ Installing Snipe-IT
[ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep '"tag_name"' | sed -E 's/."tag_name": "v([^"]+)./\1/')

@larsassink commented on GitHub (Mar 11, 2025): I tried it again as well in advanced mode: ⠋ Installing Snipe-IT [ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep '"tag_name"' | sed -E 's/.*"tag_name": "v([^"]+).*/\1/')
Author
Owner

@tremor021 commented on GitHub (Mar 11, 2025):

OK definitely something is wrong with that specific repo. Is it possible that they're having some sort of attack going so the github itself is limiting calls to that repo? @MickLesk

@tremor021 commented on GitHub (Mar 11, 2025): OK definitely something is wrong with that specific repo. Is it possible that they're having some sort of attack going so the github itself is limiting calls to that repo? @MickLesk
Author
Owner

@bvdberg01 commented on GitHub (Mar 11, 2025):

I had a look at https://api.github.com/rate_limit and it is eating the rate limit when executing the composer command:

Image

@bvdberg01 commented on GitHub (Mar 11, 2025): I had a look at https://api.github.com/rate_limit and it is eating the rate limit when executing the composer command: ![Image](https://github.com/user-attachments/assets/d2a92f2d-d33f-46ef-b873-5ca194d13661)
Author
Owner

@MickLesk commented on GitHub (Mar 11, 2025):

lol

@MickLesk commented on GitHub (Mar 11, 2025): lol
Author
Owner

@bvdberg01 commented on GitHub (Mar 11, 2025):

lol

Maybe because --prefer-source is used?

@bvdberg01 commented on GitHub (Mar 11, 2025): > lol Maybe because --prefer-source is used?
Author
Owner

@MickLesk commented on GitHub (Mar 11, 2025):

we can try it after merge:
https://github.com/community-scripts/ProxmoxVE/pull/3009

@MickLesk commented on GitHub (Mar 11, 2025): we can try it after merge: https://github.com/community-scripts/ProxmoxVE/pull/3009
Author
Owner

@larsassink commented on GitHub (Mar 11, 2025):

Here we go again:

⠙ Installing Snipe-IT [ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')

@larsassink commented on GitHub (Mar 11, 2025): Here we go again: ` ⠙ Installing Snipe-IT [ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')`
Author
Owner

@angeeinstein commented on GitHub (Mar 18, 2025):

I get the same rate limit problem. When trying with a GitHub auth token installed, I get ⠹ Installing Snipe-IT [ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')

@angeeinstein commented on GitHub (Mar 18, 2025): I get the same rate limit problem. When trying with a GitHub auth token installed, I get ` ⠹ Installing Snipe-IT [ERROR] in line 45: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/snipe/snipe-it/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')`
Author
Owner

@MickLesk commented on GitHub (Mar 18, 2025):

yeah, we dont know why. Even my extended token runs directly into the limit

@MickLesk commented on GitHub (Mar 18, 2025): yeah, we dont know why. Even my extended token runs directly into the limit
Author
Owner

@MickLesk commented on GitHub (Mar 19, 2025):

its an composer issue. I'm trying to find out why.

@MickLesk commented on GitHub (Mar 19, 2025): its an composer issue. I'm trying to find out why.
Author
Owner

@MickLesk commented on GitHub (Mar 19, 2025):

Works now. Can anyone approve the working function? Maybe you try directly in verbose mode.

Image
@MickLesk commented on GitHub (Mar 19, 2025): Works now. Can anyone approve the working function? Maybe you try directly in verbose mode. <img width="702" alt="Image" src="https://github.com/user-attachments/assets/a362e502-d43f-4c06-94f3-b580caf1ae0f" />
Author
Owner

@angeeinstein commented on GitHub (Mar 19, 2025):

It works for me

@angeeinstein commented on GitHub (Mar 19, 2025): It works for me
Author
Owner

@bvdberg01 commented on GitHub (Mar 19, 2025):

Works for me also right now. Only used 2 api calls

@bvdberg01 commented on GitHub (Mar 19, 2025): Works for me also right now. Only used 2 api calls
Author
Owner

@V1R7U4LS7OR4G33K commented on GitHub (Jul 19, 2025):

GitHub API limit (60 calls/hr) is exhausted.

Try again later

is there a way to prevent this from happening?

@V1R7U4LS7OR4G33K commented on GitHub (Jul 19, 2025): > `GitHub API limit (60 calls/hr) is exhausted.` > > Try again later is there a way to prevent this from happening?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#616