-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Error 500: creating categories and asset models page #13714
Comments
👋 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. |
If that's what the error is, it's still unable to write to the
|
it seems i have resolved the issue by running: semanage fcontext -a -t httpd_sys_rw_content_t "/srv/snipeit/storage(/.)?" as root :) Thank you! |
Glad you're sorted :) |
Debug mode
Describe the bug
hello,
i have a completely clean install and i have reinstalled the OS and application multiple times, but now i am at a loss as to what is the problem here..
I receive this Error 500 window when clicking either create asset model or create category. the issue seems to be the same as a lot of other users: Exception
The /var/www/html/snipeit/bootstrap/cache directory must be present and writable.
i have check the permissions of the cache file:
drwxrwxr-x. 2 snipeitapp apache 46 Oct 5 17:23 cache
and during install, it is also noted that the cache directory IS wirtable. i am also able to create directories and files under the cache folder
thank you for the help
Reproduction steps
...
Expected behavior
for the application to work as intended
Screenshots
Snipe-IT Version
v6.2.1 build 11625
Operating System
centOS stream 8 (vmware)
Web Server
apache
PHP Version
7.4.33
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: