Open Joly0 opened 1 year ago
Could someone please look at this? @uberbrady (sorry for the ping, but i am quite frustrated now)
I'm trying to figure out if the problem is on our end (which is possible), or if it's something in the laravel-backup package. I'll report back.
Hrm, so if you go to config/database.php
, if you scroll down to the connections
/ mysql
/ dump
part - you'll see a commented-out add_extra_option
part in there.
Try and add the options --ssl-ca='/cert.pem' --ssl=1
to that. Does it work if you do that? If so, that'll give you a temporary workaround and will give me an idea of what to put in to a PR to get SSL-restricted MySQL backups working correctly.
Yes indeed this fixed the issue. Had to adjust the path to the pem file, but afterwards it did work in a test environment Unfortunately i am trying to run snipe-it in an azure web app for containers and i dont have shell access there so i cant edit the files and therefore would have to wait for a release/push to master on your site. But thank you so far :)
Well, that's at least a start, I guess. I'll have to try and figure out how to translate all the various .env
values we have into the appropriate add_extra_option
parts. It may still make sense to have this change implemented at the laravel-backup side; I don't know.
Yep, i am glad this issue is solved now. Thank you very much for your effort. If some testing is required, i am willing to apply as a helper
Hey @uberbrady (sry for the ping )
Maybe you could add your information here https://github.com/spatie/laravel-backup/discussions/1679 aswell, so the package creators know about the issue and solution aswell and maybe can do something on their side. I am not as knowledgeable as you and might mix something up explaining the issue there.
Otherwise if there is anything i can do or help with, eg. testing a different branch with a fix or something else, please let me know :)
GitHubHey, i am using snipe-it which uses laravel-backup and i have an issue open over there aswell (snipe/snipe-it#12852) but it doesnt seem like i will get any help. I did some testing and the mysqldum...
Hey @uberbrady have you yet been able to get this properly implemented?
Debug mode
Describe the bug
I am running snipe-it as a docker container with azure and have a paas mysql database on azure aswell. So far, everything works as expected, except for the backups, which dont work. The moment i click on "create backup" i am presented with this error message:
For the database i have ssl enabled and for the container i have set these environment variables
I have already looked into this and found this issue https://github.com/snipe/snipe-it/issues/11785 but this is not my problem. So far the laravel.log is empty aswell, so no hints from there aswell.
I have tried accessing the db with the same username, pw and ssl certificate as the snipe-it container uses through mysql workbench and there everything works 100% fine.
Reproduction steps
Expected behavior
The backups should work, as everything else does
Screenshots
No response
Snipe-IT Version
v6.1.0 - build 10161
Operating System
Azure Web App
Web Server
Nginx
PHP Version
8.1
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
Additional context
No response