lovelylain / hass_ingress

Home Assistant ingress feature, add additional ingress panels to your Home Assistant frontend.
Apache License 2.0
49 stars 6 forks source link

Cant get HTTPS to work with work_mode: ingress #20

Open Supermillhouse opened 1 month ago

Supermillhouse commented 1 month ago

I cant get HTTPS to work with work_mode: ingress

I have been trying to get a https connection to the new Frigate update from a few days ago. (by frigate runs on a different machine to HA)

I have the below settings working fine but if I change the url to "url: https://192.168.X.X:8971" i get a "502: Bad Gateway" in the window, any ideas?

ingress: frigate_ingress: work_mode: ingress require_admin: true ui_mode: toolbar title: Frigate icon: mdi:webcam url: http://192.168.X.X:5000

chrisbennight commented 3 weeks ago

same issue here I believe; I have a music assistant instance running behind traefik at https://ma.domain.tld. In my case it's all running in docker on the same instance and if I change my url to point to http://server.domain.tld:8095 it works (same ip that traefik is proxying to)

Failure presents as just a 502 bad gateway

works

ingress:
  music_assistant:
      title: Music Assistant
      work_mode: ingress
      icon: mdi:speaker
      ui_mode: normal
      url: http://server.domain.tld:8095

fails

ingress:
  music_assistant:
      title: Music Assistant
      work_mode: ingress
      icon: mdi:speaker
      ui_mode: normal
      url: https://ma.domain.tld

http://server.domain.tld:8095/ and https://ma.domain.tld/ both resolve properly in a browser and via wget inside the home assistant container

lovelylain commented 3 weeks ago

try add host header:

ingress:
  music_assistant:
    title: Music Assistant
    icon: mdi:speaker
    url: https://ma.domain.tld
    headers:
       host: ma.domain.tld
chrisbennight commented 3 weeks ago

adding the host header addressed my issue, thanks!