This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
wiki:systeme_mana:webui [2023/07/31 10:51] cgu [Gateway administration menu] |
wiki:systeme_mana:webui [2023/10/12 16:23] (current) ehe |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| <note important>When changing the IP of the gateway, or when switching from DHCP to fix IP and vice versa, connection to the web interface will be lost. This is __not__ a bug. As the IP changed, the IP used in the browser’s URL bar is no longer up-to-date. Update it to recover the web interface</note> | <note important>When changing the IP of the gateway, or when switching from DHCP to fix IP and vice versa, connection to the web interface will be lost. This is __not__ a bug. As the IP changed, the IP used in the browser’s URL bar is no longer up-to-date. Update it to recover the web interface</note> | ||
| + | ==== HTTPS Web Interface ==== | ||
| + | === Self-signed certificate procedure === | ||
| + | This procedure will enable HTTPS access to HTTP REST API and web user interface of the product but using self-signed certificate. It's an easy way but at least with 2 drawbacks: | ||
| + | * web navigators will ask for a security exception | ||
| + | * certificates are valid only for 365 days | ||
| + | **Procedure:** | ||
| + | - Activate the configuration with self-signed certificates: | ||
| + | * ''mv /etc/lighttpd.d/ssl-selfsigned.conf.disabled /etc/lighttpd.d/ssl-selfsigned.conf'' | ||
| + | - Apply this configuration : | ||
| + | * ''/etc/init.d/lighttpd restart'' | ||
| + | - Connect to the web interface: https://your_product_name/ | ||
| + | * ex: ''https://klk-wifc-020003/'' | ||
| + | === Full chained certificate support === | ||
| + | |||
| + | The integrated lighttpd is able to support full chained certificate but procedure will depend on the certificate authority used. | ||
| ===== Overview menu ===== | ===== Overview menu ===== | ||