• Posts

  • Joined

  • Last visited

Everything posted by Froberg

  1. You're on the linuxserver one, then?
  2. Works fine without, tried that first, but I figured it should be there since it's explicitly mentioned in the OP?
  3. Renamed to lower-case - postargs: docker exec -u 0 nxtcloud /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars' No joy, container won't load. log says: / 194: exec: docker: not found
  4. yeah it's the post-args, tried removing some stuff and it won't behave. If I remove all the post-args the container launches. I'll try and rename it lower case. Cheers.
  5. Trying to use this to replace a b0rked LinuxServer version, and this was recommended to me. I already have a nextcloud, currently stopped, but I'm not deleting it yet, so I wanted to add yours as "NXTCloud" and changed the folder mappings appropriately, and added the variables and parameters you mentioned, even added a port number for bridge mode. It doesn't want to launch however. Removing container: NXTCloud Successfully removed container 'NXTCloud' Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='NXTCloud' --net='bridge' -e TZ="Europe/Paris" -e HOST_OS="Unraid" -p '8666:80/tcp' -v '/mnt/user/appdata/nxtcloud/':'/var/www/html':'rw' -v '/mnt/user/appdata/nxtcloud/apps':'/var/www/html/custom_apps':'rw' -v '/mnt/user/appdata/nxtcloud/config':'/var/www/html/config':'rw' -v '/mnt/user/appdata/nxtcloud/data':'/var/www/html/data':'rw' -v '/mnt/user/Share/':'/mnt/Share':'rw' --memory=2G --user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0 'nextcloud:latest' PostArgs: && docker exec -u 0 nxtcloud /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars' 2c3b5dfa03141bda7dbd795480db77ec70845af59c511b1ae910008bded9e6b8 Error: No such container: nxtcloud The command failed. It's sad if I'm too blind to do monkey see monkey do, but I'm stumped, really.
  6. It's already using MariaDB. I had a problem with my cache drive, everything went down, turns out it was the database, but I hadn't suspected that before fiddling with NPM first, as that had just been updated and I noticed things not working post-updating that, rather than when MariaDB updated. So not sure what exactly happened, but Nextcloud was working perfectly with the config it had. I have to assume that maybe something got corrupted, despite its services being functional. I'll have a look at the Knex-container as you recommended. I've gotten this stuff to work before, I just ran against a wall trying to debug this and, well, finding a clue when you're frustrated isn't easy. I really appreciate you taking the time, thank you so much!
  7. You are correct! When changed to http in NPM, the wordpress install is now accessible. That at least means that NPM works. So either my settings for nextcloud are off, just as they were with the wordpress install, or I guess nextcloud is just broken.. although it's updateable via command line and everything appears to function fine. Unless you can see anything obviously wrong, I think I'll just have to scrap the nextcloud and start over.... I do wonder what on earth has gone wrong though.
  8. The wordpress test-site works via local logon, if that's what you wanted to verify? 🙂 Since they suffer from the same fault I think it serves the purpose for testing?
  9. Config has been set to disallow local logon, so connection gets refused. Still the same result using 9444 instead of 444.
  10. 444 is nextcloud. 8083 is the test-wordpress. # curl curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to Using linuxserver nextcloud container.
  11. As nothing has been typed, both NPM and the Nextcloud container are in bridge mode, I don't see how I could input anything manually. The nextcloud container should forward all http requests to https. (As should NPM, by the way.) Here's doing it to the root IP: # curl <html> <head><title>302 Found</title></head> <body> <center><h1>302 Found</h1></center> <hr><center>nginx</center> </body> </html> # curl curl: (60) SSL: no alternative certificate subject name matches target host name '' More details here: curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. Here's connecting to the wordpress container that I set up to test - and the nextcloud docker respectively on both http and https: # curl curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number # curl # curl curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to # sh: 13: not found But url's from the outside result in bad gateway though: 502 Bad Gateway openresty I'm sure I'm just missing something obvious but I've tried so many different configs now that I've lost count trying to get this working again.. and it HAS been working previously.
  12. I tried that for my issue; # curl curl: (3) Failed to convert to ACE; could not convert string to UTF-8 # curl curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to Any ideas on what's going on here?
  13. Just to sanity-check I changed both containers to br0 and gave them dedicated IP's. Nothing worked. Now changed both back to bridge and I'm getting bad gateway. I don't see from your table how that should be the expected result. I tried booting up a wordpress container and that also gets bad gateway.
  14. Okay I give up. I've had NPM working for ages now, but suddenly I'm having issues. I've been changing networks and setup so much that it's laughable at this point and I'm probably only making myself confused at the moment. NPM > NextCloud is the goal. Current setup: Current forwarding rules: Using a random domain to test I get a refusal because HSTS is enabled, so presumably NPM is getting the traffic. I tried using NPM on bridge instead, but that resulted in Bad Gateway. I tried setting up a wordpress container to see if my Nextcloud install was b0rked - but that can't be reached, either. Clearly it's some simple mistake doing all this. As mentioned I've tried various config changes and I even tried putting both NextCloud & NPM on the same network to no avail. Again I probably screwed something up even worse by just trying a slew of different things.. I'm fairly sure I didn't use to have NPM on a dedicated IP either.. but here we are. Please advise as I'm sure it's simple and I've just gone and FUBAR'ed it. Been trying to bring it back after some DB corruption due to a MariaDB update erroneously made me think my old NPM setup was the cause and I rebuilt it.. clearly not well enough. So it's been.. a while.. now.
  15. I'm sure there can be a myriad of other factors at play.. just figured since I've done nothing to change the container, other than adding a few more folder-mappings, that it might happen to others, too. After removing 600+ seeding torrents and restarting the container, it immediately re-added them all again. So I had to remove the .torrent files manually in the appdata directory too. Here's hoping it doesn't happen again. It's been rock solid otherwise.
  16. Fair warning for anyone who manages to read this before updating. My transmission update today resulted in the nulling of all download locations, immediately triggering a few TB's of downloads before I caught it. Not sure what went wrong, all my settings seem to be there, but the "move to x folder" history was lost and everything was reset to the standard downloads folder.
  17. Agreed.. been unsuccesful thus far in reviving it.. 502 Bad Gateway. The DB is up, as I could upgrade it through console, which I assume required DB connectivity.. so I'm a bit stumped atm.
  18. "Fix" worked for me, at least I can access the db through phpmyadmin again. Nextcloud is still b0rked though. Have to get some rest, but specifically the fix that worked in my case: And then switching to :latest.
  19. Never happened yet. Even replaced my dual 250G drives with dual 1TB drives just to eliminate that the drives themselves were faulty. Never at risk of running out of space on cache now, not even with large data ingress.
  20. Hi all All issues I've had running UnRaid, without fail, for the last few years, has been down to the RAID1 cache in my system. I am, once again, moving everything off the cache, suffering the Docker downtime because of it, and reformatting. It's taken all day so far. (Plex has soooo many files..) I am pondering splitting up my two 1TB drives and simply using one as an "unassigned device" as a backup location or even a hotswap if the primary drive fails. I have yet to have an SSD die on me though, so it's doubtful anything should happen.. I've just had so many issues by now and it's frustrating to keep restarting and spending days of time relocating files in the process. Any thoughts on this? Am I alone in suffering these corruption and filesystem problems with the RAID1 cache under BTFRS?
  21. I just set up additional logging and diagnostics in Tips and Tweak CA so if it happens again I should have more to go on.
  22. The cache is barely a month in to operation with these new drives so it's extremely odd for me. I hadn't noticed any corruption warnings though. I'll follow your guide and set up the notifications to be alerted. So you reckon' this is the cause of my problems?
  23. Did a scrub yesterday when ChatNoir mentioned it, no errors fixed or detected.
  24. Yeah that cache is irksome to say the least. I rebuilt it because it kept throwing errors and causing problems - ON NEW DRIVES - and still it persists. That's just.. hurtful at this stage. But yes, I strongly suspect BTFRS and the cache/Docker to be at the root of much of this. Side note: Plex is now fixed by recovering an earlier backup DB.
  25. Oh, the reason I suspect Docker is because when Plex broke earlier in the day I logged on to My Servers from work and checked the server remotely. Everything seemed fine, but I couldn't load the docker page - at all. Then when I tried to reboot it via the interface it would just hang and not do anything, maybe from failing to halt the docker service. Log didn't really illuminate me. Ended up phoning the wife for a hard-reset which resolved it, but left Plex with the corrupt DB. Which I still haven't addressed as yet in case troubleshooting illuminates something that might fix it.