same here

Hello,
This can be easily bypassed using unraid connect url. It works like a charm !!!

Hello, This can be easily bypassed using unraid connect url. It works like a charm !!!

I tried this but still ran into some issues, with ssl set to True, I get the following error:
websockets.exceptions.InvalidURI: https://10-0-0-250.abc123.myunraid.net:444/login isn't a valid URI: scheme isn't ws or wss

With it set to False, I get this error:
websockets.exceptions.InvalidStatusCode: server rejected WebSocket connection: HTTP 400

Neither one seems to work for me...

My server is ONLY accessible via HTTPS and on port 444

nvm on the above, got it working after I debugged it and the following config worked:

unraid:
  - name: brute
    host: 10-0-0-250.abc123.myunraid.net
    port: 444
    ssl: True
    username: root
    password: PASSWORD
    scan_interval: 30
  
mqtt:
  host: 10.0.0.247
  port: 1883
  username: USERNAME
  password: PASSWORD

Hello, This can be easily bypassed using unraid connect url. It works like a charm !!!

Thats assuming you use unraid connect which I do not, and I assume lots of others dont as well

I dont understand this limitation. If both my unraid and my self signed home assistant are on the same local network, will hass-unraid not work?

I dont understand this limitation. If both my unraid and my self signed home assistant are on the same local network, will hass-unraid not work?

Most likely because the certificate isn't trused. I'll see if I can look into it, but I don't use self signed certs.
For now use http or a trusted certificate and it should work as intended.

I dont understand this limitation. If both my unraid and my self signed home assistant are on the same local network, will hass-unraid not work?

Most likely because the certificate isn't trused. I'll see if I can look into it, but I don't use self signed certs. For now use http or a trusted certificate and it should work as intended.

I mean the ideal way to support this is to allow a custom certificate to be passed in and then simply trust that certificate. An alternative and less ideal option is to just disable verification with an ENV variable so that its possible to atleast use this as right now its not for anyone with a custom cert.

nvm on the above, got it working after I debugged it and the following config worked:

unraid:
  - name: brute
    host: 10-0-0-250.abc123.myunraid.net
    port: 444
    ssl: True
    username: root
    password: PASSWORD
    scan_interval: 30
  
mqtt:
  host: 10.0.0.247
  port: 1883
  username: USERNAME
  password: PASSWORD

You are the real MVP, this is the ONLY way I could get it to work. I dont understand why my LAN IP wouldnt

I'll add my 2 cents here:

• go to your Unraid management access section
• note your http or https port, as per your setting for 'Use SSL/TLS:'
• scroll down to the 'Local access urls' and you'll see one listed for 'uses certificate_bundle.pem' if you generated one using something like Let's Encrypt.
• plug in the details as per 'stayupthetree' post above, with just the 'your-ip-address.certificatekey.myunraid.net'