sebz29a

you can see my ngnix swag file for speedtest-tracker It's not working swag and speedtest-tracker are on the same docker network ## Version 2023/05/31 # make sure that your <container_name> container is named <container_name> # make sure that your dns has a cname set for <container_name> server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name speedtest.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth (requires ldap-location.conf in the location block) #include /config/nginx/ldap-server.conf; # enable for Authelia (requires authelia-location.conf in the location block) #include /config/nginx/authelia-server.conf; # enable for Authentik (requires authentik-location.conf in the location block) #include /config/nginx/authentik-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable for ldap auth (requires ldap-server.conf in the server block) #include /config/nginx/ldap-location.conf; # enable for Authelia (requires authelia-server.conf in the server block) #include /config/nginx/authelia-location.conf; # enable for Authentik (requires authentik-server.conf in the server block) #include /config/nginx/authentik-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app speedtest-tracker; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } }

I do expose the port 80. The GUI is accessible in HTTP but it's not working behind a reverse proxy. I have an error "failed while requesting certificate status" No problem with others containers. Did anybody access to the application behind a reverse proxy ? Thanks u for your help

Hi, i want to access speedtest-tracker behind a reverse proxy, swag in occurence. In the log i can see 🔒 SSL_MODE has been set to MIXED, setting the web server to work in HTTP + HTTPS... 🏃‍♂️ An SSL key was not detected, so I'll generate a self-signed SSL certificate pair for you... The problem is that i don't find the way to access the application in HTTP from my reverse proxy. Only https is working but don't behind the reserver proxy. Thank u for your help.

Problem solved removing an old deprecated plugin : CA config editor

Hi, I have a similar issue since unraid 6.12.4. Web gui in slow on main tab / Terminal / log / about 10 secondes to open. This issue was not present in unraid 6.12.3. I don't use the unraid connect plugin Thanks U for your help

I'm very sorry now it's working perfectly i've been disconected from tailscale. I'm a New user of the plugin and can confirm evrything is ok with my two unraid servers 👌

Hi, Taildrop seems to don't work with unraid 6.12.3 and the last version of the plugin I have set a Taildrop Location I found this erreor in the logs : unraid Taildrop: using /var/lib/tailscale/Taildrop unraid Taildrop support: symlink "Taildrop" not found Unraid is not disponible as destination from other tailscale device. Thanks u for your help and for this plugin

Hi, Thanks U very much for the quirk !!! I just upgrade to 6.11.3 and I can confirm It's now working all my NVME drives are recognized👍😎.

Thank U very much. I have downgraded to 6.10.3 waiting for the next stable release with this quirks.

In the 6.11.1 syslog file I can find error : globally duplicate IDs for nsid 1 and Ignoring bogus Namespace Identifiers In 6.10.3 this errors are not presents and the device is recognized

Hi, With unraid 6.11.1 it's the same problem one of the first pool drive is not recognized. you can find my diagnstics file attached Thank U for your help unraidprd-diagnostics-20221008-0756.zip

hi I think I have a similar problem In my unraid server I have 2 pairs of crucial NVME drive : - First pool = 2 x crucial P2 NVME 250 GB (exactely the same models and firmware version) the two are connected on M2 slot on the MB - Second pool = 2 x crucial P2 NVME 2 TB (exactely the same models and firmware version) the two connected with PCI express adapter MB = Supermicro X11SCA-F when I update to 6.11 one of my two crucial nvme drive of the first pool is not reconized and not present in the system devices screen (with iommu group) I have to rollback to 6.10.3 for this drive to be recognized (so we can expect the nvme drive is not defect) In my case it can't be a device not supported by the newer kernel because they are exactly she same model size and firmware version (in the first pool). one is OK and the other is not reconised In 6.11 the first is reconized not the second (command executed with unraid 6.10.3 after the rollback) root@pyramiden:~# udevadm info -q property -n /dev/nvme2n1 DEVLINKS=/dev/disk/by-id/nvme-CT250P2SSD8_2022E2A7F6CD /dev/disk/by-id/nvme-eui.6479a7fff0000007 DEVNAME=/dev/nvme2n1 DEVPATH=/devices/pci0000:00/0000:00:1b.4/0000:04:00.0/nvme/nvme2/nvme2n1 DEVTYPE=disk DISKSEQ=18 ID_MODEL=CT250P2SSD8 ID_PART_TABLE_TYPE=dos ID_SERIAL=CT250P2SSD8_2022E2A7F6CD ID_SERIAL_SHORT=2022E2A7F6CD ID_WWN=eui.6479a7fff0000007 MAJOR=259 MINOR=0 SUBSYSTEM=block USEC_INITIALIZED=24785941 root@pyramiden:~# udevadm info -q property -n /dev/nvme3n1 DEVLINKS=/dev/disk/by-id/nvme-CT250P2SSD8_2022E2A7F6C1 /dev/disk/by-id/nvme-eui.6479a7fff0000007 DEVNAME=/dev/nvme3n1 DEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:0c:00.0/nvme/nvme3/nvme3n1 DEVTYPE=disk DISKSEQ=19 ID_MODEL=CT250P2SSD8 ID_PART_TABLE_TYPE=dos ID_SERIAL=CT250P2SSD8_2022E2A7F6C1 ID_SERIAL_SHORT=2022E2A7F6C1 ID_WWN=eui.6479a7fff0000007 MAJOR=259 MINOR=2 SUBSYSTEM=block USEC_INITIALIZED=24756285 Thanks U for your help

Hi, i'm in the same case. I have 2 polls each 2 Nvme drive in my unraid server. 6.10.3 evrything is ok 6.11 one if the Nvme cache drive is not recognized. Rollback in 6.10.3 solve the problem. I can't see enything in 6.11.1 changelog about this. What does i have to do to solve this problem ? Thanks for tour help

Hi, You have to delete if the redis folder allready exist and execute the commands before to install the container. Is there an error in the log of the container when execute it ?

Hi, You have to create the directory with command "install" for the non root user 1001 it's the only way I find to execute the container with non root right. With this container I don't find any way to use an other non root user/group like 99/100 To create the directory before the container installation with the good owner group and privilege in terminal : sudo install -d -m 0755 -o 1001 -g 0 redis cd redis/ sudo install -d -m 0755 -o 1001 -g 0 bitnami With this command you will not have any error after the container installation. It's is now more secure than the use of 777 like in previouse unraid versions.