mikeyw

Members
  • Posts

    13
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

mikeyw's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. First of all much Thanx to the linuxserver crew for all their hard work on this and all the other dockers and the community at large. I seem to have read myself crazy, there is a lot here in this thread. I just need a little nudge here. All I wanted to do was migrate to the server from the laptop. I have the newer unifi-controller Docker sw loaded on the unraid server. I am having issues when trying to adopt all three devices USG, USW and a AC Pro ap. So what I have done: moved to the LTS docker (why is it still at 5.6.42? and how do I get more current?) . As I understood it, if i selected the 5.9 version that's as far as I could go and never further and with the LTS version it would change with the stable releases and perhaps not the "latest". the controller docker is loaded as a custom:br0 with a IP address 192.168.1.2xx. (its running now, didn't change the default options other than the custom:br0 ip address) In the controller sw, added the Controller Hostname/IP = 192.168.1.1 (the ip of the current UGS) and checked the two boxes "Override inform host with...." and "Make Controller dis..." . Any Help would be greatly appreciated. Michael thanks to all I got it! found the issue pilot error (knew it was just had to find it
  2. I just got letsencrypt working again (long story) but now I have a question: how can I reverse proxy into a container on a different unraid server? I am running multiple servers and now need to use the letsencrypt docker on one of them and reverse proxy into the other server from the outside it kinda looks like this in my head: couchpotato >>> internet >> letsencrypt >>>>> tower 1 (this works fine) | | unifi controller >>> internet >>> >>>>> tower 2 (this one not so good) So I think that I have to somehow connect the two different docker networks( on tower1 and tower2) together so that the correct stuff gets sent to the right place. Tried a few things, but thought I should ask before I make a really big mess here. Took a look at the "docker network" command but couldn't make heads or tails of it I think because I don' t know why?. just need a little direction. ThanX Michael
  3. ThanX @squid for taking the time to look over the log file. That seemed to do it. She didn't go down clean but with an overnight parity ck things seem to be ok now. Not sure how things got so whacked. Michael
  4. I have been getting the title error and another line on the system monitor. I poked around the forum to see if there were any detail about this error, didn't find much. My Unraid had been up for >56 days and then I added some plugins and one 3TB drive that I had precleared a few days earlier, and now this. Didn't think that would cause this much issues. when I finished everything seemed to work. Then when I tried to VPN into the system later, couldn't get in. (was out of town) got back and did a reboot everything seemed ok, left agian and same thing. I have attached the diag log. So now I had to really look into whats going on. BTW: the plug-ins that were added were not overly important, just a few tools. Any guidance or direction would be greatly appreciated. Michael falcon-diagnostics-20170824-1158.zip
  5. @aptalca, thanX for taking a look at my config file. It was the latter of the the solutions. looks like I got it working now. You guys do an awesome job of supporting all these dockers. BTW: I did have to clear the DNS cache in windows too. ThanX again for your hard work. Mikey
  6. All, First of all ThanX!, I have been watching this thread for a while. it has helped me get letsencrypt/nginx running on my (Unraid)server with no real issues till now. I have a working nextcloud confg and I can get to my index page. (which I have modified slightly just so I know its mine) and can get my instance of couch potato running on my server. So now I am having issues with getting a rev proxy to my instance of home-assistant, I followed a thread bite from feb 17 about this but have tried the included config file with no success. So just looking for a little help. So here is what I have also done: copied my working nextcloud file an changed it accordingly. added the necessary stuff to the ha config file. Now what I get is "502 Bad Gateway" when I go to https://subdomain.my_server.com Here is a portion from the error log file: 2017/07/10 14:47:06 [error] 347#347: *1 SSL_do_handshake() failed (SSL: error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number) while SSL handshaking to upstream, client: ISP, server: SUBDOMAIN.myserver.com, request: "GET /favicon.ico HTTP/1.1", upstream: "https://0.0.0.0:port/favicon.ico", host: "SUBDOMAIN.myserver.com", referrer: "https://SUBDOMAIN.myserver.com/" And here is the "site-confs" file:( just the one that seems to be the issue): # This is the virtual host part that allows a subdomain include server { listen 443 ssl; server_name subdomain.my_server.com; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'there is really a key here'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://0.0.0.0:port/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } } hopefully I didn't redact too much info for it to make sense but here it is. I am sure it is something that I missed, so I would appreciate some extra eyes. ThanX in advance Mikey
  7. ThanX to the previous posters. Just found this thread today it answered a lot of questions and the on going issue of filling up the docker image file. I have been constantly increasing it to fit and now it's 50G. I have another question, it looks like the crap left behind is from some old dockers (x9) that have been long gone not sure why it was left behind. Will the above command still remove them by container id since I don't have a name anymore? I will probably try it anyway since it won't kill what's running now. or at least I hope not. FYI: no they don't show up as running containers or as orphaned containers. mike Unraid 6.2.4
  8. mikeyw

    segfault

    Well started with this. Wow got tons of errors. Seems to be up at 4855mb to 5015mb and always seems to be bit 0 and 1 in the test byte that are read or written wrong. So until I fix this first , can't go too much further. Once I fix the memory issues I will check this out. I think that there is a corrupt file. When I went to look at the log file for sickbeard (sickbeard.log) the permissions size etc were all ?'s. I could not delete it or anything else in that dir or the dir itself. BTW: since I was on Unraid 5 and the drives are reisersf should they be changed? Don't want to lose my data (about 6TB) though. check! got it Not sure who is using python but will look into is after solving the mem problem. removed docker; MQtt (don't need it now). Currently the only (non system) installed plugins are "Plex" and "Powerdown" are that are running. I will remember that next time I post. sorry! I did look at it, way more info all wrapped up in a zip file. I could have been helpful. ThanX RobJ I will post status here as I get things repaired. Hopefully it can help someone else too. Mike
  9. Hello All, I seem to be having an issue with my unraid server. The hardware was working flawlessly for the last few years, now since upgrading to Unraid 6 I have been having issues. I have attached a copy of the last syslog. It seems to stay up for about a day or so and then slowly it rots away till I have to reboot. currently I have Plex running as a plugin. SAB, Sickbeard, headphones, MQtt running as dockers. I have had nothing but trouble with couchpotato as a docker so it's loaded as a docker but not running till I can get to it. It really seems to escalate the issues when it is running. I am sure that I am missing something but just not sure what it is. Any help would be greatly appreciated. with my untrained eye libcrypto.?? python2.7 and python3.4 seem to be the culprits but unsure how to solve or why it is an issue. ThanX Mike syslog.txt
  10. Hey Guys, Well I go it back up. Had to delete the image and reload all of the dockers. (not too bad) got almost everything running again. Included a png of the docker screen. I guess that the docker.img file size reflects the size specified when creating it. but from this pic it seems that I am only using a 1/4 of the allocated space hmmmmmm. Oh well we will see how it goes from here. Again thanx for the input. BTW should the "scrub" be run at any specific time or are there some triggers that I need to watch for? Mike
  11. Guys, Just a quick one. What if I disable the docker and just changed the size of the docker would that help or hurt. I have not done it yet but just want to know so I don't make an even bigger mess. I am guessing that I would change it to 20GB from 15GB. Just looked at the image size and it is over the 15GB @16106127360. oops . Would it be nice to get a warning before the catastrophe? This all brings up another question, should the docker.img and what ever is necessary for the vm's be on a separate/multiple "cache" drives (out of the arrary) I already running one cache drive in the system, it is 500GB. Thanx again. Mike
  12. Guys Thanks for the quick response. I attached a image of the docker tab in settings and there is no clear way to run a scrub of the image from the gui. And from what I can see it doesn't even know that there is a image there. I did notice the lines in the syslog but was not sure what it was telling me. Originally I set the image size to 15GB but perhaps when the container went to update that was where the issue came in. So stuck again. Is there a way to safely do the scrub from the command line.
  13. I have been working to get moved over to Unraid 6 from 5. The upgrade went well, now I am getting all the original plugins moved over to dockers. After an update to an existing docker everything fell apart. Now I get (line 942-952) "Not starting Docker: mount error". so not even the gui knows about dockers. I have attached the syslog and would appreciate any insight to get this back up and running. I updated the "home-assistant" docker and thats when things went south.(as if it really matters now) Plex is running as a plugin (haven't got to that one yet) and no problems so far. syslog.txt