CD99

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by CD99

  1. @Squidit worked! Specifically, https://<server_ip>:<https_port> since my ssl port was different from 443. Still not sure why the GUI didn't open when trying to launch in safe mode locally, but I can now access the webgui normally
  2. Mine is on 6.9.2, and this part of the guide has no actual steps for what to do if you are not on 6.10. To reiterate, the GUI is not accessible via web or on the server directly. The GUI also does not load even when trying safemode. I can however get to the command line Steps I've tried: 1) Loading safemode 2) Removing all drives and just booting normally, safemode, etc 3) Copying all contents to a new thumbdrive and running that This issue arose when I was away, so I can't say what happened. I do have auto update for docker containers set, but if this does mess it up, I could usually use safemode to disable / remove the offending docker / app. Unfortunately, this does not work.
  3. Just replying to keep this thread alive. The GUI for Unraid broke without any warning and now I can't seem to access the GUI directly or from the web.. The diagnostics is absolutely unhelpful in providing any clue either...
  4. Thanks for the reply - I've not done anything else since my second post (not sure what else I could try, hoping someone can point me in the right direction)
  5. Hi all, attaching the full diagnostics in case it helps figure the problem out. Since my above post, I've tried copying the files over to a new thumbdrive but its still causing the same issue nas-diagnostics-20220504-1529.zip
  6. @LoyalScotsmancan you tell me what steps you took to restore to a new USB drive? I don't want to lose settings to my dockers(especially the ones with file backups)
  7. Hey all, I can't access my unraid server GUI anymore, from the web or directly. Initially i thought it was a drive issue (as I saw errors). I've now tried removing all the drives, and booting in safe mode. Neither of these helps. I'm not sure what changed, as I had been away for some months and the OS stopped responding to webgui when I was away (but the docker services were still running). All I get when I try to access it is (last ~50 lines of the diagnostics syslog) : Happy to include any other files from the diagnostics if needed. Thank you everyone for the assistance Edit: Its on Unraid 6.9.2 if that helps
  8. The best thing about unraid, in my view, is that its relatively easy to set up and then automate to run. Its one of the only non-windows system I haven't actually broken from trying to change settings, etc. I remember my last attempt at setting up my pfsense box fucked up to the extent that I gave up and reinstalled it. I'm happy beyond my initial trial and error my UnRaid system has been going strong. As for something I'd like to see - it would be to have backup functionalities in-built to the system, such that we can back up the whole system to another server / cloud provider.
  9. I've now done this step over 4 times over the past 30 days and somehow its failed. I've tinkered with the settings as well as tried restarting from scratch (deleting all the docker images and saved files) As for Maria DB, i just used linuxserver's docker with the settings advised(as per spaceinvaderone's tutorial). Since I had not put any data important in it - it wasn't a loss other than having to follow the step one by one again. Nextcloud also runs perfectly on the local server as long as I use the local network on local IP. Letsencrypt meanwhile validates the domains correctly as indicated by the logs of the docker. So somewhere between letsencrypt and the nextcloud docker something falters. I'm curious if anyone had to do the settings differently? I did try to follow Linuxserver's tutorial but it felt too technical for me, especially as there are some parts that are not as clear or doesn;t feel step by step like Spaceinvaderone's tutorial The only things I can think of that i did differently is did differently is edit the configurations using CA Config Editor (instead of a text editor) and use Cloudfare as the DNS
  10. I have so far tried redoing the steps multiple times, and deleting all the dockers and redoing it again. Definitely did not fix it
  11. Hi all, not sure if this is the right place to raise this - but after trying many things I have to ask for help on this. I have followed Spaceinvaderone's tutorial to set up Nextcloud and Letsencrypt (linuxserver's dockers). Nextcloud now works on my LAN but I cant get it to work with a domain or letsencrypt. Letsencrypt correctly validates my domain but for some reason, somewhere between that and Nextcloud, the forwarding doesnt work. My domain is with Namecheap, and the DNS is with Cloudfare. I've tried setting this to directly connect via A record and CName (via duckdns) but each time, the domain fails to resolve at the server. I have port forwarding set correctly for letsencrypt on my router. As per Spaceinvaderone's tutorial, i have changed the network of the 2 dockers to proxynet (Maria DB left on bridge), changed the settings on letsencrypt & nextcloud via CA config editor & renamed the file to .conf for the former. Can anyone help and let me know what I am missing /mnt/user/appdata/letsencrypt/nginx/proxy-confs/nextcloud.subdomain.conf server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud nextcloud; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:443; } } ---> renamed to nextcloud.subdomain.conf /mnt/user/appdata/nextcloud/www/nextcloud/config/config.php array ( 0 => '10.0.0.100:444', 1 => 'nextcloud.*mydomain*.com', ), 'dbtype' => 'mysql', 'version' => '15.0.2.0', 'trusted_proxies' => ['letsencrypt'], 'overwrite.cli.url' => 'https://nextcloud.*mydomain*.com', 'overwritehost' => 'nextcloud.*mydomain*.com', 'overwriteprotocol' => 'https', Note: Spaceinvaderone's tutorial does not show the need to add 'trusted_proxies' => ['letsencrypt'], but adding or leaving out this line does not make a difference