is this add-on still maintained ?
itâs just a docker image connecting to the public service so not much to maintain but yes, it should work 
I am trying to get a publicly accessed HTTPS URL to use Homeassistant Cast on my local Chromecast enabled TV.
my webhook configuration is following
key: xxxx
secret: xxxxxx
region: ''
forwarding:
- bucket: ha
destination: http://192.168.18.xxx:8123
tunnels:
- name: home-assistant
destination: http://192.168.18.xxx:8123
protocol: tls
domain: xxxxx.duckdns.org
duck_dns:
token: xxxxxxx
accept_terms: true
cloudflare:
email: ''
api_key: ''
tunnels_enabled: true
forwarding_enabled: true
this is how webhook log looks like
bucket list. but when I access it it turns up blank
Was there an answer for this issue? Iâm getting the same problem and can find no resolution.
Iâm also getting this error in the log:
ERROR failed to send webhook request status {"error": "rpc error: code = InvalidArgument desc = bucket metadata missing, update your client", "destination": "http://127.0.0.1:8123/favicon.ico", "method": "GET", "status": 404}
hey guys, buckets are used for webhook forwarding, not direct access 
Hereâs some info on:
- Webhook forwarding Quick Start - Forwarding - Webhook Relay - example use cases IFTTT, NodeRED integration, etc. In short, integrating between systems
- Tunnels Quick Start - Tunnels - Webhook Relay - example use case is remote access to your Home Assistant via web browser.
Itâs the latter Iâm trying to achieve, but even with a Tunnel configured and showing green âconnectedâ status in the webhookrelay portal, when trying to open a webpage using http://mydomain.duckdns.org it generates a âConnection timed outâ page.
And if I try the URL listed in the log output (eg. https://my.webhookrelay.com/v1/webhooks/my_id), then I just get a blank webpage and the log records error:
ERROR failed to send webhook request status {"error": "rpc error: code = InvalidArgument desc = bucket metadata missing, update your client", "destination": "http://127.0.0.1:8123", "method": "GET", "status": 200}
When I forget about trying to use the Tunnel, and just try to get Webhook forwarding to work, with the add-on started and it showing itâs connected in the webhookrelay portal, I try to open my webhook URL and just get the error below:
|2021-12-05 13:41:55.972|INFO|webhook request relayed|{destination: http://127.0.0.1:8123/api/webhook/standardon, method: GET, bucket: ha, status: 405 Method Not Allowed, retries: 0}|
|---|---|---|---|
|2021-12-05T13:41:56.055Z|ERROR|failed to send webhook request status|{error: rpc error: code = InvalidArgument desc = bucket metadata missing, update your client, destination: http://127.0.0.1:8123/api/webhook/standardon, method: GET, status: 405}|
|2021-12-05 13:41:56.126|INFO|webhook request relayed|{destination: http://127.0.0.1:8123/favicon.ico, method: GET, bucket: ha, status: 404 Not Found, retries: 0}|
|2021-12-05T13:41:56.197Z|ERROR|failed to send webhook request status|{error: rpc error: code = InvalidArgument desc = bucket metadata missing, update your client, destination: http://127.0.0.1:8123/favicon.ico, method: GET, status: 404}|
Iâm going to give up on WebhookRelay for Home Assistant, it just doesnât seem to work any longer.
UPDATE: Iâve managed to get the webhook forwarding working (previous issue was that I was trying to test it with a GET request which Home Assistant wonât allow, itâs got to be a POST request). Although I donât get what the point of setting up a DuckDns domain is, because it doesnât seem to be of any use, you have to use the URL given in the webhookrelay portal.
Iâve given up trying to get the Tunnel part of this add-on service to work - it just doesnât seem to work at all.
And it seems if you set the configuration to include âtunnels_enabled: falseâ then the add-on just wonât start.