Jump to content

Prof93

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Prof93

  • Rank
    Newbie
  1. Just found that I had the same issue with both of my Windows 10 VM's. Changed the GPO setting as suggested and this resolved the issue after a reboot. Thank you for your suggestion.
  2. This worked for me. Shame we have to run a old version to fix it. Hopefully they will resolve the issues ASAP.
  3. Hi All, I found the reason that it would not resolve by the local dns name. The "Local TLD" setting was set to Local but by default pfSense uses Localdomain. So now when I enter BenUnraid it redirects me to the messy but very usable secure unraid.com url ***Just checked again and I was wrong says secure on host name until you login then it goes to not secure when logged in Never mind host IP address for now. ***
  4. Fair enough will stick with that for now until. I find some nice instructions on how to do it through lets encrypt or pfSense Thanks for the reply's If I find a easy solution other than using the built in method I will let you know.
  5. Hi, Thank you for the suggestions. I currently have my own domain name. If I wanted to make this secure internally I don't understand how that helps. I have other things such as Nextcloud etc using lets encrypt. Whats the easiest way of securing internal services with SSL ? I don't want to make the GUI externally accessible. Would using lets encrypt on the GUI but not adding the subdomain to fasthosts DNS solve this or is this the incorrect way of doing it ? Many Thanks, Ben
  6. Not really as I want to find the reason behind why it doesn't work for HTTPS securely via the host name. You now have the same issue that I have.
  7. Haha that is for sure a solution currently I have Heimdall installed and it has the IP set rather than the host name. But I was looking for a solution to it being secure via the host name. I also know how to bookmark. I am a IT tech so very computer literate. Just can't work out why it will not work with the hostname. Seems a odd setup the cert has lots of strange config. I kinda know the answer and that is because the hostname is not mentioned in the cert but I don't know if there is a way round this. Anyway hopefully someone knows how it works and can explain
  8. Yeah just to GUI. I am using a windows 10 computer running chrome. It is secure using the IP just not the host name so must be config ? The host name is a host override in pfSense so this could be the issue. This was the only way I could give it a host name as the server is static and outside of the DHCP pool.
  9. Hi All, Sorry if this has been resolved in this forum. Couldn't find it when looking maybe I was searching for the wrong thing. Basically I cannot be bothered to type or remember the ip of my server and would like to access it via the hostname. When I access it via the hostname I get a issue where the site is not secure. But if I access via the IP it works fine. I use pfSense as my firewall and have put the following into the dns resolver/custom settings : server: private-domain: "unraid.net" Probably something simple but hope you can help Many Thanks, Ben