2 hours ago, Cressio said:

Sort of a Docker noob, to switch to the new maintainer/repo, do I just change ghcr.io/hay-kot/homebox:latest to ghcr.io/sysadminsmedia/homebox:latest? Or will that break everything

Yes that , what you need to do
and image do exist now , so you can go, and it is a drop in replacement.
I did it on mine to test and update the template.

 

new image : ghcr.io/sysadminsmedia/homebox:latest

Edited June 21, 20242 yr by ZappyZap

I've got Homebox installed and using a custom interface on one of my vlan subnets.  All that works fine, but I'd like it to listen on port 80 rather than 7745.  I've tried everything I can think of but nothing seems to work.  Is this something that I can change?

On 12/1/2024 at 2:45 AM, jrsphoto said:

I've got Homebox installed and using a custom interface on one of my vlan subnets.  All that works fine, but I'd like it to listen on port 80 rather than 7745.  I've tried everything I can think of but nothing seems to work.  Is this something that I can change?

the webui listen on port 3110 on the host 
you can change that by changing the variable "Web UI port" :
 

Edited December 2, 20241 yr by ZappyZap

This app was failing to start for me from a fresh install with this error in the logs:

panic: parsing config: parsing config: conf: error assigning to field ReadTimeout: 
converting '10' to type time.Duration. details: time: missing unit in duration "10"

Updating these environment variables to include an 's' after the numeric value for each resolved the issue:

HBOX_WEB_READ_TIMEOUT

HBOX_WEB_WRITE_TIMEOUT

HBOX_WEB_IDLE_TIMEOUT

 

 

Hello,
thanks for the report i will validate and take the appropriate action

Thanks so much

On 2/6/2025 at 4:32 AM, darias said:

This app was failing to start for me from a fresh install with this error in the logs:

panic: parsing config: parsing config: conf: error assigning to field ReadTimeout: 
converting '10' to type time.Duration. details: time: missing unit in duration "10"

Updating these environment variables to include an 's' after the numeric value for each resolved the issue:

HBOX_WEB_READ_TIMEOUT

HBOX_WEB_WRITE_TIMEOUT

HBOX_WEB_IDLE_TIMEOUT

 

 

I can confirm that this fix worked for me - @ZappyZap please update the Template to reflect the correct variables so that future downloads aren't affected.

3 hours ago, valiente said:

I can confirm that this fix worked for me - @ZappyZap please update the Template to reflect the correct variables so that future downloads aren't affected.

Updated 
thanks

Hi,

 

I've experienced a problem with this deployment and was wondering if anyone has experienced anything similar. I also posted a bug report on Homebox's Github issues.

https://github.com/sysadminsmedia/homebox/issues/588

 

The issue is as follows: 

 

Attempting to open a document from an item leads to a 404 page. After examining the DB file, the path under the document appears to be correct. However, Homebox is unable to retrieve the file. All files are still present on the disk and no modifications have been been made to the DB in the last 2 weeks. Homebox is running in a Docker container on Unraid 7.0.1.

 

Database item Example:

 

Item ID: d6fe9ea1-7c9c-42aa-9a01-7c940dea2a52

 

Attachment ID: d78b071a-752d-47e6-a1bc-fcacb3cb96f6

 

Group ID: 21cbe24a-beb5-4974-bb65-0f38a59df6d1

 

Document ID: dd3b3cc9-6ff4-40e4-8d6b-afe8f9780438

 

document_attachments: dd3b3cc9-6ff4-40e4-8d6b-afe8f9780438

 

item_attachments: d6fe9ea1-7c9c-42aa-9a01-7c940dea2a52

 

path: /data/21cbe24a-beb5-4974-bb65-0f38a59df6d1/documents/4615bcbc-9ece-4bd7-9841-9657104f53ba.pdf

 

It is not clear why the issue happened therefore it is difficult to provide steps to reproduce the issue.

However, all I have done is created multiple items. Categorized the items under particular locations. Created parent and children items. Attached documents like photo, manual, receipt, etc. Save the changes. Waited ~2 weeks prior to accessing a file. Received error 404 when attempting to access the file.

 

If anyone has any experience with something similar happening or if you can recommend something I can try to fix the problem it would be greatly appreciated.

Thanks

 

EDIT

When adding a new attachment to an existing item I'm still presented with a 404 when attempting to view it. However the item is successfully added to the DB and to the path for the documents. Upon deleting the attachment the file is successfully removed from the DB and from the path on the file system.

 

EDIT 2 (SOLUTION)

I was able to resolve the issue by logging out and logging back in. Perhaps the session was invalidated previously thereby denying access to the attachments.

