Closed bmg12249 closed 2 years ago
hi, actually i don't think this is a problem at your end as i see other people have the same problem from time to time on the uisp forum.
Check the logs after trying to restore the backup (docker logs container_name) and post them here. Also, you can try to create a new 1.3.11 container, restore the backup and then upgrade to 1.4.2.
hi logs below. thanks
Sentry release:
Version: 1.4.2+4b508a57da.2022-01-16T00:54:44+01:00
Waiting for database containers
Restoring backups and/or running migrations
yarn run v1.22.15
$ yarn backup:apply && yarn migrate && yarn check-crm-db
$ node -r ts-node/register/transpile-only ./cli/apply-backup
{"name":"UNMS","hostname":"b1d5e1dea693","pid":4492,"level":30,"msg":"Restoring UCRM backup","time":"2022-02-08T16:30:14.796Z","v":0}
{"name":"UNMS","hostname":"b1d5e1dea693","pid":4492,"level":30,"msg":"Restoring UISP backup","time":"2022-02-08T16:33:30.629Z","v":0}
{"name":"UNMS","hostname":"b1d5e1dea693","pid":4492,"level":30,"msg":"Destroying SSH connection to cloud.","time":"2022-02-08T16:33:35.268Z","v":0}
{"name":"UNMS","hostname":"b1d5e1dea693","pid":4492,"level":50,"err":{"message":"500 - \"sh: /ssh-proxy.sh: not found\n\"","name":"StatusCodeError","stack":"StatusCodeError: 500 - \"sh: /ssh-proxy.sh: not found\n\"\n at new StatusCodeError (/home/app/unms/node_modules/request-promise-core/lib/errors.js:32:15)\n at Request.plumbing.callback (/home/app/unms/node_modules/request-promise-core/lib/plumbing.js:104:33)\n at Request.RP$callback [as _callback] (/home/app/unms/node_modules/request-promise-core/lib/plumbing.js:46:31)\n at Request.self.callback (/home/app/unms/node_modules/request/request.js:185:22)\n at Request.emit (node:events:390:28)\n at Request.emit (node:domain:475:12)\n at Request.
There's a permission issue with the images directory. Also, it actually isn't saved in the persistent directory, causing it to get wiped every time the container is recreated. I pushed a fix to the testing branch, please test it by using the testing
tag instead of latest
or 1.4.2
when starting / creating the container.
For example:
docker run -d --name unms -p 80:80 -p 443:443 -p 2055:2055/udp -v </path/to/config>:/config nico640/docker-unms:testing
hi, This worked backup restored all running ok now .( there is an issue that it hangs about once a day both on 1.42 and 1.3.11 on bullseye but not on buster and brings network down but not a problem for me). thanks
hi, i upgraded to bullseye on raspberry pi after having problems installing on previous buster and all went well but i am unable to restore my backup file from 1.3.11. It goes through the motions and looks like its restoring but eventually returns to the uisp setup page. any pointers?? thanks