Native secure access

Use this forum to discuss possible implementation of a new feature before opening a ticket.
A developer shall edit the topic title with "[xxx]" where xxx is the id of the accompanying tracker id.
Duplicate posts about the same id. +1 posts are not allowed.

Moderators: leecollings, remb0

Post Reply
hjzwiers
Posts: 243
Joined: Friday 12 January 2018 8:26
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Native secure access

Post by hjzwiers »

Current browsers are giving more warnings over errors in SSL certificate when logging in remotely through your own domain.

How to fix this is well documented in:
https://www.domoticz.com/wiki/Native_se ... ts_Encrypt

This works fine.

The only issue is that every update of Domoticz overwrites your certificate, and so a lot of work when updating (specially when you frequently install Beta's). Is there any way to integrate this by defining your domain in for example the settings file?
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: Native secure access

Post by waaren »

hjzwiers wrote: Tuesday 15 December 2020 18:38 The only issue is that every update of Domoticz overwrites your certificate, and so a lot of work when updating (specially when you frequently install Beta's). Is there any way to integrate this by defining your domain in for example the settings file?
See this post where it is explained how you can set the name of the certificate domoticz use.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
hjzwiers
Posts: 243
Joined: Friday 12 January 2018 8:26
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Native secure access

Post by hjzwiers »

Thnx for forwarding this link.

Added:

DAEMON_ARGS="$DAEMON_ARGS -sslcert /opt/domoticz/letsencrypt_server_cert.pem"
in /etc/init.d/domoticz.sh (change /opt/domoticz to your domoticz directory)

followed all instructions again in: https://www.domoticz.com/wiki/Native_se ... ts_Encrypt

reforwarded port 80 to server (which is a lot of manual work, because I have nextcloud running on another server which also needs port 80 access)

Now my certificate is on my domain, and all is ok on https ............

Problem is how to make this automated so I don't need to repeat all these actions every three months ......., to do is test if I can now upgrade Domoticz without the certificate being broken
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest