bastl

@luca2 The issue the Threadripper chips had is that they used 2 dies or 4 where the ressources (RAM, PCI lanes etc) are shared between them. On 1st gen you ended up with a higher latency which could cause some small performance decrease with mixing cores from 2 dies. With Ryzen 2nd gen this shouldn't be that big of an issue anymore and with 3rd gen the latency is even further reduced. In your case I guess cores 0/1/2 and it's HT are on the same chiplet and the rest on the second. You can kinda test it. Setup a VM with lets say cores 1/7 and 2/8 and do some memory benchmarks and do the same benchmarks after changing the cores to 1/7 and 3/9. You will maybe see some slightly higher latencies for RAM. But in general you won't notice it in games anyways. Always keep in mind to not to use the core 0 and it's HT because this will always used by unraid itself for doin stuff in the backround.

The custom Qemu arguments are still working. Starting with Qemu 4.0 they changed the naming to x-speed and x-width. from the Official Changelog Qemu 4.0 PCI/PCIe Generic PCIe root port link speed and width enhancements: Starting with the Q35 QEMU 4.0 machine type, generic pcie-root-port will default to the maximum PCIe link speed (16GT/s) and width (x32) provided by the PCIe 4.0 specification. Experimental options x-speed= and x-width= are provided for custom tuning, but it is expected that the default over-provisioning of bandwidth is optimal for the vast majority of use cases. Previous machine versions and ioh3420 root ports will continue to default to 2.5GT/x1 links. This is how it looks like in 6.8 RC5 now <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.x-speed=8'/> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.x-width=16'/> </qemu:commandline> Nvidia System Info is reporting the correct link speeds again

@darthcircuit Starting with 6.8 RC1 I had to remove the pci-root-port patch. Sure it shows x1 in the Nvidia control panel, but I can't notice any performance drop as in qemu 3.xx versions. Couple people using qcow2 and the underlying xfs filesystem which is the main issue with qemu 4.1. Compressed qcow2 files are only a issue on top of the corruption of vdisks. 4.1.1 maybe will have a fix and if not 4.2 for sure which is already worked on. https://bugs.launchpad.net/qemu/+bug/1847793

All in all it's not a big deal. If I edit the script file itself with an external editor the notification comes through correctly. As long as not all german words are filtered out, I'am fine with it 😂

Is it Unraid web ui erasing my letters or the plugin itself?

@Squid If I change it inside the Unraid ui, you say this is how it is? I never changed the script file itself only via ui and it always worked. 😂 No external editor involved.

@andreidelait None of the header informations nextcloud complains about are set in the letsencrypt default site-confs file for me. And it shouldn't if they come with changes during an nextloud or docker update, right?

I'am using a script for snapshotting VMs on BTRFS formatted drive which informs me via telegram when finished. Switching to 6.8.RC4 and adjusting some paths in the script I've noticed some german letters (ä ö ü) getting removed by the script when saving. Never happened in earlier builds. The affected line is the following: /usr/local/emhttp/webGui/scripts/notify -i normal -s "BTRFS Send/Receive beendet" -d "Script ausgefhrt" -m "$(date '+%Y-%m-%d %H:%M') Information: BTRFS VM Offline Snapshot auf HDD erfolgreich abgeschlossen" It should be "Script ausgeführt" not "ausgefhrt". Is this an issue from the plugin itself or caused by unraid. I think there was an update for user scripts since I am on 6.8RC but not 100% sure. Any idea how to fix this? full script: #!/bin/bash #backgroundOnly=false #arrayStarted=true cd /mnt/cache/VMs_backup sd=$(echo VMs_backup_off* | awk '{print $1}') ps=$(echo VMs_backup_off* | awk '{print $2}') if [ "$ps" == "VMs_backup_offline_$(date '+%Y%m%d')" ] then echo "There's already a snapshot from today" else for i in `virsh list | grep running | awk '{print $2}'`; do virsh shutdown $i; done # Wait until all domains are shut down or timeout has reached. END_TIME=$(date -d "300 seconds" +%s) while [ $(date +%s) -lt $END_TIME ]; do # Break while loop when no domains are left. test -z "`virsh list | grep running | awk '{print $2}'`" && break # Wait a little, we don't want to DoS libvirt. sleep 1 done echo "shutdown completed" virsh list | grep running | awk '{print $2}' btrfs sub snap -r /mnt/cache/VMs /mnt/cache/VMs_backup_offline_$(date '+%Y%m%d') for i in `virsh list --all --autostart|awk '{print $2}'|grep -v Name`; do virsh start $i; done sync btrfs send -p /mnt/cache/VMs_backup/$ps /mnt/cache/VMs_backup_offline_$(date '+%Y%m%d') | btrfs receive /mnt/disks/VMs_backup_hdd if [[ $? -eq 0 ]]; then /usr/local/emhttp/webGui/scripts/notify -i normal -s "BTRFS Send/Receive beendet" -d "Script ausgefhrt" -m "$(date '+%Y-%m-%d %H:%M') Information: BTRFS VM Offline Snapshot auf HDD erfolgreich abgeschlossen" btrfs sub del /mnt/cache/$sd #btrfs sub del /mnt/disks/VMs_backup_HDD/VMs_backup/$sd else /usr/local/emhttp/webGui/scripts/notify -i warning -s "BTRFS Send/Receive gescheitert" -d "Script abgebrochen" -m "$(date '+%Y-%m-%d %H:%M') Information: Es wurde heute bereits ein Offline Snapshot erstellt" fi fi