Everything is now working as it should.

Edited May 12, 20251 yr by GiulioCD
Solution

I did not experienced this , but i did not switch to 7.x.x train 
i will follow this issue on the github
thanks for the report

Hi, Installed the docker a couple months ago to track some stuff, tried to log back in as it didn't remember me/logged me out in between then and now and I get an error message "Invalid email or password".
Since I used a password manager, I know I'm not typing it wrong but to avoid having to redo all the work, would their be anyway to "hack" me back into the account? Any which would be simple enough? The only issue I can think of is because the generated password was long and with special characters maybe an update caused it to be invalid shrug

I'm seeing in the template fields to set up email related things but I don't see a password recovery on the main page of HomeBox.

Edit: fixed it by opening the db file and editing the password hash to "$argon2id$v=19$m=16,t=3,p=2$aG9tZWJveGU$hrwLfKINzqdjHDH0B3xCVw" which is for "password123", was able to log in and reset password to the previous one.

Edited September 30, 2025Sep 30 by Eddyall

There is an error in the template:

Container Variable: HBOX_MODE has a typo (HMOX_MODE)

9 hours ago, Wozzagonebush said:

There is an error in the template:

Container Variable: HBOX_MODE has a typo (HMOX_MODE)

Hi @Wozzagonebush thanks for the report i will have fix asap

Dear community,

I am trying to enable direct HTTPS inside your HomeBox container on UnRAID 7.1.4 (without Nginx Proxy Manager) using the UnRAID Docker template editor and the SSL certificate already enabled on my system.

I tried the approach below to keep all traffic local and encrypted, allowing HomeBox’s Scanner to function correctly (current message "Media Stream API is not supported without HTTPS"). Unfortunately, I was not able to get it to work. Once I performed the steps and rebooted the container - the webpage still does not open under port 7743 using https. It keeps working with port 3100 though.

Would appreciate your help on how to enable https in order to make the scanner functionality work.

Thanks in advance and kind regards,

JB

Step 1: Prepare your SSL certificate

Since you have already activated SSL under Settings → Management Access, UnRAID generated a trusted certificate—usually stored at:

/boot/config/ssl/certs/<yourservername>_unraid_bundle.pem

You can reuse it for your container by splitting it into certificate and key files.

1. Open the UnRAID web terminal.

2. Run:

3. mkdir -p /mnt/user/appdata/homebox/ssl cd /boot/config/ssl/certs/ cp <servername>_unraid_bundle.pem /mnt/user/appdata/homebox/ssl/

4. Split the PEM file into key and cert:

5. awk 'split_after==1 {n++;split_after=0} /BEGIN PRIVATE KEY/ {split_after=1} {print > "server" (n ? n : "") ".pem"}' <servername>_unraid_bundle.pem

   Or manually copy the key and certificate sections into:

   • /mnt/user/appdata/homebox/ssl/server.key

   • /mnt/user/appdata/homebox/ssl/server.crt

This gives you two required files: server.key and server.crt.unraid+1

---

Step 2: Edit the HomeBox container

1. Go to the Docker tab.

2. Click Edit on the HomeBox container.

3. Enable Advanced View (top right toggle).

4. Under Extra Parameters, add environment variables:

5. -e HOMEBOX_SSL_CERT=/ssl/server.crt -e HOMEBOX_SSL_KEY=/ssl/server.key

6. Under Add another Path, Port, Variable, Label or Device:

   • Config Type: Path

     • Host Path: /mnt/user/appdata/homebox/ssl

     • Container Path: /ssl

     • Set Access Mode: Read-only

   • Config Type: Port

     • Host Port: 7743

     • Container Port: 443

     • Connection Type: TCP

Ensure the original HTTP port (3100) remains if you still want HTTP access.

---

Step 3: Apply and restart

• Click Apply to recreate the container.

• Once restarted, wait a few seconds for the service to initialize.

• You can verify the logs by clicking the container’s Log icon. If configured correctly, it should show:

• Listening on https://0.0.0.0:443

---

Step 4: Access HomeBox securely

Open a browser on your LAN and visit:

https://<your-unraid-ip>:7743

If you used the UnRAID-issued certificate, your browser should already trust it if the hostname matches. Otherwise, you may need to temporarily accept the certificate.

After logging in, test the Scanner in HomeBox — camera and barcode capture should now function because the page is served over HTTPS.homebox+1

I will need to try to reproduce ... .as i am using a RP

On 12/1/2024 at 11:58 PM, ZappyZap said:

