MQTT subscripton to home/nodes/command/rpi-rpi4-4gb-b/+ disabled

[AndrewTapp]

I'm relatively new to this and would appreciate some advice/pointers regarding this issue I'm currently experiencing.

This has been running without issue for some time, however I've recently not been having any updates within Home Assistant.

The service appears to be running correctly, however I'm getting a MQTT subscription disabled message on checking the status. Have no idea if it's the reporter service or the MQTT broker on Home Assistant, have checked what I can and searched various threads but have not found anything.

Any advice would be appreciated.

[kali-777]

I had SAME problem looks like He has "good" Certificate from Let'sEncypt so i just changed HTTPS from HTTP then it will work! 😊

response = requests.request('GET', 'https://kz0q.com/daemon-releases', verify=False)

[bsimmo]

I had SAME problem looks like He has "good" Certificate from Let'sEncypt so i just changed HTTPS from HTTP then it will work! 😊

response = requests.request('GET', 'https://kz0q.com/daemon-releases', verify=False)

It would be better to disable that whole check. You are now connecting insecurley to a website that isn't really needed.
The check is looking for new versions but the chances of getting any is low and you can just look here every now and again.
The secure part isn't working for whatever reason, be it lapsed certificate, a hacker in between etc...

[kali-777]

I had SAME problem looks like He has "good" Certificate from Let'sEncypt so i just changed HTTPS from HTTP then it will work! 😊
response = requests.request('GET', 'https://kz0q.com/daemon-releases', verify=False)

It would be better to disable that whole check. You are now connecting insecurley to a website that isn't really needed. The check is looking for new versions but the chances of getting any is low and you can just look here every now and again. The secure part isn't working for whatever reason, be it lapsed certificate, a hacker in between etc...

I agree about disable to check, however I'm sorry to 'disagree' but I'm working in PKI >10y ANY HTTPS even self-signed/expired Certificate is securer than plain HTTP, to perform a MiTM Attack Your DNS needs be posioned OR Server needs to be hacked, those Risks are kind of low, especially via Pi-hole/dnsmasq/unbound/stubby 😏

[bsimmo]

Sorry misread, "I read" that the change was from S to no S, I now reread it as no S to S, i.e security is now being used. My bad. Still, just disable it, it's caused so many problems over the past years.

…

On Fri, 8 Nov 2024, 9:13 am Kali, ***@***.***> wrote: I had SAME problem looks like He has "good" Certificate from Let'sEncypt so i just changed HTTPS from HTTP then it will work! 😊 response = requests.request('GET', 'https://kz0q.com/daemon-releases', verify=False) It would be better to disable that whole check. You are now connecting insecurley to a website that isn't really needed. The check is looking for new versions but the chances of getting any is low and you can just look here every now and again. The secure part isn't working for whatever reason, be it lapsed certificate, a hacker in between etc... I agree about disable to check, however I'm sorry to 'disagree' but I'm working in PKI >10y ANY HTTPS even self-signed/expired Certificate is securer than plain HTTP, to perform a MiTM Attack Your DNS needs be posioned OR Server needs to be hacked, those Risks are kind of low, especially via Pi-hole/dnsmasq/unbound/stubby 😏 — Reply to this email directly, view it on GitHub <#151 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACYAXN5HL63PZGUJBTGYYCLZ7R6FDAVCNFSM6AAAAABH4DXVVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUGE4TMOBXGI> . You are receiving this because you commented.Message ID: ***@***.***>