pingmanping

@tjb_altf4 I kept my Jackett to the latest version and just realized that the proxy settings were broken. The only time I get this to work again was to follow your instruction Since the official unRaid 6.4.0, I gave my binhex-delugevpn an IP on a different subnet, and the vpn and privoxy seem to work; however, my Jackett proxy settings broke again after pointing it to use the new IP of the proxy. It used to be pointing to unRaid's IP when it was working. Would it be possible to point Jackett to use delugevpn as a proxy if they are on two different subnet? I am trying to re-ip my containers because I don't want my users to keep going to my unRaid server's IP. So far the only thing I got it working after re-IP-ing are Emby, Booksonic, Unifi

+1

got it. thanks Sent from my iPad using Tapatalk

I'm on 6.3.5

You are right. I deleted some of my tabs and it fixed the issue. However, how come I when I changed the display settings to 1680x1050, the web UI was still fixated to the original size instead of adapting to the new resolution.

I am on Macbook Pro Retina and screen resolution is 1680x1050

I have this issue for a while and did not bother finding a fix because I thought it was a temporary thing. However, it has been bugging me because I keep clicking the wrong button because of the problem. Please see the screenshot. I tried different web browsers - Chrome, Firefox, Safari, and IE, but got same results. I tried several mobile browsers and got the same results.

I am not sure if I should create a new post and reply to this one. I am installed the Linuxserver Syncthing. It works, but got some issues. I mapped the /sync to my share folder /mnt/user/Cloud/syncthing. However, when I create a folder via web UI, the "Folder Path" is /config. If I leave this to default, my share folder will be created on /mnt/cache/appdata/syncthing/folder-name. The fix that I have is to manually change the /config to /sync. Is this a normal behavior?

I have been trying to figure this out how to fix this UI. I have binhex-delugevpn container with PIA enabled. It has been working until two days ago. Nothing really has changed other than my Docker turned off all the containers by itself. I turned every container, and every single one works normal, but the binhex-delugevpn. Stuff that I have done so far - I deleted the container and reinstall it - did not fix the problem I deleted the container and copied the backup to /mnt/cache/appdata/binhex-delugevpn/ - did not fix the problem I deleted the docker.img and reinstall eveything - did not fix the problem The VPN part is working, and I can verify this by configuring my laptop to point to my unraid server's ip via port 8118, but I just don't have a web UI. Has anyone had encountered this issue? Thanks

What could be the sign if my cache disk dropped offline? Before I updated my containers last night and disabled then re-enabled the Docker this morning in the settings, all my containers are working and my IP camenras are recording to my cache disk. The issue started when I updated a container (radarr).

I rebooted the server, and got it working again. I am just wondering what could have caused this issue in the first place? I have not messed with my unraid server other than updating the containers and the plugins.

I updated radarr last night, and I didn't noticed that the update failed. Now, the icon is a questiona mark. I could not remove the container. Whenever I tried to remove the container, it barks at me stating "Execution Error". I deleted the copy in /mnt/user/appdata/radarr and /mnt/cache/appdata/radarr and I still can't remove the container, and getting the same error message. I just updated one of my containers and it was successfully updated; however, it did the same thing. That's probably why I did not noticed the issue last night. I stopped one of my containers and turned it back on, and it worked, so it has nothing to do with my server. I stopped all my containers then turned off docker in the settings and turned it back on. Now, I have no containers and the attached screenshot below is what I see when I go to the Docker tab. EDIT: I got a bunch of these in System Log Oct 30 04:01:32 BGDunRAID root: /mnt/cache/system/docker/docker.img is in-use, cannot mount Oct 30 04:01:32 BGDunRAID emhttp: err: shcmd: shcmd (304596): exit status: 1 Oct 30 04:02:02 BGDunRAID emhttp: shcmd (304616): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/system/docker/docker.img' /var/lib/docker 20 |& logger

I installed nextcloud from linuxserver and changed the port to 444. It was working, and I was able to access it over my local network. However, when I tried to access it over the VPN, it failed. I checked my firewall policy and I am allowing everything: Source addresses: SSL-VPN-NET-ADMIN-NETBOOK Destination addresses: any Applications: any Action: permit I had this brilliant idea to change the network type from bridge to host. This broke the container ever more, so I revert it back to bridge, but nothing happened. Now, I can access all my docker containers and the unraid server itself, but not nextcloud. I ran nmap and the port 444 is closed. I tried to remove the nextcloud container, and deleted the /mnt/cache/appdata/nextcloud then reinstall nextcloud again, but the port is still closed. I changed the network type from bridge to host, but the port is still closed. I restarted the server, and got my ssd filesystem corrupted, but I believe it is fixed now. Restarting the server did not help to fix the nextcloud issue. Has anyone have encountered this issue before?

