Everything posted by destrugter
-
[Support] kru-x - Godaddy ddns
Does this support wildcard subdomains? Edit: Sorry I just read over the previous posts and figured out how to do it. Thanks!
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
- [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
I'm having the following issue when trying to renew my certificate. I own the domain and have a Dynamic DNS service that updates the domain to point to my IP once per day. It resolves correctly.- [Plugin] CA Appdata Backup / Restore v2
I'm having an issue where I put a mariadb docker on another drive and it's not included in the resulting backup archive- [Support] binhex - rTorrentVPN
I'm not trying to be bothersome, but I'm still having issues and if there's anything else I can do or any other kind of information you need please let me know. I've went through a complete reinstall of unraid plus all of my docker containers and stuff. I started from fresh settings too (as in, I renamed the old folder so that the docker would start with brand new downloaded files), the only thing I carried over was my array data. I do appreciate your time This line shows up, I'll look into it but maybe it's helpful for you 2018-08-22 17:35:21,321 DEBG 'rutorrent-script' stderr output: [NOTICE] [pool www] 'user' directive is ignored when FPM is not running as root [NOTICE] [pool www] 'group' directive is ignored when FPM is not running as root- [Support] binhex - rTorrentVPN
I'm an unraid user, downloads are saved to a folder on the array- [Support] binhex - rTorrentVPN
It doesn't matter which endpoint I choose, the result ends up being the same. Here's a new log from using CA Vancouver. I will note that this docker was working flawlessly until around Monday or so. I'm not sure if I downloaded an update to it. I don't know if that information helps but just wanted to note it in case it does help somehow. These are very well seeded torrents on prolific trackers. To test I had my friend add one to his client and it worked instantly for him. supervisor.txt- [Support] binhex - rTorrentVPN
I turned it on because that's what the FAQ told me to do and post the log. I don't know if it's not connecting to PIA, but it's not downloading/uploading torrents. What's happening is all of my torrents will just stop working completely. Sometimes when I restart the docker they will download for a little bit but eventually they will stop. They will sometimes come back on in the middle of the night when I'm sleeping.- [Support] binhex - rTorrentVPN
I'm having an issue where it seems that rtorrent isn't connecting to PIA. It keeps repeating the same message over and over again. I have the right login information, and I have the .ovpn file and certs in the openvpn folder supervisor.txt- Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
root@Tower:~# ls /dev/disk/by-id/ ata-ST4000DM000-1F2168_W300N23H@ ata-ST4000DM000-2AE166_WCD00SKM-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZRX5@ ata-WDC_WD80EFAX-68LHPN0_7SGEH6ZC-part1@ wwn-0x15347340737589170177x@ wwn-0x17869328123984629760x-part1@ wwn-0x7337873558900592640x@ ata-ST4000DM000-1F2168_W300N23H-part1@ ata-ST4000DM000-2AE166_WCD00W9K@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZRX5-part1@ ata-WDC_WD80EFAX-68LHPN0_7SGGS10C@ wwn-0x15347340737589170177x-part1@ wwn-0x2448360361219477504x@ wwn-0x7337873558900592640x-part1@ ata-ST4000DM000-1F2168_W301BFZE@ ata-ST4000DM000-2AE166_WCD00W9K-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E5RF7ZFA@ ata-WDC_WD80EFAX-68LHPN0_7SGGS10C-part1@ wwn-0x16487769232413708288x@ wwn-0x2448360361219477504x-part1@ wwn-0x8009008642695254017x@ ata-ST4000DM000-1F2168_W301BFZE-part1@ ata-ST4000DM000-2AE166_WCD01D8E@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E5RF7ZFA-part1@ usb-SanDisk_Cruzer_Glide_20051941900F434249FC-0:0@ wwn-0x16487769232413708288x-part1@ wwn-0x2674452748132438016x@ wwn-0x8009008642695254017x-part1@ ata-ST4000DM000-1F2168_Z301EWPM@ ata-ST4000DM000-2AE166_WCD01D8E-part1@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4E2074065@ usb-SanDisk_Cruzer_Glide_20051941900F434249FC-0:0-part1@ wwn-0x16930046281319993344x@ wwn-0x2674452748132438016x-part1@ wwn-0x8049149434923208704x@ ata-ST4000DM000-1F2168_Z301EWPM-part1@ ata-ST500DM002-1BD142_Z3TS29S3@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4E2074065-part1@ wwn-0x10710563513610293248x@ wwn-0x16930046281319993344x-part1@ wwn-0x4942871422373482496x@ wwn-0x8049149434923208704x-part1@ ata-ST4000DM000-1F2168_Z3066X52@ ata-ST500DM002-1BD142_Z3TS29S3-part1@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4EME6RLLH@ wwn-0x10710563513610293248x-part1@ wwn-0x17180219197074984960x@ wwn-0x4942871422373482496x-part1@ wwn-0x9493789144843964417x@ ata-ST4000DM000-1F2168_Z3066X52-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0AHA407@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4EME6RLLH-part1@ wwn-0x12063343908222947328x@ wwn-0x17180219197074984960x-part1@ wwn-0x5796585026736902144x@ wwn-0x9493789144843964417x-part1@ ata-ST4000DM000-1F2168_Z306BCX1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0AHA407-part1@ ata-WDC_WD80EFAX-68LHPN0_7SG6BAPC@ wwn-0x12063343908222947328x-part1@ wwn-0x17553825102953598977x@ wwn-0x5796585026736902144x-part1@ ata-ST4000DM000-1F2168_Z306BCX1-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0XYDPLE@ ata-WDC_WD80EFAX-68LHPN0_7SG6BAPC-part1@ wwn-0x12945688142666682368x@ wwn-0x17553825102953598977x-part1@ wwn-0x604058783246864385x@ ata-ST4000DM000-2AE166_WCD00PES@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0XYDPLE-part1@ ata-WDC_WD80EFAX-68LHPN0_7SG7KANC@ wwn-0x12945688142666682368x-part1@ wwn-0x17824789654740815873x@ wwn-0x604058783246864385x-part1@ ata-ST4000DM000-2AE166_WCD00PES-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZPUA@ ata-WDC_WD80EFAX-68LHPN0_7SG7KANC-part1@ wwn-0x1477663287396159489x@ wwn-0x17824789654740815873x-part1@ wwn-0x6059429298605936640x@ ata-ST4000DM000-2AE166_WCD00SKM@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZPUA-part1@ ata-WDC_WD80EFAX-68LHPN0_7SGEH6ZC@ wwn-0x1477663287396159489x-part1@ wwn-0x17869328123984629760x@ wwn-0x6059429298605936640x-part1@- Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I do not have precede plugin. It also looks like it's messing it up to give all of the disks the same mount point as well.- Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Let me start off by saying I really love your plugin. I actually have 2 issues with Unassigned Devices plugin. Some information: I am running unRAID Server OS version 6.3.5 I am running Unassigned Devices plugin version 2017.09.20 I am using this Mediasonic ProBox HF2-SU3S2 4 Bay 3.5' SATA HDD Enclosure over this Inateck Superspeed 4 Ports PCI-E to USB 3.0 Expansion Card. I am providing this information in case it's relevant in helping me, since the devices may not act correctly towards the plugin. Now, my 2 issues: I am used to Unassigned Devices identifying my disks in the following fashion: {Model Number}-{Part Number}_{Serial Number}. For example: ST4000DM000-1F2168_XXXXXXXX. Instead what I'm getting is: 000-1F2168_000000000000 I am used to Unassigned Devices mounting my disks in the following fashion: {Model Number}_{Part Number}_{Serial Number}. For example: ST4000DM000_1F2168_XXXXXXXX. I attempted to change this by unmounting the disk, clicking on the mount point, entering it in that format, and pressing enter. It results in the disk being mounted like this: ST4000DM000 1F2168 XXXXXXXX. It doesn't matter the brand of the disk, all of my disks have appeared this way after recently reformatting the drives. I don't know if this is a bug or if it's simply the combination of devices I am using possibly misrepresenting the devices to unRAID and Unassigned Devices. This isn't something that kills the plugin for me, but if at all possible I would like to get the old behavior back for these devices. I plugged the disk into the same array device where my pool lives, and the disk almost shows up correctly. The Identification part shows up 100% the way I'm used to seeing it, but the mount point was just set to: ST4000DM000_1F2168 and the issue with renaming with underscores turning into spaces still exists here. This is why I'm unsure if it's a bug or the combination of devices misrepresenting the data to unraid and unassigned devices. Any and all help is appreciated. - [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)