joshallen2k

Members
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

0 Neutral

About joshallen2k

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Thanks. Didn't know that. Win11 now running exactly per @SpaceInvaderOne. Updated and running fine.
  2. I've followed the instructions to a T. However once starting the VM and opening a VNC window I get the UEFI shell and nothing proceeds. What am I doing wrong? All settings are per the video.
  3. Yes, it was the @SpaceInvaderOne tutorial that I originally used for the setup. I changed my network to bridge and had the same error. I just used the troubleshooting guide https://www.linuxserver.io/blog/2019-07-10-troubleshooting-letsencrypt-image-port-mapping-and-forwarding which suggests using the Nginx docker to test connectivity and forwarding. Using nginx seems to work - I can reach the standard web page, and when I use a port checker, port 80 and 443 are open/green. When I delete the nginx docker and launch swag (using the same port forward and network settings), then port 80/443 are s
  4. Thanks for the clarification, but I'm still having difficulty. With the setup in the screens below, the SWAG docker container fails to start with Execution Error 403. Note the fixed IP I specified in the template is the IP of my Unraid server (192.168.2.229). The IP of "ATLANTIS" is 192.168.2.229
  5. Thanks for the reply. I double checked my WAN IP and its fine. For some reason my router when I specify an IP it resolves to the host name. WHat I'm unsure of is where you say to add my custom IP's again in the SWAG template. I don't think I specified anything there before. What should it be?
  6. Hi all - I'm having difficulty troubleshooting what looks like a port forwarding issue. My SWAG reverse proxy was working fine until a week ago. I was getting BTRFS errors in my docker.img, so deleted it and created from new. After reloading my apps, I noticed my reverse proxy was not working anymore. In my SWAG logs, I saw this error: int: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound c
  7. Thanks. I was afraid of that. Any suggestions on an alternative for Eth that would make sense to mine with this card?
  8. I'm having trouble with PhoenixMiner. Not connecting to any shares on Nanopool. I've tried a number of settings/suggestions from online posts, but no luck. Here is what the logs keep repeating: Eth: Mining Unknown on >ssl://eth-us-east1.nanopool.org for 0:01 Available GPUs for mining: GPU1: AMD Radeon (TM) RX 460 Graphics (pcie 1), OpenCL 1.2, 4 GB VRAM, 16 CUs GPU1: 39C 0% 7W GPUs power: 7.1 W Current -gt 15 Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales) Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00% Eth: Average speed (5 min): 0.
  9. I fixed this by disabling proxy inside Cloudflare. I'm not entirely sure why this worked, as my previous SWAG instance ran fine with Cloudflare proxy turned on...
  10. Hi - I'm having trouble with my swag setup. With a fresh docker install, my logs show challenge failed for my subdomains. They are properly setup in Cloudflare and my port forwarding is correct (forwarding 80 to 180 and 443 to 1443). I've attached my logs. Any suggestions? swaglog.txt
  11. Hi, i have the docker running, but it doesn't seem to be generating any Eth. Does this log help at all? [95mGPU1: 38C 0% 8W GPUs power: 8.2 W [96mEth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01 [96mEth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01 Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01 Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01 Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01 Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01 Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:02 [95mGPU1: 38C 0% 8W GPUs power: 8.2 W [96mEth speed: 0.000 MH/s, share
  12. Hi - I am having trouble getting duckdns/swag/wireguard to work for me. I've followed a number of guides but can't get it going. Symptoms: - Going to https://MYSERVER.duckdns.org - cannot reach server. Specific ports (e.g. :8989 for Sonarr) do not work either - Wireguard peers when service enabled cannot reach any IPs. I believe I have configured all correctly, and port forwarding for Wireguard appears properly enabled. Where would I start to troubleshoot this? All help appreciated.