It seems like MC has finished but not sure if the copy is 100% completed. I got home and the ssh was disconnected. I formatted the cache disk via putting a check mark on the format under the Main tab. I don't know if this is an issue or what, but the data that I have on the cache disk didn't get erased after running the format. Then after the format, the cache disk got mounted. All my docker images, and some files are now back, I think.

I don't remember of doing that. I hope that my ssh won't get disconnected

Okay. I just want to make sure. Does MC copy operation happen in the background by default? I really want to make sure because The reason I was asking was when I was doing rsync then my ssh somehow got disconnected, I had to do everything again. Does unraid have the ssh timeout setup. I know this is different but whenever I login to my firewalls at work the firewalls had a default of 15 minutes of idle then after this it will auto-disconnect the ssh.

One more thing, I ran the Midnight Command via SSH, would this be a problem? I don't know if ssh will eventually timeout while I'm at work then messed up my file transfer. This one worries me more.

Okay, so I don't need to do the "btrfs check --repair". I just need to format just like starting from scratch. Let me see if I understand you correctly. I can just move the copied files from the array to the newly formatted cache disk, correct?

Step 1 seems to be working. I am using Midnight Command to copy /x to my array. Once everything has been copied, what do I need to do with the cache disk? Do I need to format it as it shown in the Array Operation under the Main tab or do the "btrfs check --repair"? Is my SSD going bad?

I am not a linux guy. I just want to make sure that I am doing this correctly. Right now, I have the SSD plugged in to my elementary OS laptop via USB, and it is still unmountable. It shows up in the GUI, but when I right click and select "mount", it will bark at me saying that it is unmountable. Is the command is "btrfs fsck" or "btrfs check --repair"? Can I do this on my elementary OS laptop or on my unRaid server? Do I need to go to maintenance mode or just boot up normally?

Here is the btrfsck /dev/sdc1 root@BGDunRAID:~# btrfsck /dev/sdc1 Checking filesystem on /dev/sdc1 UUID: b56a1610-bb12-400e-9b26-904a0e5bb338 checking extents bad key ordering 19 20 bad block 281542656 Errors found in extent allocation tree or chunk allocation checking free space cache checking fs roots bad key ordering 19 20 root 5 inode 13583 errors 400, nbytes wrong root 5 inode 1300023 errors 2001, no inode item, link count wrong unresolved ref dir 257 index 3 namelen 7 name libvirt filetype 2 errors 4, no inode ref root 5 inode 1300025 errors 2001, no inode item, link count wrong unresolved ref dir 256 index 26 namelen 7 name domains filetype 2 errors 4, no inode ref root 5 inode 3765760 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 21 namelen 5 name unifi filetype 2 errors 4, no inode ref root 5 inode 3769246 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 22 namelen 10 name EmbyServer filetype 2 errors 4, no inode ref root 5 inode 3929077 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 25 namelen 9 name booksonic filetype 2 errors 4, no inode ref root 5 inode 4002362 errors 2001, no inode item, link count wrong unresolved ref dir 256 index 34 namelen 16 name domains_no-cache filetype 2 errors 4, no inode ref root 5 inode 4009051 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 27 namelen 16 name binhex-delugevpn filetype 2 errors 4, no inode ref root 5 inode 4009160 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 28 namelen 6 name radarr filetype 2 errors 4, no inode ref root 5 inode 4009380 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 34 namelen 13 name binhex-sonarr filetype 2 errors 4, no inode ref root 5 inode 4135121 errors 2001, no inode item, link count wrong unresolved ref dir 256 index 77 namelen 5 name Media filetype 2 errors 4, no inode ref root 5 inode 4374768 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 36 namelen 6 name apache filetype 2 errors 4, no inode ref root 5 inode 4378599 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 37 namelen 7 name jackett filetype 2 errors 4, no inode ref root 5 inode 4401772 errors 2001, no inode item, link count wrong unresolved ref dir 256 index 114 namelen 9 name Downloads filetype 2 errors 4, no inode ref root 5 inode 5424640 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 39 namelen 36 name Community_Applications_VM_XML_Backup filetype 2 errors 4, no inode ref root 5 inode 5425855 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 40 namelen 3 name kde filetype 2 errors 4, no inode ref root 5 inode 5665745 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 43 namelen 11 name binhex-plex filetype 2 errors 4, no inode ref root 5 inode 5692894 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 44 namelen 11 name binhex-emby filetype 2 errors 4, no inode ref root 5 inode 5861581 errors 2001, no inode item, link count wrong unresolved ref dir 256 index 148 namelen 21 name ESXi_Datastore_Lab_VM filetype 2 errors 4, no inode ref root 5 inode 6659751 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 50 namelen 9 name .htaccess filetype 1 errors 4, no inode ref root 5 inode 6659752 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 51 namelen 10 name index.html filetype 1 errors 4, no inode ref root 5 inode 6853111 errors 2001, no inode item, link count wrong unresolved ref dir 256 index 163 namelen 6 name Backup filetype 2 errors 4, no inode ref root 5 inode 6873968 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 59 namelen 20 name appdata_ocevq7fsss5f filetype 2 errors 4, no inode ref root 5 inode 6874048 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 60 namelen 7 name .ocdata filetype 1 errors 4, no inode ref root 5 inode 6874049 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 61 namelen 5 name karlo filetype 2 errors 4, no inode ref root 5 inode 6874148 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 62 namelen 14 name files_external filetype 2 errors 4, no inode ref root 5 inode 6874252 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 63 namelen 3 name kna filetype 2 errors 4, no inode ref root 5 inode 6874344 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 64 namelen 3 name aig filetype 2 errors 4, no inode ref root 5 inode 6896982 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 66 namelen 17 name mariadb-nextcloud filetype 2 errors 4, no inode ref root 5 inode 7002239 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 68 namelen 14 name home-assistant filetype 2 errors 4, no inode ref root 5 inode 7063916 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 69 namelen 33 name Community_Applications_USB_Backup filetype 2 errors 4, no inode ref root 5 inode 7115094 errors 2001, no inode item, link count wrong unresolved ref dir 260 index 70 namelen 9 name nextcloud filetype 2 errors 4, no inode ref root 5 inode 7162647 errors 2001, no inode item, link count wrong unresolved ref dir 256 index 188 namelen 17 name TimeMachine_Karlo filetype 2 errors 4, no inode ref found 182835875840 bytes used err is 1 total csum bytes: 0 total tree bytes: 98664448 total fs tree bytes: 41385984 total extent tree bytes: 56918016 btree space waste bytes: 31632797 file data blocks allocated: 82555465728 referenced 13913096192 root@BGDunRAID:~#

