Homepage & Truenas Scale Electric Eel

[SavanFlou]

Description

Hello everyone,
I made the migration to Electric Eel yesterday, and Homepage did not survive to this.
To be clear,
It worked like a charm before and I was very happy with it.
Now, the app does not take into account the IP address of my servor, and put a 0.0.0.0 address, but with the correct webUI port defined in the settings.
So to be simple, the webUI sent me to "http://0.0.0.0:30054" and not http://xx.xx.xx.xx:30054"

So can someone explain to me what to add to the setting to define the correct url?

Thank you.

homepage version

v0.9.11

Installation method

Other (please describe above)

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

When I click on WebUI
the pointed URL is http://0.0.0.0:30054
I do not see what to add more :)

[ihatemyisp]

This is a bug within TrueNAS. I confirmed the behavior in Elec Eel RC.2. You should report the issue with them at https://github.com/truenas/apps/issues.

That said, you can simply replace the 0.0.0.0 (in the address bar) with the ip or hostname of your TrueNAS machine and it will work just fine.

[SavanFlou]

Hello, thanks for the help.

But actually, my problem is more complex than just the problem with 0.0.0.0

I cannot use Homepage if I choose to use one of my datasets to store the data, it must be the IxVolume. If I try to define the Host Path, I always get the errors.

When I try to see Homepage with an Host Path, I will always get the same message instead of Homepage

"Application error: a client-side exception has occurred (see the browser console for more information"

And if I look at the log of my container in Truenas

024-10-25 21:51:53.596339+00:00Listening on port 30054
2024-10-25 21:52:08.276138+00:00error copying config Error: EACCES: permission denied, copyfile '/app/src/skeleton/settings.yaml' -> '/app/config/settings.yaml'
2024-10-25 21:52:08.276265+00:00at copyFileSync (node:fs:2982:3)
2024-10-25 21:52:08.276280+00:00at checkAndCopyConfig (/app/.next/server/chunks/1227.js:53:55)
2024-10-25 21:52:08.276303+00:00at init (/app/.next/server/pages/index.js:4837:76)
2024-10-25 21:52:08.276315+00:00at createLogger (/app/.next/server/pages/index.js:4881:5)
2024-10-25 21:52:08.276331+00:00at /app/.next/server/pages/index.js:3920:81 {
2024-10-25 21:52:08.276345+00:00errno: -13,
2024-10-25 21:52:08.276356+00:00syscall: 'copyfile',
2024-10-25 21:52:08.276373+00:00code: 'EACCES',
2024-10-25 21:52:08.276387+00:00path: '/app/src/skeleton/settings.yaml',
2024-10-25 21:52:08.276400+00:00dest: '/app/config/settings.yaml'
2024-10-25 21:52:08.276412+00:00}
2024-10-25 21:52:08.980843+00:00Error: EACCES: permission denied, copyfile '/app/src/skeleton/settings.yaml' -> '/app/config/settings.yaml'
2024-10-25 21:52:08.980944+00:00at copyFileSync (node:fs:2982:3)
2024-10-25 21:52:08.980957+00:00at checkAndCopyConfig (/app/.next/server/chunks/1227.js:53:55)
2024-10-25 21:52:08.980968+00:00at init (/app/.next/server/pages/index.js:4837:76)
2024-10-25 21:52:08.980983+00:00at createLogger (/app/.next/server/pages/index.js:4881:5)
2024-10-25 21:52:08.981006+00:00at /app/.next/server/pages/index.js:3920:81 {
2024-10-25 21:52:08.981019+00:00errno: -13,
2024-10-25 21:52:08.981030+00:00syscall: 'copyfile',
2024-10-25 21:52:08.981041+00:00code: 'EACCES',
2024-10-25 21:52:08.981055+00:00path: '/app/src/skeleton/settings.yaml',
2024-10-25 21:52:08.981076+00:00dest: '/app/config/settings.yaml'
2024-10-25 21:52:08.981087+00:00}

[ihatemyisp]

EACCES = permissions problem

I'm assuming you already have your Homepage files in a dataset? You have to have them owned by 1000:1000.

Change the ownership of your dataset (recursively) to 1000:1000 and then remove and rebuild the Homepage app, pointing it at your dataset.

[mda4mda]

Yes, I also had permissions issues with the EE upgrade and that fixed it.

[owennewo-dev]

What are your permission settings for the Homepage Dataset? This is how I have mine configured:

[mda4mda]

I haven't messed with datasets. I'm using docker compose and pointing to the files.

[SavanFlou]

Thank you, but there is no user or group at 1000 in my Truenas config.
Right now the dataset belongs to Apps= 568.

I will try to change and put me as owner.

Edit:
So I did not solve using the app, but I was able to create a Docker through Dockge, and that works, with another dataset that I "own". After a bit of thinking, I think the problem is my dataset was in another dataset grouping all those for the apps, and I did not put me in the permissions of this dataset, which was created as "dataset for apps".

[ihatemyisp]

Yea, you have to do it via the console/CLI and not the UI. The console will let you set whatever owner/group you want, even if they don't actually exist on the host system. The docker container runs internally as 1000:1000 and the app attempts to set those permissions but it fails because it doesn't have permission to change permissions.

I also run Homepage via docker compose and Dockge though it's because I put all my compose files in a git repo.

[lucky13820]

have you figured out how to do this? I'm running into the same issue, and I just can't seem to fix it.

I tried to use docker compose and Dockge to run Homepage, it won't work if I want to use my own dataset. I used chown -R 1000:1000 /mnt/HDDs/Docker/homepage in shell and from SSH, both didn't work. Homepage still throws the same permission error.

[SavanFlou]

As I said, I used Dockge and it worked with a dataset of Truenas.
Here is my code

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    ports:
      - 3000:3000
    volumes:
      - /mnt/***/homepage/config:/app/config # Make sure your local config directory exists
    restart: unless-stopped
networks: {}

I created befor the dataset and I do not recall putting something special in the permissions.

[lucky13820]

Thanks, turns out I just need to create a new dataset and try again. Everything works now.