Squid
-
Posts
28,770 -
Joined
-
Last visited
-
Days Won
314
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Squid
-
That's the way that br0 works. Any and all port mappings are ignored by docker itself.
-
Try rebooting. If that fails, then enable debugging mode within CA's settings, then after it fails, hit debugging on the CA screen and upload that file generated along with your diagnostics
-
Unlikely for this to have happened. You've probably at least forwarded 32400 for Plex, but a shortcut people take when they don't understand how to forward a port is to simply place a server within a DMZ... Alternatively, one of your clients has been hijacked -
Is this related? I can connect to all of the servers via MyServers dashboard remotely, but I cannot switch from one server to another via the drop down on the plugin..
-
Save backup of Flash Device Settings To Cloud Services
Squid replied to Gov's topic in Feature Requests
The unraid.net plugin automatically stores a backup (as it changes) to Limetech's own cloud storage. -
Since forever actually You have to manually edit the applicable file within /config/plugins/dockerMan/templates-user and remove the line <TemplateURL>....</TemplateURL>
-
Mar 25 09:24:05 UNRAID01 unassigned.devices: Disk with serial 'WDC_WD40EFRX-68N32N0_WD-WCC7K3EV27PU', mountpoint 'WDC_WD40EFRX-68N32N0_WD-WCC7K3EV27PU' is set as passed through. You're passing it through so that a VM can manage it.
-
A write to the drive failed. That's a given since unraid disabled the drive. Most of the time this is because of poorly connecting the drive. SMART report from the drive would be helpful.
-
The only access to SSH is via root, and it has to have a password set
-
[6.9.1] Issue after upgrade - no GUI / SSH / SMB Shares
Squid replied to sfaruque's topic in General Support
So I'm a bit confused... But your diagnostics show that you logged into the GUI (not from the command prompt) Mar 25 14:41:39 Dhaka webGUI: Successful login user root from 192.168.1.10 And then roughly an hour later it looks like you turned off the system -
Part of it is the differing units (GB vs GiB) between what the dashboard says (500GB drive) vs the commands (465GB drive) du --si will give a larger value, and the rest is probably taken up by metadata storage
-
All overclocks (XMP included) introduce instability into any system and should be avoided.
-
Then deleting it should get rid of it permanently. You definitely do NOT want to have Plex being installed as a plugin. If it comes back, post your diagnostics
-
Do you still have a PhAzE plugin installed?
-
Is your server in the router's DMZ? What ports have you forwarded to the server?
-
The only shares that have files on the cache are all set to be prefer, which means that mover will try to move them TO the cache drive from the array (appdata, domains, whatever share starts with "U") What space are you expecting to be seeing available? Possibly, your VM vdisk isn't "sparse", so it has grown to be the maximum size that you've set (by default, it never shrinks, and only grows). See here: https://forums.unraid.net/topic/51703-vm-faq/?tab=comments#comment-557606
-
Tools - Diagnostics. Post entire zip file
-
Post your diagnostics, as Unraid does NOT remember any devices etc from one boot to another
-
Network failure implies a problem within Settings - Network. Could be as simple as a typo on an address, or a completely wrong setup. Diagnostics would help the network people help you.
-
Appdata restore has to save the log somewhere. If docker is enabled, then it saves it on a drive (inside the docker.img file) If it's not enabled then it has to store it in RAM.
-
Explore the flash drive via the network Config / Shares folder. Delete them like any other file. There's no harm in leaving them, except that it makes diagnostics a PITA
-
Looks like all those .cfg's were created by Ransomware Protection (long deprecated) and can be very safely deleted (Squidbait-*)
-
Click the question mark
-
Sure about that? Enabling VT-x and not just VT-d? Mar 19 11:57:52 Tower kernel: x86/cpu: VMX (outside TXT) disabled by BIOS https://askubuntu.com/questions/1297433/vmx-outside-txt-disabled-by-bios
-
That's what I thought. I've seen some of the postings around for China regarding this, and at least one of them suggested to edit and save the file /usr/local/emhttp/plugins/community.applications/include/paths.php I'm suspecting that you've done this, have the system set up to re-copy that file on a reboot, and your saved copy is now incompatible with all versions of CA going forward. IE: As far as I'm concerned, the error message that you're seeing is impossible on a non-modified copy of CA