@EdgarWallace Config looks ok to me. Did you restarted the container already? For me without a restart of Nextcloud changes won't have an effect.

@EdgarWallace Can you please post the file. If your domain name is in there, please remove it or blur it out /mnt/user/appdata/nextcloud/nginx/site-confs/default

Make sure the following is set in your "default" site-conf add_header X-Content-Type-Options "nosniff" always; add_header X-Robots-Tag "none" always; add_header X-Download-Options "noopen" always; add_header X-Permitted-Cross-Domain-Policies "none" always; add_header Referrer-Policy "no-referrer" always;

@CorneliousJD My config looked exactly the same like yours. I did what @local.bin and @Smooth Beaver suggested. 1. Backup of my current running Nextcloud 17 install 2. grabbed the config template for nginx from https://docs.nextcloud.com/server/17/admin_manual/installation/nginx.html 3. adjusted a couple things so it matches the old config like uncommented IPv6 access and adjusted the server_name _ without a domain name server { listen 80; # listen [::]:80; # server_name cloud.example.com; server_name _; adjusted the cert path ssl_certificate /config/keys/cert.crt; ssl_certificate_key /config/keys/cert.key; changed the path for Nextcloud # Path to the root of your installation root /config/www/nextcloud; changed the max upload size to my old settings # set max upload size client_max_body_size 10G; fastcgi_buffers 64 4K; included the full path for fastcgi_params "/etc/nginx/fastcgi_params" location ~ ^\/(?:index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+)\.php(?:$|\/) { fastcgi_split_path_info ^(.+?\.php)(\/.*|)$; set $path_info $fastcgi_path_info; try_files $fastcgi_script_name =404; include /etc/nginx/fastcgi_params; and finally checked if all the settings for for "Strict-Transport-Security" and "X-Frame-Options" are the same as before. 4. restarted Nextcoud docker 5. restarted letsencrypt docker 6. logged into Nextcloud and checked the logs and disabled the "Nextcloud announcements" app because it spammend the logs with Symfony\Component\Routing\Exception\RouteNotFoundException: Unable to generate a URL for the named route "ocs.provisioning_api.AppsController.disable" as such route does not exist. Looks this a known issue and will be addressed with an later update. https://github.com/nextcloud/nextcloud_announcements/issues/54

Could be also possible the browser you are using causing this.

Could be the default driver from windows causing this. Each version of windows indroduced lots of changes and new bugs. Might be you have an iso that comes with errors or has some corrupted files on it. Wouldn't be the first time I'am seeing this from Microsoft 😂 I had a freshly 1903 iso downloaded with the creation tool from microsoft which for f*** sake won't boot. Redownloaded the file the same day with the same tool and it worked. Same size, different hash. If you have an older iso which worked in the past, try this.

Did you installed the qxl driver for the gpu by hand? On default Win10 uses a basic driver and shows "basic graphics adapter" in the device manager without errors. Try to install the driver for the GPU from the virtio iso.

Strange. In general VNC connection errors via the web-vnc unraid comes with are really rare. I think one of the latest 6.8 RC versions some people reported having some issues with the web-vnc not connecting. Which version of Unraid you're on?

@rorton Did you tried to change the Windows power settings from balanced to performance? I've not had the exact same error as you in the past, but with the balanced power plan after some idle time windows falls a sleep for me and couldn't wake up again. Can't tell you which version of Windows I was on back than, but changing to performance solved my issue.

I'am using Letsencrypt explicitly for Nextcloud

@rorton You can convert the formats sure. example: qemu-img convert -O qcow2 -p original_image.img changed_image.qcow2 or qemu-img convert -O raw -p original_image.qcow2 changed_image.img With the above cli command you can convert the "original" image to an qcow2 format. "-O" followed by the "input-file" and the "output-file". "-p" shows the progress of the convertion. Second example is to output an raw vdisk file. Every format has some extra options you can use. For example qcow2 supports compressed files (-c). Here is a quick link for the qemu-img man page: https://linux.die.net/man/1/qemu-img If you're on the latest unraid 6.8 RC version you might avoid compressed qcow2 files right now. I've discovered a bug where the disk can get coruppted. Not actual sure if this a unraid or a qemu issue.

The type of the vdisk stays the same. Simply change the file itself to librenms.img and the extension in the source file path to the same.

Quick fix would be to rename the file extension of the vdisk to img and edit the xml and change the extension. You can basically name the vdisk file how ever you like, as long as the format for the vdisk is setup correctly in the xml. example: <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback' discard='unmap'/> <source file='/mnt/user/VMs/Mint/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='scsi'/> <boot order='1'/> <alias name='scsi0-0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> I can rename the vdisk what ever I like as long as the type, in my case qcow2 is the correct one and the VM shouldn't have any issues. I can even call it vdisk1.vmdk and it will work. Unraid only checks if the declared type matches with the file you setup.

@blaine07 Go to Unraids web ui, click the docker tab, left click the nextcloud icon and select "console" and type the following nano /config/nginx/site-confs/default Thats the file I modified.

Check if there is a line in the same file which looks like the following add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; I think I had that same warning a couple versions ago and changed/added that line.

I connected a console inside the docker, opened the file "/config/nginx/site-confs/default" with nano and placed it in the server section below already existing "add_header" options. And now when I look at it again, there is already same option commented out further above 😂 EDIT: I modified the file inside the nextcloud docker, not the letsencrypt docker.