Dennys Umbrel App Store ☂️

Added Gitea Mirror.

Added Jotty.

1 Like

Added Spoolman.

Added Shiori.

Added HomeHub.

Added Glass Keep.

Greetings: Thanks for all you are doing. Since the upgrade of my Umbrel Home to 1.5, Overleaf from your store is no longer accessible. I can’t get to it at either of these addresses…

umbrel.local:8063/

umbrel.local:8063/launchpad

… nor by way of TailScale.

Hey @box2321 :waving_hand:

I’ve updated the Overleaf app to version 6.0.0, and this release now requires MongoDB 8.0. Due to the jump to MongoDB 8, your existing Overleaf data can no longer be used, so you’ll need to set things up fresh.

Just a small heads-up: The installation may take a bit of time, and even after the app finishes installing, it can take another minute or two before Overleaf becomes fully accessible. After that, everything should load normally again. If it still doesn’t load right away, try clearing your browser cache.

Let me know if anything still doesn’t come up! :flexed_biceps:

Thanks! I updated, I gave the update a bit of time, and after installing I gave it many minutes, I restarted umbrel, and I cleared out my browser cache. I can’t open Overleaf, with or without adding /launchpad to the URL.

Could you please share your logs so I can take a closer look? :blush:

Thanks for your speedy reply. I ssh’d in and typed the command…

sudo docker logs -f denny-overleaf_app_proxy_1

… I got the following, repeated many times…

Error waiting for port: “The address ‘denny-overleaf_web_1’ cannot be found”
Retrying…

Could you please go to the app, right-click it and choose Troubleshooting, then paste the full output here? That will give me everything I need to check what’s going on. :folded_hands:

Ha! Thanks for telling me how to do it the right way. Log attached.

umbrel_denny-overleaf_2025-11-16_15-07.log (114.6 KB)

Thanks for sharing the full troubleshooting output, that really helps.

The important part is this line from the MongoDB container:

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!

Because your CPU does not support AVX, the mongo container cannot start properly. As a result, Overleaf cannot resolve or connect to mongo, which is why you see repeated errors like:

MongoNetworkError: getaddrinfo ENOTFOUND mongo

Overleaf 6.0.0 uses MongoDB 8, which inherits this AVX requirement, so on that machine the app unfortunately cannot run correctly. To use this version, you would need to run Umbrel on different hardware that supports AVX.

I’m sorry about the trouble here, I could only test the app on my Umbrel Home, and there everything runs fine. If this turns out to be a blocker for more users, I can also consider doing a rollback to an older Overleaf version that doesn’t depend on MongoDB 8.


*Edit: I just looked into this and it turns out that on hardware like the Raspberry Pi 5 the highest MongoDB version that actually runs is MongoDB 4.4. Anything from MongoDB 5 and newer requires CPU features that the Pi does not provide.

I was running Overleaf on my Umbrel Home, and that’s what I’m trying to run it on again.

Device: Umbrel Home (2023)
Model number: U130120
Serial number: U230300604
UmbrelOS: 1.5

… and thank you!

Could you please run the following command on your Umbrel Home to check whether AVX is available?

lscpu | grep -i avx

If AVX is supported, you will see entries like avx or avx2. If nothing shows up, then AVX is not available.
Just let me know what the output looks like.

And if this turns out to be an AVX issue after all, I can also roll the app back to a MongoDB 4.4 compatible version for you. :flexed_biceps:


*Edit: I did some further research and the Umbrel Home uses an Intel N150 from the Alder Lake N series. These CPUs only support SSE4.2 and do not have AVX or AVX2, which explains the issue on your device.

Earlier I mentioned that I had tested the app on my Umbrel Home, but at that time I was still running the older version that did not rely on the newer MongoDB. On my VM, where I usually test my apps, everything worked fine, which is why I didn’t notice the hardware limitation at first. Sorry for the confusion.

Because of this we need to go back to a MongoDB 4.4 compatible version. I will prepare the rollback tomorrow. :flexed_biceps:

Your work is much appreciated! Thank you!

1 Like

Hey @box2321!

Thanks a lot for the support, really appreciate it. :wink:

I’ve rolled the app back to version 4.2.8, so you can give it another try now.

Please remember to clear your browser cache before testing, and please let me know afterwards if everything is working correctly. :flexed_biceps:

I installed the roll-back update, still could not access the app.

Uninstalled, re-installed, and now working correctly! Thanks!

As you said, I did lose all previous work, but fortunately had good exports before that update.

Great to hear it’s all working again! :blush:

I won’t make any further changes to the app for now, so things should stay stable.

I’ve also added a clear note in the release notes to make sure others are aware of the AVX limitation.