darrenyorston

Hi all. I picked up an Ubiquiti USG today. I have it all set up fine however IP assignment is in the 192.168.1.0 range. My server was set as 10.1.1.140. I removed the USB and renamed the network.cfg file. I restarted the server and upon entering the server's new IP address it wants to resolve to the SSL address. How do I get access to the webui again?

With the system temp plugin how do I determine the motherboard sensor name? My CPU temp sensor was releatively simple. It was initially k10temp=Tdie. Though its changed its name now and says k10temp-CPU temp. I dont know what my MB sensor is called though. How do i work out whether jc42 - temp1 or jc-42-temp2 are the mb? And which part of the mb? When I look in the bios there appear to be 5 sensors but they are obviously named and do not reflect the sensors reported by the plugin. My MB is a Gigabyte x399 Aorus Xtreme.

I really dont know if i fixed mine or it just came good. I could only see code 43 when i used vnc. I read though that using vnc will often show code 43 anyway. I thought to update the driver using device manager, via vnc, but most buttons were greyed out. I could uninstall the 1080 though. So i did. After reboot i noticed the buttons in device manager for the 1080 were no longer greyed out. So i closed vnc and acessed the vm via teamviewer. I updated the driver via device manager. The moment i did my displays started working. I rebooted the vm and all is working normal. I dont what this had to do with linux vms though.

That worked. I presume each time I want to edit the plugin Ill just need to change the port? Thanks for the help. Much appreciated.

Thankfully a short lived issue. Though it was a bizarre solution. I read on the net someone suggesting using Teamviewer. I accessed the VM using VNC, installed Teamviewer. I un-installed the GTX1080 then restarted the VM. Once restarted I got the Teamviewer pwd then closed the VN client. Accessing the VM via Teamviewer I updated the driver. Once I restarted the VM the 1080 worked with no problems. For some reason the Linux VMs also began to work. No idea why. They didnt display video but once I changed the Windows 10 device the Linux devices started working.

Appears I have been struck by the Code 43 issue. I moved my GTX1080 to a different PCIe slot and my VMs, Windows 10 and Linux, would start but there was no display output. I set a primary video display as VNC with the 1080 as secondary. When looking via VNC I could see the error on the 1080 in Windows System Devices. The Linux VMs crash straight soon after boot so I cant see what they are doing. I tried using a new edited ROM but it didnt resolve the issue. Hypervisor is off in the VM template and obviously isnt there for Linux VMs. At the moment cant get display output on any VMs. Any suggestions?

I checked that out. I hadnt changed the VM name and the Vdisk location still reflected the Vdisk folder name. I got it to save by changing the vidsk setting to manual. Anyways, seems I caused a worse problem. My Nvidia GPU doesnt seem to work now, on any VM. No errors when I pass the GPU through, using the same vbios as when it worked yesterday, just no output to the displays. I tried moving the cards back to their original locations. No luck. ;-( UPDATE: Appears Code 43 has occurred on my GTX1080. UPDATE: Fixed the problem utilising Teamviewer instead of VNC.

I am having an issue with one of my VM templates and would like some advice. I have a Windows 10 VM with GPU and USB controller passthrough. I need to move a card that was in a PCI slot to another PCI slot. Even though I did not move the GPU I was passing through it now has a different ID. As a result the VM does not work anymore. I am not surprised. However, the problem is I cant seem to update the VM. When I change the GPU back to VNC and select update it displays "Updating" (greyed out) but never seems to progress. If I go back to the VM list the change isnt saved. I am presuming something is wrong with the template. My other VMs dont have this issue. I know I can create the VM easily enough but am cautious as the Windows 10 VM is activated. Can I just change the template XML without creating an issues with the activation?

Unable to connect Firefox can’t establish a connection to the server at d7b7dd5f31171a775e28111b7128e5ddc8c08b3c.unraid.net:2379. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer’s network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. On the settings page it shows the ControlR Status as Stopped. It wont start on port 2379

If I change the port to 2379 the server wont start. It shows stopped even though Enable Control Server is set to Yes. And yes I clicked Apply and Done. Its the same error code regardless of the port I try: SSL_ERROR_RX_RECORD_TOO_LONG

Didnt work. I tried a few other ports as well. Same result. SSL is set to yes.

Finally got the opportunity to have a look at the update. I am having an issue where the web UI isnt accessible with SSL active. Do I need to edit something in the plugin to allow it to work with SSL?

Sorry. I thought this post was deleted. Ive solved the issue.

I have started getting a problem with accessing my SMB shares from a Windows 10 VM. Everything has been working fine. I have been able to do whatever I want to files on shares. create, edit, delete. However, today I was working on a document and when I went to save it said permission denied. I had created the document earlier and had been working on it fine. I had to save it to the VM then use File Explorer to move the file to the SMB share. I can move files, create folders, delete content no problem. But for some reason I can save a word document once its been edited. I created a txt file on the same share, edited it, and was able to save it no problems. I only have the default root user on my server. I have been creating,editing, and deleting word documents on my server and never had this problem before. In fact I was doing this fine two days ago. Now it wont work. I have created a test SMB share and made it accessible. From the VM I created a word document in the new share, edited it, and saved with no problem. SOLVED: I noticed the icon next to the network share was different. Seems something called Offline Syncing was active. No idea where it came from, never installed it and never seen it before.

I did. Thats where the 11.9gb came from.

No problem.

Yeah ive noted thats how containers update. I use quite a few of your containers and have never had an issue. As a result i thought nothing of updating the container. I was not surprised when it said the container was deleted. Only when it said it was finished. As i said not a huge issue with deluge as it takes only a few minutes to set up.

Let me try to make it clearer for you. I DID NOT RECEIVE A WARNING THAT THE CONTAINER WAS GETTING FULL. Furthermore, I would not call 12GB in a 20GB container "getting full". As I said I am not overly concerned that the container was deleted as it was easy enough to re-install. I am more concerned that clicking update caused the container to delete. Makes me hesitant to update any container.

I did not say it was the containers fault. Try reading my post again. Yes I do receive notifications. All updates are selected, as are all notices, warnings, and alerts. I did not receive a warning. My containers showed as "Update Ready". I updated the container and it deleted it. My only issue is that when I selected update it would have been preferable to be notified the container was going to be deleted. If it had I would not have selected update. Thankfully it was not something or greater value. According to the O/S my containers total 11.9 GB. My container size was set 20GB when this occurred. As a consequence I raised it to 30GB. I have since raised it to 50GB so as to stave of similar issues in the future.

Resolved it. Seems the docker contain was getting full. Stopped docker and increased its size and all was good. Cant say an auto-delete of the container was great. A warning might have been better.

Yeah man. When I checked my containers every container I have said there was un update available. I started with deluge as its first on the list. The container started updating. It processed, deleted the container then stopped. The container was then gone. I had to reinstall it.

US Texas end point doesnt support port forwarding. https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn Also check your LAN NETWORK config. I am assuming 10.0.0.102 is you unRAID server. If so change the fourth group to 0 and not 102.

So a bunch of binhex containers are showing as "update ready". I updated deluge but the update said it was deleting the container instead. now its gone. what gives?