[SUPPORT] xavierh / actual-server

[xavierh]

Support thread for unraid docker template.

 

This docker image was already created by the developer. I've just created the unraid template for it using jlongster/actual-server:latest.

 

GitHub: https://github.com/actualbudget/actual
DockerHub: https://hub.docker.com/r/jlongster/actual-server
My Repository: https://github.com/xavier-hernandez/unraid-templates

[kri kri]

Thanks for adding this. Should there be an appdata folder for this? 

[Agent531C]

Is this any different than the existing actual-server container?

[xavierh]

On 1/20/2023 at 8:07 AM, kri kri said:

Thanks for adding this. Should there be an appdata folder for this? 

 

It should be part of the template, you can add the path yourself. I think its advised not to pre-populate that.

[xavierh]

On 1/20/2023 at 11:13 AM, Agent531C said:

Is this any different than the existing actual-server container?

 

This "app" is created off the official docker image. The other one is like 7 months old; I noticed when I tried using a feature that wasn't available in that version.

[BoKKeR]

Is there a special way to run this? I try accessing 5006 and get 

 

[xavierh]

On 4/14/2023 at 11:53 AM, BoKKeR said:

Is there a special way to run this? I try accessing 5006 and get 

 

 

If you click on the troubleshooting documentation link it'll explain it a bit. Basically you need HTTPS set up. However, you can click on the Advanced options link and you can get around but just make sure you don't have 2 tabs open at the same time.

[Camilo]

Hi! Anybody having this issue after the latest update?

Solved! I had to clear cache and cookies.

Edited October 6, 2023 by Camilo

[pumavision]

Has anyone been able to get this container accessible through reverse proxy?

I don't know what the problem is- I've configured it in Nginx Proxy Manager the same way as many others, which all work. I'm using a wildcard certificate and configured the CNAME record the same way as my other subdomains. However, when I try to access the proxied version of Actual, I get an Error 526: Invalid SSL Certificate.

 

Anyone else run into this?

[pumavision]

Following up to my previous post: I have tried deleting my existing wildcard certificate and creating a new one. Again, all my other subdomains are working, but I can't get this one to work. Same Error 526. I also tried using my server IP instead of the container name in the "Forward Hostname / IP" field in Nginx Proxy Manager, with no success. And yes, the ActualServer container is running in the correct Docker network.

[xavierh]

I don't even see my app in the apps store anymore. Not sure why. I would assume though you have a problem with the internal SSL and it causing an error via proxying.

[Zata]

Could this template be updated to use actualbudget/actual-server instead of jlongster/actual-server? Seems the official one is updated more frequently.

[bubiman]

I don`t know why but the documentation on how to set up HTTPS was not working for me. If anyone else is runing into this problem, here is what I did:

 

1) I changed the mounted paths in the unraid docker configuration. I had to delete the two pathes for server und user and added just one data path
<

 

2) Under advanced view I changed the WebUi URL to HTTPS

 

3) Following this documentation https://actualbudget.org/docs/config/https/ I created the selfhost.key and selfhost.crt with the given openssl command, I created the config.json with the listed lines and put all three files into the mounted /data path /mnt/user/appdata/actual-server/

 

After restarting actaul it is now working with ssl but I have to confirm the not trusted self created ssl key

Edited September 22 by bubiman
typo