You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the internet to local in the LAN it goes through a reverse proxy that does https with let's encrypt and needs a client certificate for authentication. instead of basic-auth with username:password.
After that i am internal in the LAN and the ntfy-server doesn't need https anymore.
What would be useful if ntfy-APP speaks client authentication at reverse proxy using certifkat.
The connection via browser and mutual TLS works. Just not as comfortable as the APP, especially for alarms and status messages.
The text was updated successfully, but these errors were encountered:
A great feature would be:
From the internet to local in the LAN it goes through a reverse proxy that does https with let's encrypt and needs a client certificate for authentication. instead of basic-auth with username:password.
After that i am internal in the LAN and the ntfy-server doesn't need https anymore.
What would be useful if ntfy-APP speaks client authentication at reverse proxy using certifkat.
The connection via browser and mutual TLS works. Just not as comfortable as the APP, especially for alarms and status messages.
The text was updated successfully, but these errors were encountered: