Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

notify fails with ntfy:// but succedes with generic://{fqdn}?disabletls=yes #786

Open
5 tasks done
tctlrd opened this issue Feb 22, 2024 · 0 comments
Open
5 tasks done
Labels
bug Something isn't working

Comments

@tctlrd
Copy link
Contributor

tctlrd commented Feb 22, 2024

First Check

  • This is not a feature request
  • I added a very descriptive title to this issue.
  • I used the GitHub search to find a similar issue and didn't find it.
  • I searched the documentation, with the integrated search.
  • I already read the docs and didn't find an answer.

Homebox Version

v0.10.3

What is the issue you are experiencing?

The ntfy:// uri prefix fails with my locally hosted ntfy server. It spouts this error:
/go/src/app/internal/web/mid/errors.go:31 ERROR occurred error="failed to send ntfy notification: error sending payload: Post \"https://{fqdn}/hb\": remote error: tls: internal error"
The ntfy server is reverse proxied behind caddy with https working and every other app interfacing fine with it using https.
Caddy is configured to also accept non-tls notifications.

The notification works fine with generic:// when I add ?disabletls=yes - otherwise it is:
an error occurred while sending notification to generic webhook: Post \"https://{fqdn}/hb\": remote error: tls: internal error

How can the maintainer reproduce the issue?

Send a homebox test notification to a local ntfy server behind caddy with https working.

Deployment

Other

Deployment Details

Kubernetes in TrueNas Scale with TrueCharts.

@tctlrd tctlrd added the bug Something isn't working label Feb 22, 2024
@tctlrd tctlrd changed the title notify fails with ntfy:// but succedes with generic://fqdn?disabletls=yes notify fails with ntfy:// but succedes with generic://{fqdn}?disabletls=yes Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant