I'm currently running build 14050. In this version, we are still facing the same behaviour of the web server.
The letsecrypt challenge file that has been created when trying to generate a new certificate in my case is the following: /home/pi/domoticz/www/.well-known/acme-challenge ...
Is that rule (mandatory dot in the file name) also true for subfolders of the <webroot> folder ? Because Certbot doesn't create his challenge file in the <webroot> folder but in the <webroot>/.well-known/acme-challenge folder.
Furthermore, this would mean that something has been ...
I did the same test as you did with the robots.txt and came to the same result... but :
If I rename the file generated by Certbot to something containing a dot (.) in the name, then the file is reachable! (in my case, the generated file is named ...
I upgraded my Domoticz installation yesterday from Build 13872 to 13949 and I'm currently facing the same issue than you do.
I will give it a try to downgrade my installation to 13872 and check if it works then (Trying to point out whether this issue is related to LetsEncrypt or to ...
it seems so silly once it works ! So, good news, the answer is below :-D
The problem was that, my postData was coded this way: postData = { "muted": false, "current": 18, } instead of: postData = { muted = false, current = 18, }
I have faced exactly the same problem. Seems to be related to ZWave 1.6 (Have a look to the other open topics).
I made a restore of my complete SD Card, went therefore back to ZW 1.4 and now evething is working well again.