Support for Maybe Finance docker containers (Web & Worker)

Application Name: Maybe Web | Maybe Worker

Maybe Github Repo: https://github.com/maybe-finance/maybe
My Template Repo: https://github.com/dkeners/unraid-templates

 

Take a look at the template repository readme, I will be adding tips and tricks for running Maybe Finance. Please leave questions/issues in this thread or as an issue in the template repository.

Unraid is not an official environment for this app, please post any questions or issues relating to running Maybe via these templates in this thread and not in the maybe github issues.

Edited May 9, 20251 yr by dkeners
Remove comment

Hi, I set up Maybe following your guide, thanks for providing such detailed instructions BTW, however I can not get onboarding to advance past preferences. A blue progress bar appears at the top of the screen after clicking submit but nothing happens after that.

Any ideas?

One question I did have about the install process is regarding the Redis data path. The container template did not include a path initially so I added it but wasn't sure if /data was the correct container path.

Thanks!

2 hours ago, headtrip0 said:

Hi, I set up Maybe following your guide, thanks for providing such detailed instructions BTW, however I can not get onboarding to advance past preferences. A blue progress bar appears at the top of the screen after clicking submit but nothing happens after that.

Any ideas?

One question I did have about the install process is regarding the Redis data path. The container template did not include a path initially so I added it but wasn't sure if /data was the correct container path.

Thanks!

Update: It randomly worked but I had to refresh the pages a few times and even received a few timeouts (unable to connect) which is not something I have encountered from the webui for any of my other docker containers. I am having this problem frequently as I attempt to navigate around the UI so something seems to be wrong.

I was able to find one issue. It looks at though the Maybe-Web container is disconnecting over and over frequently. This is a small example from my unraid logs. When the Maybe-Web container is turned off these messages stop completely unless I start/stop a container so this is ALL from that one container.

Jun 4 14:51:16 Unraid kernel: eth0: renamed from vethd4ff049

Jun 4 14:51:16 Unraid kernel: br-4a4a323fda54: port 4(vethb269508) entered blocking state

Jun 4 14:51:16 Unraid kernel: br-4a4a323fda54: port 4(vethb269508) entered forwarding state

Jun 4 14:51:44 Unraid kernel: br-4a4a323fda54: port 4(vethb269508) entered disabled state

Jun 4 14:51:44 Unraid kernel: vethd4ff049: renamed from eth0

Jun 4 14:51:45 Unraid kernel: br-4a4a323fda54: port 4(vethb269508) entered disabled state

Jun 4 14:51:45 Unraid kernel: vethb269508 (unregistering): left allmulticast mode

Jun 4 14:51:45 Unraid kernel: vethb269508 (unregistering): left promiscuous mode

Jun 4 14:51:45 Unraid kernel: br-4a4a323fda54: port 4(vethb269508) entered disabled state

Jun 4 14:51:46 Unraid kernel: br-4a4a323fda54: port 4(veth99ee0be) entered blocking state

Jun 4 14:51:46 Unraid kernel: br-4a4a323fda54: port 4(veth99ee0be) entered disabled state

Jun 4 14:51:46 Unraid kernel: veth99ee0be: entered allmulticast mode

Jun 4 14:51:46 Unraid kernel: veth99ee0be: entered promiscuous mode

Jun 4 14:51:48 Unraid kernel: eth0: renamed from veth70fbfbc

Jun 4 14:51:48 Unraid kernel: br-4a4a323fda54: port 4(veth99ee0be) entered blocking state

Jun 4 14:51:48 Unraid kernel: br-4a4a323fda54: port 4(veth99ee0be) entered forwarding state

Jun 4 14:51:56 Unraid kernel: br-4a4a323fda54: port 4(veth99ee0be) entered disabled state

Jun 4 14:51:56 Unraid kernel: veth70fbfbc: renamed from eth0

Jun 4 14:51:57 Unraid kernel: br-4a4a323fda54: port 4(veth99ee0be) entered disabled state

Jun 4 14:51:57 Unraid kernel: veth99ee0be (unregistering): left allmulticast mode

Jun 4 14:51:57 Unraid kernel: veth99ee0be (unregistering): left promiscuous mode

Jun 4 14:51:57 Unraid kernel: br-4a4a323fda54: port 4(veth99ee0be) entered disabled state

Jun 4 14:51:58 Unraid kernel: br-4a4a323fda54: port 4(vethb50d1af) entered blocking state

Jun 4 14:51:58 Unraid kernel: br-4a4a323fda54: port 4(vethb50d1af) entered disabled state

Jun 4 14:51:58 Unraid kernel: vethb50d1af: entered allmulticast mode

Jun 4 14:51:58 Unraid kernel: vethb50d1af: entered promiscuous mode

Jun 4 14:52:01 Unraid kernel: eth0: renamed from veth1f5edad

