CHBMB

Also, the problem seems to be isolated to sqlite databases. Sent from my Mi A1 using Tapatalk

It's not our issue to fix and by design appdata is meant to reside on cache. It makes far more sense to have appdata localised to one disk anyway and no real sense to write it directly to the array as that slows things down considerably and causes issues. Also, protected array is not the same as backups, appdata should be backed up, not relying on parity protection. Sent from my Mi A1 using Tapatalk

Ignore it, discussed elsewhere in this thread and on GitHub. Harmless error if you're not using Lua and is a problem with the upstream project. Sent from my Mi A1 using Tapatalk

Run this to check: docker exec -it mariadb bash msyql -uroot -p If that works then paste a screenshot of the settings before you submit them on the Nextcloud setup page

Looks like the root password for your database is wrong

Fix has been merged, so if you try again it should work now.

It's OK thanks, I think I've isolated it and have submitted a PR to fix it.

Actually I'm already looking at it, I *think* it's a problem with a python package.

If you don't provide us with the information, we can't help.

@monogoat Post your docker run command, it's wrong, or your router config is wrong.

People are using it, but a word of caution, it's not to be considered stable and it's unsupported, backup before you try it and any problems, you're on your own.

I must admit I agree, I suspect the actual risk of me running a vulnerable home server is infinitismally small, however that isn't a criticism of LT, as I understand 110% they are kind of "duty-bound" to patch this stuff.

It's only a minor kernel bump from our current version 4.19.41 to the fixed version of 4.19.43 I wouldn't be suprised if @limetech release a v6.7.1 at some point. Still need the paired Intel microcode though....

I suspect, although, I'm not 100% sure as I'm not a networking guy that the dual router setup is causing some issues, essentially you have a double NAT http://www.practicallynetworked.com/networking/fixing_double_nat.htm

For stability I'd say go with LTS, you can always upgrade at a later date. Sent from my Mi A1 using Tapatalk

Struggling to get my head around why you have two routers and I can't visualise your setup at all.

Here's the flow Router (443) - External Docker Port (1443) - Internal Docker Port (443) Router (80) - External Docker Port (180) - Internal Docker Port (80) Hence why you forward 443 on router to 1443 and port 80 on the router to 180 Sent from my Mi A1 using Tapatalk

No Sent from my Mi A1 using Tapatalk

Yes to the appropriate ports on LetsEncrypt Sent from my Mi A1 using Tapatalk

Yeah and you're forwarding the wrong ports, that's what I'm trying to tell you. Sent from my Mi A1 using Tapatalk

No, I mean on your router. Sent from my Mi A1 using Tapatalk

You need to forward 443 to 1443 and 80 to 180 Sent from my Mi A1 using Tapatalk

Have you got your domain provider configured appropriately with a names and cnames etc and forwarding ports 80 to 180 and 443 to 1443 on your router. Some screenshots might be helpful. Sent from my Mi A1 using Tapatalk

@TheLamer & @sparklyballs both found the issue within a minute of each other. Basically there's a directory missing in Grocy itself, so ideally the fix would come from upstream, however we're implementing a workaround for now.

OK, so haven't worked out the issue yet, however with FRESH APPDATA a pull from linuxserver/grocy:v2.3.0-ls16 Regardless I've opened an issue on our Github to track things, and it's also a good example of the sort of info you should be posting as a minimum, (docker run command and docker logs.) @Lee B even added on that and posted some Nginx logs. Reports that just say it doesn't work are not terribly useful.