-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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 generating backup #14657
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. |
Please provide us with the information requested at the Getting Help documentation:
|
Hello installed in docker with docker compose up. |
You should just be able to do the things outlined in the upgrade guide in the docs. (Git pull, composer install, php artisan migrate, etc.) That’s all the upgrade script is really doing anyway. Once you’ve upgraded, that port error you’re seeing should go away. |
Hello I get this error, both in the docker container as well as the VM: "Could not open input file: composer.phar" |
Debug mode
Describe the bug
When trying to save a backup I get error 500. therefore I cannot create a backup before upgrading. can I still upgrade to the latest version without risks of losing data?
version is v6.3.1 build 12672 (g00cea3eb3)
Reproduction steps
1.Go to settings
2. click on backup
3. click on generate backup
...
Expected behavior
a backup is generated.
Screenshots
No response
Snipe-IT Version
v6.3.1
Operating System
Docker(Ubuntu)
Web Server
Apache
PHP Version
8.1.2
Operating System
Windows
Browser
Edge
Version
No response
Device
No response
Operating System
No response
Browser
Edge
Version
No response
Error messages
Spatie\DbDumper\DbDumper::setPort(): Argument #1 ($port) must be of type int, string given, called in /var/www/html/vendor/spatie/laravel-backup/src/Tasks/Backup/DbDumperFactory.php on line 56
Additional context
No response
The text was updated successfully, but these errors were encountered: