Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 server error upon audit completion - hosted instance #16019

Open
ANSAJason opened this issue Jan 3, 2025 · 2 comments
Open

500 server error upon audit completion - hosted instance #16019

ANSAJason opened this issue Jan 3, 2025 · 2 comments
Labels
❓ not sure if bug This issue has not been confirmed as a bug yet

Comments

@ANSAJason
Copy link

ANSAJason commented Jan 3, 2025

The issue I am running into with our install of snipe-it (hosted, so I do not have access to debug/server) is when finishing an audit of asset, it returns a 500 server error.
(7.1.15)

The odd thing is it seems everything is saved, the audit is complete and the asset is updated.

The problem is as I create step outs/ guides / processes for maintaining our assets I would prefer not to bake in extra refreshes / clicks / and errors to prevent constant questions from the people I task with it.

Copy link

welcome bot commented Jan 3, 2025

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@snipe
Copy link
Owner

snipe commented Jan 6, 2025

Hi @ANSAJason - please open a ticket with us at [email protected] so we can pull your server logs and look a little closer. Most of the time, this is because a slack/teams/other webhook is misconfigured, it it might throw the 500, but since that happens after the audit actually happens, the audit is record, it's just the notification that can't be sent.

@snipe snipe added the ❓ not sure if bug This issue has not been confirmed as a bug yet label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❓ not sure if bug This issue has not been confirmed as a bug yet
Projects
None yet
Development

No branches or pull requests

2 participants