gStone82

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

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

gStone82's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Twice in the last month my server has restarted unexpectedly with the Fix Common Problems plugin reporting Machine Check Events detected. After the first time I ran a full memtest with no results. Yesterday the server again restarted with MCEs. I've attached both a diagnostics pulldown as well as my syslog server backup which I setup after the first restart. Unfortunately the backup doesn't seem to have any useful information at the time of the restart (Dec 16 ~18:37) I believe due to it crashing entirely. Non-persistent syslog on recovery reports the following mcelog errors: Dec 16 18:38:01 gStone-Plex mcelog: failed to prefill DIMM database from DMI data Dec 16 18:38:01 gStone-Plex mcelog: Kernel does not support page offline interface Dec 16 18:38:01 gStone-Plex mcelog: Running trigger `unknown-error-trigger' (reporter: unknown) Dec 16 18:38:01 gStone-Plex mcelog: CPU 3 on socket 0 received unknown error Dec 16 18:38:01 gStone-Plex mcelog: Location: CPU 3 on socket 0 I have some suspicions that the error is related to VM virtualization but I can't confirm that. Any assistance in getting to the bottom of this would be much appreciated. I had assumed that my memory was going bad but after the memtest I'm beginning to think it is CPU related. Thanks! gstone-plex-diagnostics-20221216-2222.zip syslog-192.168.1.48.log
  2. Sure. See below. The DNS 1.1.1.1 in the config did not import into the peer DNS field. I'd assume because it is listed under interface rather than peer. I ended up using Torguard's provided DNS for Wireguard (10.9.0.1) found here: https://torguard.net/tgspec.php. Without the DNS entry clicking active button would set it to active for about a second before switching back to inactive. Nothing relevant showing in the Unraid logs. # TorGuard WireGuard Config [Interface] PrivateKey = ListenPort = 51820 MTU = 1292 DNS = 1.1.1.1 Address = 10.13.37.5/24 [Peer] PublicKey = AllowedIPs = 0.0.0.0/0 Endpoint = 107.181.189.38:1443 PersistentKeepalive = 25
  3. As far as I can tell no, it can not. WG tunnels don't show as an option under network bridge. For now just run Wireguard locally on the VM itself.
  4. Yup. I just tested it out today. Works great. Only issue I ran into was I needed to enter my VPN's DNS server into the Peer DNS Server field for the connection to activate.
  5. Any chance we can get an option to remove the colored circles? Also would be great if we were able to fix the webui's in place rather than having them randomly appear in different locations on every reload.