Iceman24

Members
  • Content Count

    61
  • Joined

  • Last visited

Community Reputation

13 Good

About Iceman24

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I'm getting this warning from Fix Common Problems and the fix doesn't stop the scan from still reporting the warning. Fix appears to have been applied okay. Template URL for docker application AdGuard-Home is not the as what the template author specified.The template URL the author specified is https://raw.githubusercontent.com/sgraaf/Unraid-Docker-Templates/main/adguardhome/template.xml. The template can be updated automatically with the correct URL.
  2. I'm strategizing for the DNS servers I may use in future, was wondering if it was possibly to specify a different DNS port for unRAID's settings? Looking at the settings, it just asks for DNS server like most devices would, no port section. I know from other devices some don't allow simply adding a colon and the port, that they just want the DNS server and they use the default port 53 or whatever other one they may use.
  3. Nice. What is not working on it?
  4. Thanks. I will give it a go, just need to decide on SSD.
  5. I have an unRAID build already, using HDD's as array and SSD as cache, but this 2nd one I'm doing has more simple needs and less storage capacity, so I was wondering if there was a reason this wouldn't be ideal. My thoughts were to put a 1-2TB SSD as the only array drive in lieu of 1-2 HDD's as array. I don't need much storage capacity, so SSD's are cheap enough that price wise it'd be around the same anyways. I would use SSD as the main drive for everything. The 1 HDD, only other drive in system I would use as a backup drive using Unassigned plugin. It could be external, but I want to keep it
  6. How are you paying $50 a year? I see $100 if paid annually.
  7. Has there been any progress on getting this to work? I was going to try it since I could self-host, but I wouldn't be willing to do a VM just for it.
  8. If that Docker is setup to only run on HTTP, the scheme needs to be HTTP. You can still force SSL in the SSL tab, but the scheme must be whatever the Docker is setup to use. Also, I would recommend blocking out your domain. Nobody needs to know that to help anyways.
  9. You're welcome. Make sure this area of your config.php looks like this. 'trusted_domains' => array ( 0 => 'unRAIDIP:NextcloudPort', 1 => 'nextcloud.server.com', ), 'trusted_proxies' => array('unRAIDIP'), 'forwarded_for_headers' => array('HTTP_X_FORWARDED_FOR'), 'dbtype' => 'mysql', 'version' => '18.0.0.10', 'overwrite.cli.url' => 'https://nextcloud.server.com', 'overwritehost' => 'nextcloud.server.com', 'overwriteprotocol' => 'https',
  10. I'm not in a position to do anything other than say check my post about 10 back with how to fix this. Have to add line in "default" to file.
  11. Interesting. I never knew anyone included "php7" in the command and it worked for me without it.
  12. Thanks, that did work. Odd thing though is that when I did so, it removed the ovewritehost from the file entirely and moved the overwrite.cli.url all the way to the bottom, but kept it. So it seems the overwritehost was the only one needing commenting or removal, as it was removed upon reboot and the other one was kept, but moved to bottom of file.