Tolete
Members
-
Joined
-
Last visited
Everything posted by Tolete
-
Cachet webUI = Error 500 log = 'IPADDRESS' - - [11/Mar/2021:12:21:57 -0500] "GET / HTTP/1.1" 500 3177 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.190 Safari/537.36" "-" where are the "highly trained team of monkeys"?
-
ideally you would want to compare the two drivers on your system from before the update and after. you can take note of the driver version you have now, perform update again and see if the driver ver changes. that will give you some indication if your driver ver reverted back or not. A more stable solution would be a different HBA/LSI. While back when i was looking into which HBA for the NetApp shelf i came across some incompatibility issues with the actual name brand NetApp HBA controllers. currently i can tell you im on SAS2008 in IT MODE w/ [1000:0072] 03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
-
I updated unraid to 6.9 and did not experience problems. Is the shelf/disk showing up on bios? I updated unraid to 6.9 and did not experience problems with my shelf. -Is the shelf/disks showing up on bios? -what HBA/LSI are you running?
-
high in-bond traffic (100+ Mbps) on the dashboard when running delugevpn. Traffic normalizes when downloads are completed or container is stoped. Any help resolving this matter i would i appreciated.
-
that's correct.
-
yeah no joy here. Surprisingly running a different onlyoffice document server image (chvb) same proxy config all works well. When i attempt to run the official onlyoffice document server image (SIWATS) i get a 400 bad request . Send help!
-
anyone got the official OnlyOfficeDocumentServer running on nextcloud 21?
-
I too received this message, i was able to solve it after retrying the installation from scratch. -removed nextcloud and mariadb -settings run clean up -remove any shares/folders. Just move any data files you have to temp location. Once everything is back and running i moved it back. clean install was problem free.
-
can you repost your final "working" onlyoffice proxy config for us. thanks.
-
thank you, what are the correct parameters to add it manually?
-
Still no joy on nextcloud 21 waiting on update. -anyone got the repository "linuxserver/nextcloud tag ?"
-
need some help applying updates/hotfixes; Security Alert Important Cross-Site-Scripting (XSS) security fix. Please upgrade as soon as possible. 3.9.3 / 3.8.4 / 3.7.4 / 2.4.14 / 1.3.5 Security Alert Critical security hotfix for Live Chat available in our latest releases 3.10.5, 3.9.7, 3.8.8. Please upgrade as soon as possible. how do i go about applying these updates/fixes, currently unraid shows up-to-date
.png.86e04890d8e450bfbb3a1cbbaf6055be.png)
-
only issues I'm having with NC is this error code. Client error: `GET https://documentserver.MYDOMAIN.COM /healthcheck` resulted in a `400 Bad Request` response: <html> <head><title>400 Bad Request</title></head> <body> <center><h1>400 Bad Request</h1></center> <hr><center>ngin (truncated...) can someone translate this to English for me please and thank you. -onlyoffice for some reason stopped working. I suspect im in need of an updated onlyoffice.subdomain.conf file to work with swag (could be wrong), but everything else working normal (A+). here is my current onlyoffice.subdomain.conf file was working before swag migration. ---------------------------------------------------- # only office doc server server { listen 443 ssl; server_name documentserver.*; 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_docs OnlyOfficeDocumentServer; proxy_pass https://$upstream_docs:443; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Proto $scheme; } } ----------------------------------------------------
-
I need of some help with bitwarden "bitwarden.subdomain.conf" file. looks like Swag last update update, upgraded its proxy files. I was able to upgrade all other proxy files but for some reason can figure this one out. old - bitwarden.subdomain.conf - - working #BITWARDEN # make sure that your domain has dns has a cname or a record set for the subdomain bitwarden # This config file will work as is when using a custom docker network the same as letesencrypt (proxynet). # However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve. # If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7 resolver 127.0.0.11 valid=30s; upstream bitwarden { server bitwardenrs:80; } server { listen 443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://bitwarden; proxy_set_header Host $host; 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; } location /notifications/hub { proxy_pass http://bitwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://bitwarden; } } new - bitwarden.subdomain.conf.sample - - not working ## Version 2020/12/09 # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url # make sure your bitwarden container is named "bitwarden" # set the environment variable WEBSOCKET_ENABLED=true on your bitwarden container server { listen 443 ssl; listen [::]:443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.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 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /admin { # 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 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /notifications/hub { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 3012; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } }
-
Do we know what the correct/safe power up/down sequence is? -From the write-up looks like power on the disk shelf first (give it a minute or 2). Then power on server/host? Power down? 1. Power down server/host 2.Power switch on disk shelf correct me if im wrong?
-
Before i launch this NMC out the... unRaid w/ Network UPS Tools (NUT) w/SNMP = no joy unRiad w/o Network UPS Tools (NUT) w/SNMP = missing "NOMINAL POWER, UPS LOAD" pfSense w/ Network UPS Tools (NUT) w/SNMP = joy someone please explain, pfSense w/ Network UPS Tools (NUT) w/SNMP settings are dead simple. Maybe need help with the settings for unRaid w/ Network UPS Tools (NUT) w/SNMP.
-
meh, need some help. Unraid to UPS ping successful UPS to Unraid ping successful running a Smart-UPS-2200 w/AP9631 ____________________________ Start APC UPS daemon: Yes UPS cable: Either Custom UPS cable: UPS type:PCnet Device:ipadrr:username:pass ____________________________ AP9631 not compatible w/Unraid?
-
QSFP(SFF-8436) to MiniSAS(SFF-8088) DDR Cable https://www.amazon.com/SFF-8436-MiniSAS-SFF-8088-Cable-2-Meter/dp/B07Y4ZKQJB/ref=sr_1_3?crid=1UNRJFYPKWWC5&dchild=1&keywords=qsfp%2Bsff-8436%2Bmini%2Bsas%2Bsff-8088&qid=1589076335&sprefix=mini%2Bqsf%2Caps%2C147&sr=8-3&th=1
-
Plug and Play here -Unraid 6.8.3 -Dell R710 II w/Dell H200 in IT Mode -LSI 9200-8e in IT Mode -NetApp DS4246 24-Bay IOM6
.png.86e04890d8e450bfbb3a1cbbaf6055be.png)