theiam79

Running in to an issue with valheim - when I stop/restart the container, it renames the current {world}.db file to {world}.db.backup and then generates a new db file that is significantly smaller than the existing one. When the server does load with that db, the world is reset back to normal. Any idea what's causing this?

Thanks. I ended up getting it working, but was mostly curious how you persisted across reboots.

Interested in doing this, as it seems like its a relatively easy to maintain solution. Would you mind sharing your steps? I'm fairly new to some of the advanced features of Docker.

Keep up the good work, been rock solid for the last 4 years.

Did you ever get anywhere with this? I've been playing with it some but haven't been able to get it working

I had DDNS handled through my router configured with Google Domains so I'm not sure what the deal is, but I'll get back to it tomorrow.

Yep, switched to that one haha. Probably wont be able to work on it til later, probably need to switch to ddclient too since I'm still seeing that error

I'll mess with Nginx for the time being. It may be awhile though, using aptalca's container and it's throwing an NXDOMAIN error at me and failing first time setup

Yeah, it was. As far as setting this up as nextcloud.server.com, would changing the servername/alias, redirect, and moving the proxypass out of the location tag mess with everything else that is set up?

I can go back through your guide and set it up that way, I was just using this method for continuity with everything else.

Here is what shows in the nginx error log inside nextcloud: 2016/11/18 12:40:17 [error] 304#0: *52 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.17.0.1, server: _, request: "GET /index.php/apps/theming/styles?v=0 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.121:444" 2016/11/18 12:40:17 [error] 304#0: *53 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.17.0.1, server: _, request: "GET /index.php/apps/theming/js/theming?v=0 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.121:444" 2016/11/18 12:41:27 [error] 304#0: *56 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.17.0.1, server: _, request: "POST /index.php/login HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.121:444" As for switching from Apache, I may give that a go tonight, but if I can get it to work in Apache I'd prefer that.

Same thing, slow to load login page and then a gateway timeout on login attempt. As for the resource thought, that was just me rambling about things I thought it might have been when I was going through it haha.

I am using https. I don't think it's a resource issue, as Unraid only shows a peak load of like 15% and available RAM. Like I said I nuked it and started over and that didn't change anything. I've also cleared the browser cache and what not, as the only time I got it to login successfully was in an Incognito window, but even that failed multiple times.

That should've been attached to the last post but here it is again. config.txt

Here you go. Everything else is working normally, so I'm not sure what's up, but appreciate any help. config.txt default.txt