Closed olvegg closed 1 month ago
welcome[bot]
commented
1 month ago 👋 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
commented
1 month ago The storage/logs/laravel.log being empty is a bit worrisome. Can you check the permissions and make sure that directory is writable? That 500 could be because it's unable to write to the log file.
olvegg
commented
1 month ago Thanks for checking in, the issue was resolved today. I can confirm laravel.log is still empty and the permissions is 664 while the storage folder is 775. As you raised the issue with laravel, I thought to search what could be done to troubleshoot it and found a resource including the following commands:
php artisan config:cache
php artisan config:clear
php artisan cache:clearInterestingly, what happened now is that laravel.log is still empty BUT Snipe-IT debug bar has finally appeared which wasn't on before .. AND the mail test worked!
I have no idea what prevented the debug bar to show up before, or the email to work but it seems that the laravel commands have resolved something..??
In any case, I appreciate you responding so quickly and providing the impetus to check what was going on with laravel. I don't know if the file should still be empty, but at least now the system works as intended.
snipe
commented
1 month ago Great, glad you're sorted :) We usually recommend running those commands first just to rule out any caching issues. https://snipe-it.readme.io/docs/common-issues#quick-tip-handy-commands
Snipe-IT Documentation🚧 Problem Installing/Upgrading?: We've moved the the most common installation/upgrade issues to their own page. If you're having an issue installing or upgrading Snipe-IT, please check the Installation/Upgrading Issues page before opening a ticket on Github . Quick Tip: Handy Commands 👍 Many issue...
Debug mode
Describe the bug
I have recently setup Snipe-IT on my dreamhost VPS. I have also setup a Microsoft 365 SMTP relay which allows for my VPS IP address to send email without authentication for my external services such as my wordpress site or snipe-it.
My Wordpress uses the SMTP relay on port 25 without user authentication without any issue, I also tested directly from the VPS console via telnet to my SMTP relay on port 25. Snipe-IT on the other end throws the following error:
When using the General Settings "Test Mail" function.
Reproduction steps
Expected behavior
Expecting that mail notifications test work instead of throwing errors
Screenshots
No response
Snipe-IT Version
v7.0.3 build 13980
Operating System
Ubuntu Server 20.04.1 LTS
Web Server
Apache
PHP Version
8.2.15
Operating System
Windows 11
Browser
Firefox
Version
128.0 (64-bit)
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
[Snipe-IT Debug] I do not see any Snipe-IT error with debug mode turned on besides the error message.
[Browser's console]
[Storage/logs] The laravel.log file is empty which is surprising given that I enabled debug mode?
[Demo Reproduction] Not applicable: This cannot be reproduced in demo as the .env smtp configuration and the demo server ip authentication on MS365 is required to reproduce the issue.
[PHP Modules]
[ENV file content]
Additional context
This is a fresh install
I manually configured Snipe-IT
I have attempted to use smtp, mail or sendmail without any success
I have tested the SMTP relay to make sure it's not the issue by:
The browser console response is confusing as the .env isn't configured to authenticate with the email mentionned there:
Why would it try to authenticate with this email? This is the email of the user I use to go and test in the admin settings, but it is NOT the email configured in the .env for sending emails.
Thank you for your help on this issue.