disable port 443 for webgui

[Robert Thomspon]

SO, i assumed this was relatively easy but im guessing im missing a radio button click somewhere.

Ive set my webgui SSL connection to be 7443, however, when i go to 192.168.myip:443, it still directs to the webgui of TrueNAS. Can anyone tell me how to disable the use of port 443 by TrueNAS?

 

[sretalla]

Looks like this is what you want...

 

[Robert Thomspon]

Looks like this is what you want...
View attachment 52615

sort of the exact opposite of what i want :)
I DONT want HTTPS on the truenas (or, at least, i dont want it going to port 443... 2 slots above that, where you have 443 as the HTTPS port, you should just be able to change that and TrueNAS should stop listening on 443, but it doesnt.

If you set that 443 port to say, 444, you can still connect to 443 when you shouldnt be able to (please try and let me know if im wrong).

 

[sretalla]

What I was thinking about was the reference in the help text to the 1 year setting for the browser to remember the redirect. Maybe clear that site from the browser's cache or use another one to test.

 

[Robert Thomspon]

What I was thinking about was the reference in the help text to the 1 year setting for the browser to remember the redirect. Maybe clear that site from the browser's cache or use another one to test.

oh, i see where you were going with that. Yeah, i already tried other browsers and incognito modes... no joy, still accessed from 443

 

[Cloudified]

oh, i see where you were going with that. Yeah, i already tried other browsers and incognito modes... no joy, still accessed from 443

I hate to ask the obvious, but have you tried restarting the system after making the port number change just to see if it updates correctly after the services have restarted?

 

[Robert Thomspon]

I hate to ask the obvious, but have you tried restarting the system after making the port number change just to see if it updates correctly after the services have restarted?

I did.
And no worries. Its the same thing I would ask.

 

[Cloudified]

I did.
And no worries. Its the same thing I would ask.

Looks like you discovered a new bug. :)

 

[FrostyCat]

It works on mine, this is what I have. Traefik is handling both 80 and 443.

 

[Robert Thomspon]

It works on mine, this is what I have. Traefik is handling both 80 and 443.

View attachment 52621

yeah, i have been testing to see if i can replicate before submitting it as a bug... for me, it doesnt take on a first reboot after setting it, but will after the 2nd or 3rd... id like to replicate the problem consistently before reporting it as a bug instead of a possible fluke on my end...

 

[Ixian]

It's a whole lot simpler to just add another ip to Truenas and have Traefik or whatever ingress service you use listen on that. That's what I do.

 

[FrostyCat]

It's a whole lot simpler to just add another ip to Truenas and have Traefik or whatever ingress service you use listen on that. That's what I do.

That's also a good idea.

 

[Jip-Hop]

It's a whole lot simpler to just add another ip to Truenas and have Traefik or whatever ingress service you use listen on that. That's what I do.

Nice! Now I don't need to wait for Traefik to be up after a reboot to access the TrueNAS GUI on 443 xD I was making the TrueNAS GUI accessible again on 443 via Traefik (TrueCharts external-service). But no more :)

 

[Ixian]

Yep, I don’t even use apps, my Compose setup works just fine, you can do the same with it, add an ip alias in Truenas and have Traefik bind to it. My containers are on separate internal bridges that Traefik proxies as needed.

I did need to script removing iptables=false in the Docker daemon (if you set, then unset the App pool it won’t overwrite it on boot, only if there’s an update) and I also added some shell commands to cleanly stop the containers on shutdown and bring them back up post init but if you know what you are doing rolling your own Compose setup is simple and easy.

 

[Jip-Hop]

Tempting! Perhaps you can contribute something interesting to the conversation below my Using Docker on TrueNAS SCALE (no Kubernetes) gist.

 

[Ixian]

I like the patch approach for daemon.json - cleaner.

It's really only necessary if you are attempting to run both your own Compose setup and still want to play around with Apps. That's because if the App pool is set/the K3s service(s) is running SCALE will reset the daemon.json file on each boot. If you disable the Apps/Kubernetes stuff (by un-setting the App pool) then it leaves things alone. It will also reset it if you update SCALE but updates are relatively infrequent and it's simple just to restore things the way you want after.

I prefer to leave the Kubernetes stuff disabled. Note that folks really need to know what they are doing with Docker if they go that way particularly when it comes to security, snapshots, container networking, and so on. I'm thinking of doing a mini-writeup on the process but will put a disclaimer up top that most users are better off going the App route, working with Truecharts, and so on.