• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Ruthalas's Achievements


Apprentice (3/14)



  1. Apologies! I thought I had manually tried that previously, and hadn't realized the listing in unRAID was still incorrect. I can reach the webUI now. Thank you for your patience. Edit: Got this all set up and had a single issue- Remote sessions would disconnect after about a minute. To resolve this I followed the advice given here.
  2. Appreciate it! Configuration: Name: MeshcCentral Repository: uldiseihenbergs/meshcentral WebUI: http://[IP]:[PORT:466]/ Network Type: Bridge Console shell command: Shell Privileged: Off Port: Container 80, Host 82, TCP Port (UI): Container 8443, Host 455, TCP Port (Agents): Container 443, Host 466, TCP Path (Data): Container /home/node/meshcentral/meshcentral-data, Host /mnt/user/appdata/meshcentral/data/, Read/Write Path (Files): Container /home/node/meshcentral/meshcentral-files, Host /mnt/user/appdata/meshcentral/files/, Read/Write Path (Web): Container /home/node/meshcentral/meshcentral-web, /mnt/user/appdata/meshcentral/web/, Read/Write Path (Backup): Container /home/node/meshcentral/meshcentral-backup, /mnt/user/appdata/meshcentral/backup/, Read/Write If the log you refer to is the one linked to in the unRAID UI, then this is the contents: (If there's another within the docker, let me know where it exists and I will fetch it!) Installing archiver@4.0.2... Installing otplib@10.2.3... MeshCentral HTTP redirection server running on port 80. MeshCentral v0.7.50, LAN mode. Server has no users, next new account will be site administrator. MeshCentral HTTPS server running on port 443. I have removed the container/image and deleted it's folder in appdata and recreated it (with the above settings) and the result was the same.
  3. Unfortunately I haven't been able to get it to work. I've rebuilt the container with the configuration above and still can't access the webUI. If you have any further troubleshooting steps, let me know. Regardless, thanks for the help so far!
  4. Ah! I see. I naively copied what was visible in your first screenshot. Thank you for the correction. I've corrected the paths to match, and updated the container. I still can't access the webUI, but can modify the config file directly. My config file currently contains the default information- I anticipated configuring it from the WebUI. Should I be configuring it via the config file instead? Thanks for your help!
  5. I get ERR_EMPTY_RESPONSE at IP:466. Should the meshcentral config file be in one of the configured appdata folder? The four folders I configured are all empty.
  6. I've configured it according the the screenshot above, but can't access the webUI, is that expected behavior? Logs for the container look good (see below), but I get connection refused when I try to hit IP:455. There isn't anything in the folders I configured, but perhaps that's because I haven't been able to set anything up yet? Thanks for your work on this! Installing archiver@4.0.2... Installing otplib@10.2.3... MeshCentral HTTP redirection server running on port 80. Generating certificates, may take a few minutes... Generating root certificate... Generating HTTPS certificate... Generating MeshAgent certificate... Generating Intel AMT MPS certificate... MeshCentral v0.7.30, LAN mode. Server has no users, next new account will be site administrator. MeshCentral HTTPS server running on port 443.
  7. That's correct. I'll run another check to confirm. Thank you very much, I appreciate the assistance.
  8. I am not sure how I'd determine when the sync error started. Is that something I can find in logs? Gotcha. I believe I neglected to turn it off after testing it some time ago. Thanks for letting me know.
  9. My parity checks are currently set to write corrections to the disk, so I think I am good on that front. In that case, should I re-run the check and see if it turns out correctly this time? (Edit: Yes, the new drive is ~4TB larger than the old one.)
  10. I'd appreciate some help, I am pretty worried about this. Thank you! Summary: Swapped in a new (larger) parity drive (sdd) Used old parity drive as data disk and removed old data disk Parity check ran and returned many errors Is the correct course of action to replace the new drive? Longer story: I recently purchased a 12TB drive to increase the size of my parity drive. After purchase I ran the WD Data Lifeguard Diagnostic on it. It failed the first time, and I realized the drive was situated in the hot exhaust of my case and was hot enough to burn my fingers. After moving it, I ran the diagnostic again and it passed, both quick and extended tests I then zeroed the drive with the same tool with no issues. I then performed the parity/data shuffle as per the wiki, and everything seemed to go smoothly (it took three days or so). A scheduled parity check was initiated about a day after the rebuild, and ran for two days; when finished it returned 976214698 errors. SMART stats seem to indicate the new drive is indeed new, and has no issues. The array was in use during the parity check (I think that's fine?). There was a temperature warning for a different disk in the array once during the rebuild, but it is physically distant from the new disk in question. Diagnostic files are attached. My immediate thought is that the drive is bad, and I should have heeded the issues it had when I ran tests when it was warm. That being the case, I believe simply returning this drive and replacing it immediately with another would be the correct action? I wanted to post to make sure I wasn't missing anything, and to check that replacing the parity disk is the correct course of action. If there's any other info I can provide, let me know! Thank you for your time, Ruthalas
  11. Current situation: When a docker has an update that can be applied, it can be somewhat difficult to track down it's home repository and read through what changes have been made. Ex: Click docker icon, determine whether 'more info' or 'project page' links to a repo rather than a descriptive website, if a dockerhub page is linked search it to find a link to the github repo, navigate to releases, etc. Suggested change: Add a 'View Changes' button next to 'Apply Update' that links to the base repository the docker installation pulls from, specifically to the change history section if present on the site. This could be supported by having another field to fill when creating templates that is specifically for the change history portion of whatever site the base repo is pointing to, or by guessing based on the domain (ex: you can append '/releases' to the github link). In theory, I'd like to make this check for every update I make to important dockers, so having a direct link to the releases or change history for these projects would be very convenient.
  12. I second that request (for restore functionality). No hurry, but that would be a valuable addition.
  13. It looks like my friend found a solution. u/Toastman89 suggested the following solution on Reddit:
  14. Good afternoon folks, I have been trying to assist a friend in setting up a windows VM, but they've run in to an issue that I haven't seen before. As far as I can tell, the issue is that, regardless of which virtio driver package they select (and download) in the VM Manager pane, when they get to the "load driver" step in a Windows (7/10) setup, the mounted drive has the 0.1.1 virtio driver package. (This package doesn't work, I assume because it is old and outdated.) I've had him restart the server, toggle the VM Manager off and on, and select alternate (newish) virtio driver packages. But in each case, when he gets to the "load driver" step, the 0.1.1 version is mounted. Can anyone provide guidance on how to resolve this? If you need diagnostic logs, please let me know and I'll try to get them from him. Edit: Pictures and Video of his configuration prior to issue resolution, for posterity.