Jun 4 14:52:01 Unraid kernel: br-4a4a323fda54: port 4(vethb50d1af) entered blocking state

Jun 4 14:52:01 Unraid kernel: br-4a4a323fda54: port 4(vethb50d1af) entered forwarding state

Jun 4 14:52:05 Unraid kernel: br-4a4a323fda54: port 4(vethb50d1af) entered disabled state

Jun 4 14:52:05 Unraid kernel: veth1f5edad: renamed from eth0

Jun 4 14:52:06 Unraid kernel: br-4a4a323fda54: port 4(vethb50d1af) entered disabled state

Jun 4 14:52:06 Unraid kernel: vethb50d1af (unregistering): left allmulticast mode

Jun 4 14:52:06 Unraid kernel: vethb50d1af (unregistering): left promiscuous mode

Jun 4 14:52:06 Unraid kernel: br-4a4a323fda54: port 4(vethb50d1af) entered disabled state

Jun 4 14:52:07 Unraid kernel: br-4a4a323fda54: port 4(vethed2487d) entered blocking state

Jun 4 14:52:07 Unraid kernel: br-4a4a323fda54: port 4(vethed2487d) entered disabled state

Jun 4 14:52:07 Unraid kernel: vethed2487d: entered allmulticast mode

Jun 4 14:52:07 Unraid kernel: vethed2487d: entered promiscuous mode

Jun 4 14:52:10 Unraid kernel: eth0: renamed from veth416ec6e

Jun 4 14:52:10 Unraid kernel: br-4a4a323fda54: port 4(vethed2487d) entered blocking state

Jun 4 14:52:10 Unraid kernel: br-4a4a323fda54: port 4(vethed2487d) entered forwarding state

Edited June 4, 20251 yr by headtrip0
Adding additional detail.

Hey @headtrip0 ,
Sorry it didn't work smoothly! This log tells me that the container itself keeps crashing and restarting. In the container settings, under advanced, you can remove --restart unless-stopped from the extra parameters line, this will clear up this spam from your Unraid logs. You are correct that the container path for Redis is /data .

If you provide the logs from the docker container itself I may be able to help figure out what is causing it to crash repeatedly. If the logs button for the container isn't working you can access specific container logs by running docker logs maybe_web in the Unraid console (maybe_web will be case specific to your name).

I have also heard of Unraid not checking for conflicting ports when one is in a custom network, which leads to similar connectivity issues, please confirm you have no other containers exposing the same port (3000).

@dkeners ,

Thanks for the assist. I spent some time looking through the logs and triple checking my configuration of each container and found 2 errors. I had an incorrect hostname in a Maybe-Worker setting and another in a Maybe-Web setting. After correcting those everything is working really well now. I will spend some time exploring the interface and begin entering my details.

Any tips/trick for using Maybe especially in a self hosted environment?

Have you tried adding tailscale to Maybe yet?

Edited June 5, 20251 yr by headtrip0
added a question

Glad it worked out!

12 hours ago, headtrip0 said:

Any tips/trick for using Maybe especially in a self hosted environment?

Have you tried adding tailscale to Maybe yet?

• I would recommend the discord for maybe, there is a solid community there, as well as the resources page. I personally don't have too many myself.

• I have! Follow one of the Unraid guides to set up tailscale, https://unraid.net/tailscale, and then on another device that is looged into tailscale you should be able to access the container by going to your Unraid tailscale IP (100.xx.xx.xx) and appending the :3000.

First I want to thank you for putting these install templates together!

I am encountering an error that appears as soon as I attempt to load the webpage:

We're sorry, but something went wrong.

In the log for the maybe_web docker it says:

FATAL -- : URI::InvalidURIError (bad URI (is not URI?): "127.0.0.1:6379/1")

I already had redis running on that port and if I turn off the redis docker I get a page telling me I need to configure redis, so I am pretty sure it's connecting to redis. I'm just unsure what that error message means.

Does anyone have any ideas? When I search those error messages I cannot find anything related to Maybe.

EDIT: I ended up having to change the redis url to redis://(Unraid Server IP):6379/1 and switch the Network from maybe-stack to Bridge.

Edited June 10, 20251 yr by wizenthorne

Hi People of unraidia,
I got Maybe_Web running but in the Logs it says SKYLIGHT dont start. Is it right that this has something to do with Redis?
After following the provided guide (thanks alot for it) Maybe wont start correctly. has someone an idea?
Logs below:

logs.txt

Edited June 24, 20251 yr by exputesco

Hey @exputesco , I looked over your logs and think the issue is with your Redis URI, based on these three lines here:

