Replies: 5 comments 1 reply
-
See here. The URL should be pretty straightforward; something like:
# -vvvv increases the verbosity; good for troubleshooting
apprise -vvvv -b test "ntfys://user: pass@server/topics" |
Beta Was this translation helpful? Give feedback.
-
Sorry, I didn't ask my question very well. When I send a notification through the Apprise UI, what exactly will my swag reverse proxy see coming in? As far as I can see in the proxy logs, it's just: '111.222.333.444 - chris [13/Nov/2022:12:48:57 -0700] "GET / HTTP/1.1" 302 138 "-" "Apprise" upstream - - - |
Beta Was this translation helpful? Give feedback.
-
I'm not to familiar with Authelia. With respect to what i do know (Apprise), outbound messages from it for ntfy look like this depending on your Apprise URL This probably isn't the answer your looking for though. What's the actual problem you're having? If you're using the Apprise API, are you able to send a notification using it's built in website? |
Beta Was this translation helpful? Give feedback.
-
I really appreciate you taking the time to try and help. The problem is that notifications sent from Apprise to ntfy don't come through. This is because Authelia (authentication server) is not letting them through. It's not letting them through because nginx is only passing it what it sees from Apprise, which is: '111.222.333.444 - chris [13/Nov/2022:12:48:57 -0700] "GET / HTTP/1.1" 302 138 "-" "Apprise" upstream - - - Your link shows that the URL coming from Apprise should include the ntfy topic, but nginx is not seeing the topic. My ntfy topic contains a keyword that tells Authelia to let it through, but since it's not seeing the topic it doesn't let it through. Seems like this is an issue on my end and I need to figure out why nginx is not seeing the topic from Apprise. |
Beta Was this translation helpful? Give feedback.
-
So is it an Apprise API server that you're trying to connect to? You'll need to somehow setup Authelia to accept 'Basic-Auth` for routing to your API server only. If you're using Nginx, you just need to add 1 entry to bypass the file and maybe store a complicated user/pass for apprise there instead. Something like: # /etc/nginx/your.config
# This needs to go inside your nginx configuration you want to catch
# traffic on; you want to create a separate location line to bypass the Authelia
# hits:
location /apprise/ {
# Security
auth_basic "Restricted Area";
# See below on how to generate this pwprotect_htpasswd file
# that will be referenced if traffic doesn't match the allow lines below:
auth_basic_user_file pwprotect_htpasswd;
# Satisfy allows us to bypass authentication
# for allowed ip addresses
satisfy any;
# Local Trusted Traffic only
allow 192.168.0.0/24;
allow 127.0.0.0/8;
# drop rest of the world
deny all;
# Route traffic if the above is satisifed
proxy_pass http://your.apprise.backend.instance:80;
} Now you will want to make sure you have a # Create our original password File (and provide password when prompted)
htpasswd -c -B /etc/nginx/pwprotect_htpasswd your_user_name
# The above will prompt you to type/confirm a password Reload NginX and you should be able to access your Apprise API with the user/pass combo from outside. You can access your configuration using Apprise as: apprise --config=http://your_user_name:pw_you_set@yourserver You can also leverage the same triggers through: apprise apprise://your_user_name:pw_you_set@yourserver Hopefully this helps a little. |
Beta Was this translation helpful? Give feedback.
-
I'm trying to send alerts from a remote server to my self-hosted ntfy server via Apprise. Ntfy is behind swag and Authelia. I can't get the notifications from Apprise to bypass Authelia. In swag & Authelia it seems like the full URL it's getting from Apprise is just "https://ntfy.mydomain.com."
My ntfy topic has a keyword and I have Authelia to let anything with that keyword through. I can send notifications from the ntfy web app and my phone and those go through. I can see in swag and Authelia that the URL it gets from those contains the ntfy topic with the keyword.
Is Apprise only sending a URL with subdomain+TLD? I'm not a developer so I wasn't able to figure that out by reading through the docs.
Beta Was this translation helpful? Give feedback.
All reactions