Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

mikeyw

Members
  • Joined

  • Last visited

  1. Thanx much @ConnerVT
  2. After years (since 2013) running, my boot USB device crashed. Came home to find the server just cycling never booting. Thinking it was a PSU again, quickly changed it out and nothing, same problem, removed the USB and it booted directly into the BIOS, I found it, at least a start for now. I did find the USB rebuild instructions to fix this mess and it looks like my config directory is still accessible, but my problem is, I was on version 6.9.2. Where can I find the zipped version of 6.9.2 so I can continue this process? Is there a archive location in Lime-Tech somewhere I can get at it? Just point me in a direction and I can run with that. ThanX much - Mike
  3. 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
  4. 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
  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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.