My system is: ASRock C2750d4i Corsair 450W 16GB Crucial ECC RAM 512GB Crucial SSD (cache) 4x 4TB WD Reds 2x 8TB WD Red 1x 8TB WD Red (parity) It all started today. I installed nextcloud, and noticed that the port was closed. I thought if I reboot my server would fix the problem. After rebooting the server, I created a much bigger issue. The cache drive shows unmountable. All my docker images, appdata, and VMs are all on my cache drive. This is exactly what I did: 1. stopped all my docker containers 2. stopped all my VMs 3. stopped the array 4. rebooted 5. after the reboot, started the array 6. noticecd that cache drive is unmountable I did some more troubleshooting. I powered down the server and unplugged and replugged the cache disk cable, but no luck. It is still showing unmountable

Hello guys, Pretty new with unraid and docker. I enabled docker and install the plexmediaserver app. When I opened the webui, the plex webpage was stuck in "Looking for servers". I have the plex set to host. My unraid version is 6.3.2. I am using the trial version of unraid and haven't subscribed to plex yet. I just want to see if this is going to work, so far have not gotten any luck yet. I watched some youtube videos, and it looks pretty straight forward, but in my case it is not. Any help would be greatly appreciated

Hello guys, I am new here and new to unRAID. I am in a process of building my first NAS, so far I have put together my small build. AsRock C2750D4i mobo/cpu SilverStone DS380 case 2x WD Red 4TB I got this working last night, and installed everything into the case. Now, I am going to put this case in my network cabinet for physical security reason. I have two questions. My motherboard IPMI supports interface bonding, and I know unRAID supports it, too. Do I need to enable the IPMI network bonding and unRAID would see it as one interface or leave the IPMI to default and do the bonding in unRAID? Oh I forgot to mention, do I have to configure the switchport to trunk or access port to connect to unRAID? Also, it is unrelated to unRAID, but I am a little concern about the heat issue since the CPU is passively cooled. I am thinking to get a Nortua 60x60mm fan and attach it to the heatsink, but not sure how. Should I use an thermal conductive adhesive tape to attached the fan to the heatsink or a different type of tape? Thanks