Everything posted by jfoxwoosh
-
AVAHI or Bonjour Across VLAN's
Thank you, @kp74508 Your instruction was really helpful. My Linux Mint VM that sits on a different vlan can finally have access to the main network's printer with full print&scan functions. To anyone visiting this thread in the future: I had already created a vlan for VM and only needed to enable this network within the docker setting menu. No need to manually create the network using terminal.
-
(SOLVED) Ryzen 5900X MCE: Hardware Error - Should I be concerned?
I have been consistently getting this hardware error. Some googling of this, seems to point to early Ryzen CPU defect. However, I haven't found any other report like this online for 3rd gen Ryzen (5900X). Should this error be of concern and perhaps required a warranty service with AMD? My system diagnostics is attached. diagnostics-20220731-1416.zip
-
[Support] lnxd - PhoenixMiner
I have both 6800 and 6600xt installed in the system. The container only mines with 6800. How can I tell the container to use the 6600xt as well?
-
Anyone interested in a docker container for crypto mining?
@lnxd, this discussion thread might be old, but I don't want to ask question and clutter the phoenixminer docker support thread, which works awesome by the way. Thank you. Do you have any additional plan to dockerize other mining software like teamredminer, nbminer, etc? I might be thinking too much ahead, but I am wondering about what altcoin to mine after ethereum switch over to PoS.
-
[Support] lnxd - PhoenixMiner
@eagle470, based on the pool address, you are trying to mine ravencoin? My understanding is that Phoenixminer only mines for ethereum.
-
Uncast: A New Podcast from Unraid
Yes, this give me an idea to create a new free account with plex, which is not tied to a server in anyway, and I tried adding the uncast podcast by url. I am still experiencing the same error message. I guess this is a bug from the plex company's end.
-
Uncast: A New Podcast from Unraid
Thanks for your response. I have PlexPass as well, and it kept giving me the same error message saying "something went wrong. an unexpected error occurred." I tried different apps (ios/android) and multiple browsers, but no luck. Found this thread on the plex forum and wondering if this is related to my problem. @ljm42, which plex docker are you using? I am using the linuxserver's plex docker.
-
Uncast: A New Podcast from Unraid
I couldn't use the link to add the podcast to plex. Anyone can help?
-
WireGuard quickstart
Anyone using Untangle or OPNSENSE for the firewall? Based on my evaluation of these two software, there is no "bypass firewall rule..." checkbox like pfsense has to allow for asymmetric routing. How can I achieve the same function as the bypass by using additional policy/NAT/routing rules?
-
HandBrake
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
@FlippinTurt Sorry to waste your time. The answer to my problem is right in front of me this whole time. "NOTE 3: UnRaid network settings DNS server cannot point to a docker IP." When I set the pihole address in the "LAN DHCP" menu of the router, it automatically updated the unRAID's network DNS server to the pihole's IP. The solution is to strictly use router's "WAN" DNS server setting and leave the DHCP's DNS menu blank (for asus router at least).
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
@FlippinTurt Thank you for helping. I tried many things, and sort of able to recreate the problem. 1. Docker and router dns server all setup and working properly 2. Server reboot, the pihole-dot-doh stopped functioning. 3. At this point, I can get it to work again by setting the router’s dns server back to known server such as 1.1.1.1 or 8.8.8.8, etc., and restart/reinstall the docker. 4. Change the router dns back to the pihole-dot-doh address. Somehow the pihole-template docker is immune to the server reboot. I still need to experiment a few variables such as setting the pihole ip address in my asus router’s “LAN DHCP” menu or the “WAN” menu.
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
Docker was working fine for awhile, but last night I restarted the server and could no longer access the web UI anymore. I pinged the docker's ip (192.168.1.2) address and it is responding, and I checked my router's device list and can see the static ip of docker is there. I went ahead and download the "pihole-template" docker and that worked just fine. Not sure what happened after the reboot.