I just re build my main server. Truenas was installed for 2 years as a vm on proxmox and another 2 on bare metal.
I recently decided to uninstall proxmox and install a new truenas scale (25.04) on the same server as a bare metal installation .
All is working Almost well.
The only issue is once i started my server and the try to access for the first time from another device I get the dreadful message that the connection to this server is not secure.
i click on the button to accept the risks.
Then when i try to access the server again at a later time i get the login screen immediately i get: “not secure https://192.168.1.124/ui/dashboard” (the https is in orange and has a bar across it)
And everytime i try to access the server i need to insert my credentials because google autofill is not working.
This also happens when i try to access Jellyfin server
To note during this period i had to change my router
thank you @swc-phil and @dan or taking time from your weekend to respond.
the url i posted is my truenas scale set up on bare metal.
my truenas URL from tailscale is 100.94.20.55 and this node i set up as an exit node with subnets and is connected.
As an answer to your 1st question on my proxmox my truenas installed as a vm had the same URL as the one mentioned in my post 192.168.1.124
As an answer to upr 2nd question is no .
Truenas scale was installed from scratch on the bare metal server.
answer to question 3 Jellyfin in both cases (truenas as a vm or as bare metal) was installed as an app within truenas
on my current router (as with my old one) truenas was never iwas in dhcp. It was always both in the truenas configuration and on the router as a static ip address.
@dan
point 1 the domain name on all my truenas installation was / is WORKGROUP for all machines on my network . Is this what you mean?
point 2 never had to do this before How do i obtain a trusted cert?
point 3 once i get the trusted cert where do i i install it?
point 4 I always access my nas by the ip address (shortcut). I would not know how to access it via domain name
Once again thank you all for taking the time from your precious weekend to assist me.
I forgot to mentioned than in the tails scale configuration i have a published server url of 192.168.1.0 (did not work) and today i tried changed it to 192.168.1.124:8096 still did not work
So, did I get it correctly that you were accessing your truenas via the same https://192.168.1.124/ and didn’t get any errors and also have had your login/pass auto-inserted?
I’m accessing via 192.168.1.124 in the google search bar the https comes later. I do not know why https in lieu of http.
and the credentials need to be inserted.
BTW i just added as additional domain truenas.local and this worked and it did save my credentials. This is a step forward however it still when i enter the ip address i am back to square 1
when i use the truenas.local i still get the label not secure.
One of the possible solutions is to change them to https (or mb just add another applicable url; it really depends on credential manager implementation).
That’s odd. Your http → https redirection is already disabled. Mb it’s worth trying to turn it on and then off.
Regarding the browser warning – there are multiple possible ways to resolve it (welp, it would kinda depends on the actual browser; I would speak for chrome):
No https at all. If there won’t be redirection (to https) you should be ok. You don’t need any cert for the plain http as there is no encryption. In my opinion, working with an expired or self-signed certificate is better, as your connection is still actually encrypted (with a “potentially unsafe” cert). It is a debatable topic – truenas devs, for one, don’t think so.
Issue a valid cert. The steps required are described by Dan here – Sign in to new truenas scale - #3 by dan . Actually, you can get a public domain for free (e.g. with duckdns), but this is off-topic.
Issue a self-signed cert from a custom CA and add this CA to all clients as trusted. IMO, this is about an order of magnitude harder than just issuing a “proper” cert for the owned public domain. I personally never did it, so I can’t consult here.
Issue a self signed cert. If you would trust it after the initial warning, there would be no additional warnings on this client. At least that is how chrome and safari used to work. However, your cert has to be issued for the domain/url you access your truenas with. Truenas has a built-in functionality for issuing such certificates under Credentials → Certificates. I hadn’t used it for some time, so don’t remember much. Perhaps this doc would help.
Just to test it, I’ve disabled redirection on mine (I didn’t reboot, as it shouldn’t be needed):
If I access gui via dns over http (something like http://truenas.mydomain.tld), it’s still redirecting to https; seems like a truenas bug to me.
If I access it via ip (something like http://10.13.37.10), it doesn’t redirect to https, the browser (safari) doesn’t show any warnings. The login page has a warning at the bottom – You are using an insecure connection. Switch to HTTPS for secure access.
If I access gui via dns over http with the port number specified (http://truenas.mydomain.tld:80) it doesn’t redirect me to https Or better said it redirected me to http://truenas.mydomain.tld/ui/signin (without a port). And also no browser warnings. The login page warning is in its place.
So, perhaps you could try the url from 2 or 3. Otoh, you said that access via ip didn’t work for you… I’m on 25.04.2.5, btw.
I tries to reach truenas by manually typing http://192.168.1.124 this brought me to the login screen and google autofill worked. Go figure
In my case the crossed HTTPS did not appear however the not secure message to the far left of the address bar still appears.
If i try truena.local:80 as you suggested i get the same result no HTTPS but the not secure message is there… I guess this is a message just warning us that using http is not as safe as using https.
I am going to leave it as it is and focus on accessing Jellyfin correctly and remotely
Or better said it redirected me to