[Commotion-admin] [luci-commotion] https redirect results in inescapable certificate errors in Firefox (#23)

[Josh King]

Actually, every node is creating its own certificate; it gets generated on first boot. The problem is that when you permanently save the cert, your browser maps it to an IP address. If you primarily access the node through the 192.168.1.20 alias, rather than its LAN address, when you save the cert it gets associated with the 192.168.1.20 address. When you go to another node, it gets the same IP address but a different certificate (actually if it were the same cert, you wouldn't get this error at all), thus causing the error. This only occurs for users who primarily connect via the 192.168.1.20 alias rather than getting a DHCP lease. The solution is to change the 'thisnode' alias to point to the main LAN IP, and remove the 192.168.1.20 alias. The first part of the solution at least is in DR2. I'll leave this issue open in the meantime until DR2.1 changes the IP addressing, which will address the second part.

---
Reply to this email directly or view it on GitHub:
https://github.com/opentechinstitute/luci-commotion/issues/23#issuecomment-24532048
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-admin/attachments/20130916/fb6d407a/attachment.html>