I currently have an Ubuntu Karmic server setup with LTSP 5. I have 24 clients that PXE boot to the server. To lighten load on the server, I have setup NAT and installed Firefox locally. Local Firefox and Firefox on server work well. I have a secure browser installed (in /opt) both on server and locally that we use for state testing (this is a K-8 School). The issue I have is that on 5 of my thin client stations, the local testing browser will not launch without coming up with a Firefox Security Exception error. No matter if I try to confirm or not, it gets stuck on the this screen. I have to pull up local terminal and kill the browser just to get back to the desktop. I have tried multiple users that it works correctly on other machines, but this issue seems to be specific to the machine your logging into, and not the account you're logging in with. I even assigned a staic IP thinking it may be possible another thin client had same IP. It didn't help. Is there a setting somewhere stored locally that I'm missing? Any help or suggestions are appreciated. Thanks!

What type of Firefox-security error does it give? Have you checked vendor documentation for the secure browser you're using?

The error states that the Connection is Untrusted. If I click I Understand the Risks and click Add Exception, nothing happens. If it were an issue with the Vendor's browser it would occur on all machines. It's just a select few. It's as if there is a local firefox setting specific to the machine. I've tried numerous users that it launches for without incident on other machines. I've tried assigning a static IP thinking there may be a duplicate IP on the network. I even launched local firefox and tried manually adding the security exceptions, then launching the secure browser. Nothing seems to work...

Here's some info on that error...
https://support.mozilla.com/en-US/kb...is%20untrusted
Do you have the correct certificate installed on all the computers?

Thanks for the link. The error I was receiving did state that the certificate will be be valid until some date. It didn't occur to me that the System Date\Time in the BIOS could have an effect, but I guess running a local app that it makes sense it could be that. I'll check first thing tomorrow and will let you know. Thanks for the information. It's much appreciated.

Sorry for the delay in responding. The end of the school year is a hectic time for me. I did get a chance to test the BIOS time, and sure enough it was set to 2005. After setting the correct date and time, I booted it up and was able to launch the Local Secure Browser. Makes sense now, and am kicking myself for not thinking of that sooner. Thanks again for the link.