the webui listen on port 3110 on the host 
you can change that by changing the variable "Web UI port" :
 

This didnt work. I cant get this running on port 80

On 12/1/2024 at 11:58 PM, ZappyZap said:

the webui listen on port 3110 on the host 
you can change that by changing the variable "Web UI port" :
 

This didnt work. It will not work on port 80.

Where's the data stored?

I must be missing something obvious. I installed the docker back in Sept. and had imported my inventory from a prev. system, uploaded all the photos, etc. I noticed that the files in the user\appdata\homebox share showed no updates from my activities and I couldn't find where the data was being stored. But everything was working and I went on to other things. I had accessed it a few times since then without issue.

Today I opened the docker and it wouldn't recognize my credentials (stored in PW manager and never changed). I re-registered and all the data was reset to the default for a new install. I imported my initial data again (luckily saved the import file) and will have to do all the other updates I have done. But, even after all the changes I have made today, I see that there are only three files in the user\appdata\homebox share (homebox.db-wal, homebox.db-shm, and homebox.db) and they have a last modified date of 2025-09-19. I checked the docker configuration and don't see any parameters to define where the docker data is stored for homebox. I want to ensure I know where the data is stored so I can back it up to prevent another data loss.

EDIT: OK, I've found the problem. The Docker image has the same three data files (homebox.db-wal, homebox.db-shm, and homebox.db) as exist in the user\appdata\homebox share. It is those files that are getting updated. I would think the docker should be storing the data in the appdata share and not the docker image. Not sure if there is a reason the data is stored in the image and if there is a way to change it to store the data in user\appdata\homebox - preferably without losing any data.

EDIT #2: So, I dug into the documentation for Homebox and found the following configuration within the default compose.yml file: homebox-data: /data/

I then created a new configuration option in the Homebox Unraid Docker with the following options:

• Config Type: Path

• Name: homebox-data

• Container Path: /data/

• Host Path: /mnt/user/appdata/homebox/

• Access Mode: Read/Write

After restarting the docker, it was again acting as if I had not registered (expected if it was using a different storage location). After registering, I was gain faced with a new system and the default entries. I imported my last export to get back to where I last was (without images). I could then see that the files in the appdata share (user\appdata\homebox) were now being updated as I made changes in Homebox. I believe this is how it should be configured. Please advise if this is problematic. I will continue to verify that everything continues to function as expected.

Edited March 2Mar 2 by mjdamato
I think I found a solution

1 hour ago, mjdamato said:

EDIT: OK, I've found the problem. The Docker image has the same three data files (homebox.db-wal, homebox.db-shm, and homebox.db) as exist in the user\appdata\homebox share. It is those files that are getting updated. I would think the docker should be storing the data in the appdata share and not the docker image. Not sure if there is a reason the data is stored in the image and if there is a way to change it to store the data in user\appdata\homebox - preferably without losing any data.

FWIW, I just went into Homebox and added a location, and the homebox.db file in my appdata/homebox folder updated.

Forgive me if you know this already, but the files will appear in the container if you access it via the console. Same files in appdata/homebox on the server, and /data in the container.

On 3/2/2026 at 12:36 PM, darias said:

FWIW, I just went into Homebox and added a location, and the homebox.db file in my appdata/homebox folder updated.

Forgive me if you know this already, but the files will appear in the container if you access it via the console. Same files in appdata/homebox on the server, and /data in the container.

Sorry for the delayed response. Notifications weren't enabled for me on this forum.

I guess I don't know that and I'm not really following you. Let me restate what I found to make sure I didn't misstate something:

• After installing the homebox docker and using the application for a while, the data under appdata\homebox had not been changed since I first set up the docker. There were three files related to the DB but they had never been changed since setting up the docker and there were no files related to the many files I had uploaded.

• I then found that the same three file names for the DB (with newer date/times) and all the images I had uploaded were instead contained within the docker image.

So, when I made changes they were only written to the docker image, they were not getting written to the adddate folder. It was my understanding that the appdata share was for storing the "data" for the dockers and the docker image was to hold all the "logic" needed to run the docker. I'm not terribly versed in how the dockers work but, based on your last comment, are you saying that when a docker is started it should load the data from the appdata location into the docker container? I could see where that would make sense. If that is the case, shouldn't the homebox data get written back to the appdata folder at some point? Mine never was - the data was only ever updated in the docker image.

Also, many of my dockers have a configuration for the container to set the appdata location. E.g. My Plex docker has a "AppData Config Path: /mnt/user/appdata/binhex-plex" and my Duplicati docker has "Appdata: /mnt/user/appdata/duplicati". Some don't have a setting and neither does my Homebox docker. But as soon as I added a new parameter for the Homebox docker, as noted in my second edit, to set and set the location to the appdata folder I could see that data was being written to my appdata folder as I made changes. I assumed that this is how it should work.