I, [2025-06-24T13:45:52.704365 #1]  INFO -- : Processing by PagesController#redis_configuration_error as HTML
F, [2025-06-24T13:45:52.712384 #1] FATAL -- : URI::InvalidURIError (bad URI (is not URI?): "192.168.188.158:6377")
- Gracefully stopping, waiting for requests to finish

The issue with redis may (I suspect) be one of the two things below:
- One thing that catches my attention is the port for redis is 6377 in the URI you have configured, while the default port for redis is often 6379.
- The second item would be the IP of redis docker container. Make sure that all your containers that want to talk to each other are on the same network, be it all on default bridge, or a custom bridge.

If using the maybe_net bridge this should be configured as: redis://maybe_redis:6379/1

If using the default unraid network then it could be configured: redis://{YOUR-UNRAID-IP}:6379/1

Skylight is a service that Maybe uses for their hosted platform to monitor performance, so in a self-hosted setup it is OK and expected for this to not start.

Hi @dkeners ,

thank you for responding!

I tried a few configs on the network side, but you are right the container comes the farest with redis://maybe_redis:3677/1 but the WebUI shows:

"Redis Configuration Required

Your self-hosted Maybe installation needs Redis to be properly configured."

At leased its not crahsing^^

The port is changed becaus redis is already running for differend apps. I thing you have to install a Redis instance for every app that needs one right? I thought changing ports is no problem as far as they are equal?

The Worker is charshing no matter what i enter in the template.. could that be the problem?

@exputesco of course! Sorry for the delay in replies; busy couple of days…

You are correct that changing any port is ok as long as you take care to match it everywhere needed. (And that it doesn’t conflict with any other ports you have set up).

Setting up 1 redis per server is not completely necessary, and they can be shared between apps assuming they run on the same version of redis. HOWEVER, I like running 1 redis per app so that I do not have to worry about my other apps needing a version change or having any unintended overlap.

I’m just confirming that you created the custom docker network, and inside of it you have your Web, Worker, Redis and Postgres containers? Also, did you update the redis URI inside of the worker container settings? That should match exactly what you have in the web settings.

Let me know if any of these help! If there are still errors with the worker some logs may be helpful, or a description of where each of the 4 apps are located (in default network, custom bridge, or other custom network, ports. Do Not, Do Not share sensitive IP data). I have attached a photo of my docker tab that shows what ports and network each container is on.

maybe_db_LOG.txt maybe_redis_LOG.txt Maybe_Worker_LOG.txt Maybe_Web_LOG.txt

Hi and sorry for taking so much time to answer! You know life do things.. good things but cant find time..

I just checked the logs again for all four parts of maybe and have a sreenshot of these from the docker tab.
I've checked the Maybe docu to look for something but I guess I dont know enought to understand what those logs wnat to say me^^

It feels like im throwing my homework to you to get it done but I appreciate you to show and teach me something so i can solve more and more my self!

Howdy, I've got this working well except for Enable Maybe AI. I've set my OPENAI_ACCESS_TOKEN and entered the correct value but the app still complains about needing this key in order to make use of AI. Any help would be much appreciated.

@exputesco No worries! Hopefully we can solve this and then it won't be a problem for the next person! :)

I looked through your logs and your database and redis look to be running perfectly!
It does look like the issue is still with how your Maybe_Web and Maybe_Worker are reaching Redis, I am finding this in the Maybe_Worker logs Connection refused - connect(2) for 172.19.0.4:6377 (redis://maybe_redis:6377/1) .

I may have been mistaken about how local dns works in custom docker networks... 😅. I think that Maybe is not seeing your custom defined port at all, only docker containers outside of the network see the custom number. I have made a small diagram about how this works, happy to clarify if it doesn't make sense, I will add to the guide if helpful! (Appflowy is used as an example app that would have another redis container.)

Setting your Redis port in the Maybe_Web and _Worker containers to the 6379 value in the column should fix your issues. Apply in both containers and see if you get past the redis screen of the app.

If the app is now working, and you don't need access to the DB or Redis in the bridge network, you can remove the port like in the config below.

Edited July 1, 20251 yr by dkeners

Ahh ok. so it was my understanding of the custom networks! Thanks allot it seems to work!!

For the guide is maybe a note that subnets/customnetworks are that way, or im one of the few not knowing that^^

Thank you again that will help my selfhosting journey for ever!! :)

Thanks for developing this! I've been trying to get this to work with Unraid's tailscale integration, but keep getting the error:
Executing Unraid Docker Hook for Tailscale

ERROR: No root privileges!

ERROR: Unraid Docker Hook script throw an error!

Starting container without Tailscale!

Starting container...

I've been able to get it to integrate with TSDproxy but it'd be amazing to just have the native tailscale integration work.

Thanks again

Hey @runza_gaming , I found some info on this error in another thread. It seems like something that I could maybe improve on the template side! I have to provide some major updates to this template as Maybe was sunset by the old devs, however a compatible branch is still under active development. I will update again in this channel when I make those changes to the template, in the meantime that thread has some helpful ways to get past this error! (Except running in privileged mode, avoid that whenever possible)