storm123

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About storm123

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed
  1. Thank you for all your help aptalca. I made the change and it didn't work but after some digging I found that it turns out my nextcloud_works docker was broken. I've re-built it and it's all working perfectly now. Much appreciated.
  2. Hi, Confs for letsencyrpt attached. Error log makes mention of "[error] 685#685: *996 no host in upstream ":443", client: xxx.xxx.xxx.xxx, server: nextcloudwork.*," Thank you for helping so far nextcloud.subdomain.conf nextcloudwork.subdomain.conf
  3. Thanks mate. Gave it a go. I now get a connection but it goes to a 500 internal server error. Any logs I can share to help track down the final step?
  4. Hi guys. Thank you for the container. I've recently re-set this container up. It's mostly working perfectly. I am running two nextcloud containers - one for personal and one for work. Reverse proxy works perfectly for the home one. Reverse proxy for the work container doesn't seem to work for me - it just re-directs to the home container. Home container is called "nextcloud" and mapped to nextcloud.XXX Work container is called "nextcloud_works" and mapped to nextcloudwork.XXX. Both being run as sub-domain reverse proxies. Attached are the reverse proxy configs
  5. Thanks for this. Just tried to install and couldn't see an option to set port or config location. There is instead a repeat of the option to set permissions. See attached. Thanks.
  6. Thank you for all the input guys. Sorry for the delay in getting back. Work and life has been so busy so just dealing with the issue this weekend. I ran the fix-fixable option on that disk. I then ran the -check option again and found a couple of more errors. I then ran the rebuild-tree option. Again ran the -check and more errors. I was basically in a loop. In the meantime, I was preclearing another 6TB disk. This kept failing in that the server would just lock up (no network/keyboard unresponsive etc.) and eventually I worked out one of the RAM sticks had errors. Using Memtest I iden
  7. Thank you Johnnie. I've done as instructed and it doesn't look good. I think I'll replace the drive and then try and work on the issues. I may even have some warranty. Should I just put a new drive in, pre-clear and then let it rebuild from parity?
  8. Hi all, Bit of a panic. My array stopped and now is sort of back on line. Biggest problem is that disk 13 is now reporting as unmounted and the main page of the web gui is giving me the option to format it. I don't want to do this as there's quite a bit of data on it. I've done some searching for similar errors and pulled the diagnostic zip file (see attached). I've not done anything else. In fact, I've just disabled the mover from kicking in shortly. Any help on next steps would be appreciated. Thanks, tower-diagnostics-20161231-1844.zip
  9. Any chance anyone can help? There seems to be some more telling issues in the subsonic_sh.log file created by the container. See attached. Thanks. 1069 [main] INFO org.springframework.context.support.ClassPathXmlApplicationContext - Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@5f184fc6: display name [org.springframework.context.support.ClassPathXmlApplicationContext@5f184fc6]; startup date [sat Sep 17 14:33:04 BST 2016]; root of context hierarchy 1833 [main] INFO org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definition
  10. Hi, Hope you can help. I've just tried to install this docker and when running it just doesn't seem to run. The log file is attached. Thanks supervisord_2.log.txt
  11. Right just been tinkering with it and changed the access token but no joy. Also I've tried changing from bridge to host but no effect again. Is there any way to trash the database so it pulls a fresh one? Thanks
  12. Yes. I copied the code from the metabrainz site once I created my account. I've just checked and my account with them is still active. Is it worth me re-generating the access token and seeing if that fixes this? Thanks for speedy responses
  13. Thanks for the quick response. I just checked and my one shows: "Last replication packet received at 2015-06-21 00:03 UTC" Any way to force update the database then? Thanks