xavierh Posted January 20, 2023 Share Posted January 20, 2023 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 Quote Link to comment
kri kri Posted January 20, 2023 Share Posted January 20, 2023 Thanks for adding this. Should there be an appdata folder for this? Quote Link to comment
Agent531C Posted January 20, 2023 Share Posted January 20, 2023 Is this any different than the existing actual-server container? Quote Link to comment
xavierh Posted February 4, 2023 Author Share Posted February 4, 2023 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. Quote Link to comment
xavierh Posted February 4, 2023 Author Share Posted February 4, 2023 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. Quote Link to comment
BoKKeR Posted April 14, 2023 Share Posted April 14, 2023 Is there a special way to run this? I try accessing 5006 and get Quote Link to comment
xavierh Posted April 16, 2023 Author Share Posted April 16, 2023 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. 1 Quote Link to comment
Camilo Posted October 6, 2023 Share Posted October 6, 2023 (edited) Hi! Anybody having this issue after the latest update? Solved! I had to clear cache and cookies. Edited October 6, 2023 by Camilo Quote Link to comment
pumavision Posted November 5, 2023 Share Posted November 5, 2023 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? Quote Link to comment
pumavision Posted November 5, 2023 Share Posted November 5, 2023 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. Quote Link to comment
xavierh Posted November 6, 2023 Author Share Posted November 6, 2023 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. Quote Link to comment
Zata Posted November 6, 2023 Share Posted November 6, 2023 Could this template be updated to use actualbudget/actual-server instead of jlongster/actual-server? Seems the official one is updated more frequently. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.