Jump to content

MothyTim

Members
  • Content Count

    101
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MothyTim

  • Rank
    Advanced Member
  • Birthday 12/25/1964

Converted

  • Gender
    Male
  • URL
    http://www.timstephens.co.uk
  • Location
    Plymouth, UK.
  • Personal Text
    MB: Gigabyte Z390 UD | CPU: Intel® Core™ i7-8700K CPU @ 3.70GHz | RAM: 16 GiB DDR4 | Cache: M2 Crucial MX500 250GB SSD | Parity: 3TB | Array: 3x3TB | Nvidia Geforce GTX1050 Graphics as pass-through.

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This is the config I've ended up with after much eperimentation! Devices show up and I'm able to add them and manage them! Cheers, Tim # make sure that your dns has a cname set for unms and that your unms container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name unms.YOURDOMAIN.com; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_unms unms; proxy_pass https://$upstream_unms:443; proxy_cache off; proxy_store off; proxy_buffering off; proxy_set_header Host $http_host; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Referer ""; client_max_body_size 0; } }
  2. Hi, no longer seems to be an issue for me! I think my docker was growing because I couldn't connect any devices! Maybe it didn't like sitting there with nothing connected? I had another go at getting Letsencrypt reverse proxy to work and was finally successfull, since then the docker hasn't been growing! Cheers, Tim
  3. Hi, still getting this error in my log? Anyone else? ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Europe/London URL=timstephens.co.uk SUBDOMAINS=nextcloud,sonarr,radarr,deluge,tautulli,ombi EXTRA_DOMAINS=unifi.berecomputing.co.uk,unms.berecomputing.co.uk ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=tim@timstephens.co.uk STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d nextcloud.timstephens.co.uk -d sonarr.timstephens.co.uk -d radarr.timstephens.co.uk -d deluge.timstephens.co.uk -d tautulli.timstephens.co.uk -d ombi.timstephens.co.uk EXTRA_DOMAINS entered, processing Extra domains processed are: -d unifi.berecomputing.co.uk -d unms.berecomputing.co.uk E-mail address entered: tim@timstephens.co.uk http validation is selected Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found: no field package.preload['resty.core'] no file './resty/core.lua' no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/5.1/resty/core.lua' no file '/usr/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/common/resty/core.lua' no file '/usr/share/lua/common/resty/core/init.lua' no file './resty/core.so' no file '/usr/local/lib/lua/5.1/resty/core.so' no file '/usr/lib/lua/5.1/resty/core.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './resty.so' no file '/usr/local/lib/lua/5.1/resty.so' no file '/usr/lib/lua/5.1/resty.so' no file '/usr/local/lib/lua/5.1/loadall.so') nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size Server ready
  4. I have noticed this in my log, not sure what's going on but it seems to be working ok? What is it and Is it a problem to worry about? nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found: no field package.preload['resty.core'] no file './resty/core.lua' no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/5.1/resty/core.lua' no file '/usr/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/common/resty/core.lua' no file '/usr/share/lua/common/resty/core/init.lua' no file './resty/core.so' no file '/usr/local/lib/lua/5.1/resty/core.so' no file '/usr/lib/lua/5.1/resty/core.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './resty.so' no file '/usr/local/lib/lua/5.1/resty.so' no file '/usr/lib/lua/5.1/resty.so' no file '/usr/local/lib/lua/5.1/loadall.so') nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size Server ready Cheers, Tim
  5. I found this on Ubiquity’s website, not sure what I need from it to make UNMS work? Like I said previously I can get the GUI page but can’t see my devices, that was by editing the UniFi template! Hoping that someone with mor knowledge can help? map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { listen 80; server_name unms.example.com; client_max_body_size 4G; location / { proxy_redirect off; proxy_set_header Host $host; proxy_pass http://127.0.0.1:8080/; } } server { listen 443 ssl http2; server_name unms.example.com; ssl_certificate /etc/letsencrypt/live/unms.example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/unms.example.com/privkey.pem; ssl on; set $upstream 127.0.0.1:8443; location / { proxy_pass https://$upstream; proxy_redirect https://$upstream https://$server_name; proxy_cache off; proxy_store off; proxy_buffering off; proxy_http_version 1.1; proxy_read_timeout 36000s; proxy_set_header Host $http_host; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Referer ""; client_max_body_size 0; } }
  6. Have you edited server_name with your domain name and left it blank here for security?
  7. Hi, no it’s UNMS controller it’s for the Edge series products from Ubiquity. I have UniFi working perfectly, just can’t get UNMS to connect devices! cheers, Tim
  8. Hi, trying to get UNMS to work correctly, has anyone had success with this? I can connect ok to the GUI but can't get devices to connect! Here is my conf file. # make sure that your dns has a cname set for unms and that your unms container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name unms.berecomputing.co.uk; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_unms unms; proxy_pass https://$upstream_unms:443; } location /wss { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_unms unms; proxy_pass https://$upstream_unms:443; proxy_buffering off; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_ssl_verify off; } } Can anyone see anything wrong here? Cheers, Tim
  9. Ok so I updated yesterday and in 24 hrs docker image has grown 10% from 67% to 77%! So still a problem for me!
  10. Ok thanks guys, I’ll try and work out which slot it’s referring to and then I might be able to workout what’s going on! Cheers, Tim
  11. Hi, I have a recurring error that I have noticed in the logs that I can't track down! All my PCIe cards seem to function correctly. `does anyone know what they are telling me? Thanks, Tim Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First)
  12. I believe this is because Plex have stopped using Gracenote, so there will be problems with the music library until the transition is complete! Plex never give a time frame so I guess we wait!
  13. Hi, I’ve noticed very high RAM usage all of a sudden! Anyone else noticed this? Was there an update recently? cheers, Tim
  14. I have tried booting Unraid legacy and that has made no difference. I don’t think it going to work, it’s a shame but not the end of the world just would have been nice for a couple of things! It is strange the a card from 2005 works happily in OVMF as it doesn’t support UEFI! I also tried booting into Windows baremetal and dumping the BIOS with GPU-Z but that says that the card doesn’t support reading bios! Anyone know anything else I can try? cheers, Tim
  15. This is the part of the log relating to the failed start of the VM! Jun 19 14:59:58 Tower kernel: vfio-pci 0000:08:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered blocking state Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered disabled state Jun 19 14:59:58 Tower kernel: device vnet1 entered promiscuous mode Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered blocking state Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered forwarding state Jun 19 14:59:59 Tower kernel: vfio-pci 0000:08:00.0: enabling device (0000 -> 0003) Jun 19 14:59:59 Tower kernel: qemu-system-x86[24486]: segfault at a8 ip 0000563b04d4a9ea sp 00007ffdb3bcb010 error 4 in qemu-system-x86_64[563b04ce2000+4cc000] Jun 19 14:59:59 Tower kernel: Code: f9 ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 53 48 89 fb 48 83 ec 08 48 8b 6f 58 e8 1e dd ff ff 48 89 df e8 76 e9 ff ff <48> 8b 85 a8 00 00 00 48 85 c0 74 2e 8b 93 a0 00 00 00 39 90 a0 00 Jun 19 14:59:59 Tower kernel: br0: port 3(vnet1) entered disabled state Jun 19 14:59:59 Tower kernel: device vnet1 left promiscuous mode Jun 19 14:59:59 Tower kernel: br0: port 3(vnet1) entered disabled state Jun 19 14:59:59 Tower kernel: vfio-pci 0000:08:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none