If this is going to cause problems I would appreciate some guidance. I was just trying to prevent my docker image from growing too large because of all the files I am uploading to homebox.

EDIT: OK, after some trial and error. I see that when I am making changed within homebox it is now updating the files in both the docker.img (when accessed via the container console) and within the appdata\homebox directory. I am guessing that the results I get from the console looking inside the docker.img are maybe just a pointer back to the appdata/homebox folder. That all makes sense now. But I still don't know where the data was being stored before I added the config path entry to the docker template. The files were absolutely not being stored in the appdata/homebox directory.

Edited March 8Mar 8 by mjdamato

6 hours ago, mjdamato said:

EDIT: OK, after some trial and error. I see that when I am making changed within homebox it is now updating the files in both the docker.img (when accessed via the container console) and within the appdata\homebox directory. I am guessing that the results I get from the console looking inside the docker.img are maybe just a pointer back to the appdata/homebox folder. That all makes sense now. But I still don't know where the data was being stored before I added the config path entry to the docker template. The files were absolutely not being stored in the appdata/homebox directory.

Bingo. When you browse the /data directory through the Docker console, you're actually looking at files in appdata/homebox on your server. If you didn't have a directory mapping in your Docker configuration to map /data to appdata/homebox, then Homebox is just going to write to the /data directory as usual, which is going to be in the Docker image. Does that make sense?

Edited March 8Mar 8 by darias

8 hours ago, darias said:

Bingo. When you browse the /data directory through the Docker console, you're actually looking at files in appdata/homebox on your server. If you didn't have a directory mapping in your Docker configuration to map /data to appdata/homebox, then Homebox is just going to write to the /data directory as usual, which is going to be in the Docker image. Does that make sense?

Yes, makes sense. Thank you! I had expected that the template for the Unraid Docker from CA would have included the parameter to map /data to the appdata folder. You stated it was working for you, so I wonder if that parameter got dropped along the way in a later update of the template. I certainly don't want to question the dev who created the docker template as I'm not all that familiar with the dockers and am just benefiting from others work.

If I can ask one unrelated question. The current version of Homebox has a bug that kills the session when opening a record with a PDF attachment. The only workaround at this time is to downgrade. In my docker configuration I have the value

Repository: ghcr.io/sysadminsmedia/homebox:latest. I know I need to replace the :latest tag to the value for a specific prior release. I've tried changing repository to ghcr.io/sysadminsmedia/homebox:v0.23.0 (which is the version prior to the current bug) and clicking apply and applying, but that isn't working (error below). Am I using the wrong format, or is the tag some other value I'm not finding? Thank you again for your help.

 --restart=unless-stopped 'ghcr.io/sysadminsmedia/homebox:v0.23.0'
Unable to find image 'ghcr.io/sysadminsmedia/homebox:v0.23.0' locally
docker: Error response from daemon: manifest unknown.
See 'docker run --help'.
The command failed.

59 minutes ago, mjdamato said:

Am I using the wrong format, or is the tag some other value I'm not finding? Thank you again for your help.

Not entirely sure on this one. Did you try homebox:0.23.0?

3 minutes ago, darias said:

Not entirely sure on this one. Did you try homebox:0.23.0?

That was it! I was digging into the repository thinking I needed to use the GUID associated with the version or some such value associated with the release. Thanks again.

I need to review this, the app have chenged look like and i have been sick for the last 2 week, and unable to keep focus in front of comp for more than 1h ....
I will get this reviewed

Hi everyone,

An update is required for the Homebox Docker template to run after the recent update to v0.26. According to the Homebox Quick Start Guide new environment variable, HBOX_AUTH_API_KEY_PEPPER, must be added to your template. Without this variable, the container will fail to start.

How to Update Your Template:

1. Go to the Docker tab in your Unraid WebUI.

2. Click on the Homebox icon and select Edit.

3. Scroll to the bottom and click Add another Path, Port, Variable, Label or Device.

4. Fill out the form with the following details:

   Config Type: Variable

   Name: API Pepper

   Key: HBOX_AUTH_API_KEY_PEPPER

   Value: Result from openssl output

5. Run openssl rand -base64 48from the Unraid console and paste the output in the Key.

Hope this helps anyone trying to start the container after the update.

Edited June 14Jun 14 by Alex.vision
API name mistake

I will update it
thanks for the head-up