BorgWarehouse webGUI no longer creates folder in storage location?

[tehbuhtig]

BorgWarehouse version : 3.1.1

Installation type :

• [x] Docker
• [ ] Baremetal (Debian/Ubuntu)
• [x] Other environment : Debian 12 VM running on proxmox 8

---

hey guys.

I've been playing around a bit w/ my BorgWarehouse installation and ran into a strange issue. I had originally installed BorgWarehouse on top of a Debian 12 VM per the instructions in the documentation. this worked great but I wanted to try out the docker container, so shifted to that. I eventually got that working too, but decided that I liked the VM approach better, and decided to move back to the VM.

this is where the weirdness began.

after restoring the VM I thought I would start over w/ a new repo. I successfully created a new repo in the BorgWarehouse webGUI, but was not able to link pika backup to it. upon further inspection, the create new repo button did not create the corresponding folder in the storage location. then I went into troubleshooting:

1. updated BorgWarehouse to latest 3.1.1 --> no change
2. shut down the VM and started the docker container again --> no change
3. tried using a local folder instead of a mounted NFS share, both in VM and docker container --> no change
4. tried using both the new repo and existing repo setup options in pika --> different errors for each but neither worked
5. manually created the folder myself w/ name matching the one created in the webGUI --> errors in pika saying repository path not allowed 5a. oddly enough, after manually creating the folder myself, deleting the repo in the webGUI will delete the folder in the storage location

this all worked fine only weeks ago when I set up the docker container. I thought maybe I donked up the NFS permissions, but trying w/ a local folder did not change anything. also I could create files and folders just fine via the command line in both the VM and the docker container. and the delete function in the webGUI worked as expected.

I checked the logs in the borgwarehouse docker container and did not see anything out of sorts. I cannot find the borgwarehouse logs in the VM despite searching.

I managed to work around the problem for now by:

1. creating a new repo in the webGUI
2. manually creating the folder w/ name matching the one created in the webGUI in the NFS storage location
3. copy old backup data per the import old repositories instructions from the documentation
4. configure existing repo in pika backup

backing up using pika and borgwarehouse works now, but I don't think I should have to do steps 2 or 3. not sure why they are needed now when I did not need to do that before.

any help would be appreciated. I am keeping around both the docker container and a copy of the VM if you guys want me to do any further troubleshooting.

[robfuscator]

Late to the party, but I've found your issue trying to link Pika to a freshly created repo and getting a Path Not Allowed error.

I'm not sure if I understood your problem correctly, but in my case I've just misunderstood the process of creating a repo. If I understood correctly, BorgWarehouse doesn't create the actual borg repo for you, but just simplifies the process of allocating space and setting up the SSH access permissions.

So the process is (1) create the repo in BorgWarehouse, (2) create the repo in PikaBackup, (3) create backups. I suspect you might have missed step two, as I did.

[tehbuhtig]

hey robfuscator. (great username btw!)

thanks for the comments, but the problem I am having is all in what you have listed as step (1).

when I click on the add a repo button in the borgwarehouse webGUI, the repo gets created in borgwarehouse (i.e. added to the repo.json file in the borgwarehouse config folder and shown in the webGUI) but the corresponding folder on the actual storage (in my case on the nfs share from my truenas server) does not get created. I have to do some manual workarounds to make it work, as described above.

this is new behavior - when I first set all this up in the v2 days, it worked as expected.