Phredwerd

Is there a way to disable having to sign in to see all the recipes? Mealie 0.5.6 allowed this and I could easily share mealie with people without needing for a login.

After a bit of fiddling, I did get this to work and mealie V1 now has my recipes. Thanks!

RIght sorry, I wrote that quite late and was tired so I missed a detail. As I mentioned, I was getting that bad gateway error with 0.5.6 so I uninstalled it thinking it had to do with the reverse proxy I have setup to access it. I re-installed it via the container templates list but it still wouldn't work even when accessing it without the reverse proxy so I deleted it from my templates and went to find another version that would work but I can't find any. In the link above: https://nightly.mealie.io/documentation/getting-started/migrating-to-mealie-v1/ It mentions needing to be able to access my old mealie install to export the data but the issue is, I can't! So I need to find a working 0.5.6 build I can install to export the data.

I was running 0.5.6 but recently I started getting Bad Gateway 502 when I tried loading it up. I have all my recipes there and I need a way to export those so that I can migrate to 1.0. I can't seem to find v0.5.6 on the Unraid App store anymore. What are my options here? I really don't want to loose all those recipes!

Hi there, I've set this docker up in my server and configured it to use Digital Ocean following this template: https://github.com/qdm12/ddns-updater/blob/master/docs/digitalocean.md The config.json file: { "settings": [ { "provider": "digitalocean", "domain": "mydomain.ca", "host": "@", "token": "<my token>", "ip_version": "ipv4" } ] } Docker starts fine and the WebUI output shows this: But when I got look at my DNS Panel in Digital Ocean, no A record gets set. Even 12 hours later. Here is the contents from updates.json: { "records": [ { "domain": "mydomain.ca", "host": "@", "ips": [ { "ip": "<my ip>", "time": "2024-01-25T23:43:37.728524444-05:00" }, { "ip": "<my ip>", "time": "2024-01-26T00:21:35.437335624-05:00" } ] } ] } Everything looks right. Did I miss something? Thanks!

Is there one in particular you can recommend that has worked for you?

Is there anyway to change how the USB adaptor in this device presents the ID? That's really annoying that it does that.

Yeeahh I was thinking this may have been the culprit. Both drives involved in this issue are encased in an Orico brand hard drive enclosure. This one in particular: https://www.orico.com.cn/product/detail/397.html

It doesn't matter which USB port I plug either drive into, they both present with the same device ID. Even if I change the mount point this won't work. So drive one's mount point is Video and the other drive is Space. If I plug in the first drive, it will mount as Video but if I then plug in the second drive whilst the first is also plugged in, Video disappears and Space takes it's place. They are vastly different drives too! One is a 500GB Toshiba I lifted out of on an old mac book and the other a 1GB Hitachi. It's really bizarre.

I've got a bit of an odd scenario. I've somehow got two separate USB drives that I plug in to do backups with that both have the same disk identification numbers. How is that even possible and how can I change the ID of one of the drives?

Ok it seems that the Nebula theme (installed via the Customizer plugin) was causing this issue as well as this error: Warning: filemtime(): stat failed for /var/www/app/assets/css/app.min.css in /var/www/app/app/Helper/AssetHelper.php on line 41 Showing up at the top of any page you were on. I guess it must be outdated? Too bad. I liked that theme.

Is there a way to revert the sub-task organization back to how it used to be as opposed to the way it's setup now with stacking? I preferred it with the "X" moving icon, the drop down and the name of the task be all in the same line.

Looks it was. I'm not seeing it anymore in my logs.

This appears at the top of any page I'm on Warning: filemtime(): stat failed for /var/www/app/assets/css/app.min.css in /var/www/app/app/Helper/AssetHelper.php on line 41 I tried clearing the sessions table, stopping and restarting the kanban app, docker itself and even re-installed kanban but that didn't seem to work so not sure what else can be done?

What strikes me odd as that setup persisted for a good 18 months through multiple parity checks. Then the one I ran in May one showed those errors. I ran another check with corrections enabled and it resulted in 0 errors but this still persists. Also, I have my unraid setup such that it sends me a telegram every morning at 12:20 AM and it constantly shows up as FAIL because of this. Kind of annoying more than anything at this point.