kingJahfy

Members
  • Posts

    31
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

kingJahfy's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. I resolved this by editing the `/boot/config/ident.cfg` file on the flash drive (via SSH). Changing `USE_SSL` from `auto` to `no` then running the `reboot` command. `use_ssl` is not a command. Thanks for pointing me in the right direction. root@bluebox:/# use_ssl no -bash: use_ssl: command not found root@bluebox:/# fd use_ssl ^Croot@bluebox:/#
  2. Unable to access Unraid server via web interface. I was forced to change my static IP address. Before replacing my broken router I changed the IP to non-static (DHCP provided). After updating the configuration and rebooting everything I am unable to access the server via web/GUI. I've attached my diagnostics. How can I change to a static IP address from the terminal and reset the redirect to the new IP address? $ http --all http://192.168.1.92 HTTP/1.1 302 Moved Temporarily Connection: keep-alive Content-Length: 138 Content-Type: text/html Date: Sat, 02 Jul 2022 18:54:12 GMT Location: https://c6c25df20c1fd154bcb8f1adc592a497e3c1d910.unraid.net:443/ Server: nginx <html> <head><title>302 Found</title></head> <body> <center><h1>302 Found</h1></center> <hr><center>nginx</center> </body> </html> Context: Router died and got a new ISP. Figured I would use them for DHCP and move over to business class wireless access points. Only problem is they (ATT Uverse) dont allow you to use the 10.x.x.x block. So I can't configure my server with the same IP address. bluebox-diagnostics-20220702-1432.zip
  3. The root cause in my case are the firewall rules for the ATT router. My personal router (connected to ATT) has a firewall but I have to think hard about adjusting any firewall rules and enabling port triggering.
  4. Note that I got past the WebUI issue by doing the following "The alternative to this is to set env var 'STRICT_PORT_FORWARD' value to 'no', this will then skip any port forwarding and allow you to connect to ANY PIA endpoint independent of whether it supports port forwarding or not (not recommended)." However, the original issue is still there. At this point I'm wondering if its an ISP policy causing port forwarding issues.
  5. A bit of background on my network setup: internet -> att garbage router -> personal router -> unraid unraid -> technitium dns server (at personal router) -> att router -> internet Perhaps if I were to connect to the same host as your working connection I would be able to bypass these issues. Please share the IP address being used in your connection to ca-toronto.privateinternetaccess.com. You can do this by opening the console for the container and running the following command. curl ifconfig.io The hope is I can connect If I change the hostname in the CA Toronto.ovpn file to the ip address you share.
  6. Unfortunately for me, now the UI doesn't work.... with CA Vancover 😦 2020-09-08 15:51:26,782 DEBG 'start-script' stdout output: [info] PIA endpoint 'ca-vancouver.privateinternetaccess.com' is in the list of endpoints that support port forwarding 2020-09-08 15:51:26,782 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-toronto.privateinternetaccess.com [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [info] Attempting to get dynamically assigned port... 2020-09-08 15:51:47,137 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 12 retries left [info] Retrying in 10 secs... Stating the obvious --- This frustrating, PIA is very popular and i've had little issue with the service until now
  7. Please assist, how can I determine if this is a port forwarding issue or a DelugeVPN issue. Unable to download files using DelugeVPN with PIA and server, remote ca-toronto.privateinternetaccess.com port 1198. Torrents stuck in state downloading. See attached deluge logs for more info. deluge-web.logdeluged.log Attempts to resolve this issue Changed from CA Toronto to DE Berlin. Issue(s) remains. Attempt to enable port forwarding - tldr; Issue remains: Enabled port forwarding on archlinux docker container running OpenVPN as directed by PIA support portal. OS details are as follows, note all commands are ran from within the DelugeVPN docker container. sh-5.0# cat /etc/os-release NAME="Arch Linux" PRETTY_NAME="Arch Linux" ID=arch BUILD_ID=rolling ANSI_COLOR="38;2;23;147;209" HOME_URL="https://www.archlinux.org/" DOCUMENTATION_URL="https://wiki.archlinux.org/" SUPPORT_URL="https://bbs.archlinux.org/" BUG_REPORT_URL="https://bugs.archlinux.org/" LOGO=archlinux sh-5.0# uname -r 4.19.107-Unraid Results of running `port_forwarding.sh` are as follows. sh-5.0# chmod +x port_forwarding.sh sh-5.0# ./port_forwarding.sh Loading port forward assignment information... Port forwarding is already activated on this connection, has expired, or you are not connected to a PIA region that supports port forwarding After running the above command the docker container was restarted, none of the downloads became active. I am attempting to download ubuntu and torguard's check my torrent ipaddress.
  8. I had an extra 1TB hdd drive laying around that matched the size of the 1TB ssd that I recently purchased and thought it would be better to make a pool for redundancy than using a single drive. As indicated at https://wiki.unraid.net/UnRAID_Manual_6#Creating_a_Cache_Pool - "Pooling multiple storage devices together ensures that data protection is maintained at all times, whether data is in the cache or the array" I bought a 1TB ssd because the previou 250GB ssd was regularly over 75% usage and there was a discount.
  9. Thanks for the quick responses. I will backup and recreate the cache pool with another SSD. I believe I understand how to do this but to be doubly sure, I don't make a mess of things again, are the steps documented in the FAQ or on the wiki?
  10. Recommended next steps? The sde1 drive of the server cache is has write, read, and corruption errors. The HD drive is the secondary drive in a cache pool with an SSD. I've followed the instructions in the FAQ for monitoring btrfs pool. Here are the steps I've taken: Check btrfs stats confirmed errors Check cable connections (same cables) Run btrfs scrub (clicking on cache from main) While scrub is running I see that there are "uncorrectable errors" on sde1. The drive in question also fails a SMART test. What would you recommend as next steps? is it time to replace the drive and cable? Background: These errors started happening after replacing a smaller SSD in the cache pool. sde1 was not touched. bluebox-smart-20200820-0925.zip bluebox-diagnostics-20200820-0924.zip
  11. The Fix common problems plugin alerted me to a warning, "You may experience slow read/writes to cache2." Attempts to fix the issue are unsuccessful and a `SG_IO: bad/missing sense data` error is shown. I ran the first command to get an understanding of the drive then the next to enable write caching, unsuccessfully. Any advice on fixing this issue? root:~# hdparm -I /dev/disk/by-id/ata-WDC_WD10EARX-00N0YB0_WD-WMC0T0478211 /dev/disk/by-id/ata-WDC_WD10EARX-00N0YB0_WD-WMC0T0478211: ATA device, with non-removable media Model Number: WDC WD10EARX-00N0YB0 Serial Number: WD-WMC0T0478211 Firmware Revision: 51.0AB51 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 root@:~# hdparm -W 1 /dev/disk/by-id/ata-WDC_WD10EARX-00N0YB0_WD-WMC0T0478211 /dev/disk/by-id/ata-WDC_WD10EARX-00N0YB0_WD-WMC0T0478211: setting drive write-caching to 1 (on) SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 61 40 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 write-caching = 0 (off)
  12. Thanks for your help. I've resolved the issue by deleting `/mnt/user/system/docker/docker.img` and restarting the server.
  13. Attached the diagnostics download. The docker.txt file in the logs directory is empty. Do you recommend deleting `/mnt/user/system/docker/docker.img`? Not seeing docker images for Calibre using the `docker images` command.
  14. Unable to get past the following error While attempting to add the Calibre container. Any ideas on how to resolve this issue? root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='calibre' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'GUAC_USER'='<redacted>' -e 'GUAC_PASS'='<redacted>' -e 'PUID'='99' -e 'PGID'='100' -p '6580:8080/tcp' -p '6581:8081/tcp' -v '/mnt/user/ebooks/calibre_lib/':'/books':'rw' -v '/mnt/user/downloads/':'/import':'rw' -v '/mnt/user/appdata/calibre':'/config':'rw' 'linuxserver/calibre' Unable to find image 'linuxserver/calibre:latest' locally latest: Pulling from linuxserver/calibre 739c8d67eaa9: Already exists 48e5522c5960: Already exists 1a517b165cc5: Already exists 4b343106a4e7: Already exists c4e91587e6f5: Pulling fs layer 400a866308bb: Pulling fs layer 55b380095b7a: Pulling fs layer fb90632fd9d3: Pulling fs layer 51d418a717bc: Pulling fs layer a6f26d37fde7: Pulling fs layer 7efae67fbdca: Pulling fs layer a6f26d37fde7: Waiting fb90632fd9d3: Waiting 7efae67fbdca: Waiting 51d418a717bc: Waiting 400a866308bb: Verifying Checksum 400a866308bb: Download complete 55b380095b7a: Verifying Checksum 55b380095b7a: Download complete 51d418a717bc: Verifying Checksum 51d418a717bc: Download complete c4e91587e6f5: Verifying Checksum c4e91587e6f5: Download complete 7efae67fbdca: Verifying Checksum 7efae67fbdca: Download complete fb90632fd9d3: Verifying Checksum fb90632fd9d3: Download complete c4e91587e6f5: Pull complete a6f26d37fde7: Verifying Checksum a6f26d37fde7: Download complete 400a866308bb: Pull complete 55b380095b7a: Pull complete /usr/bin/docker: failed to register layer: ApplyLayer unexpected EOF stdout: {"layerSize":160707934} stderr: . See '/usr/bin/docker run --help'. The command failed.
  15. Awesome, Thanks to everyone for the helpful information.