Summary: Support thread for all (there's one) of my Docker Templates for CA.

 

This thread is purely for supporting the templates themselves. I have absolutely nothing to do with the actual development of anything.

 

• Ntfy
  Web: https://ntfy.sh/
  Description: ntfy (pronounce: notify) is a simple HTTP-based pub-sub notification service. It allows you to send notifications to your phone or desktop via scripts from any computer, entirely without signup, cost or setup.

Edited November 13, 20223 yr by kostecki

Thanks for this container @kostecki, really like Ntfy as a self hosted solution.
Is there any reason adding the extra Variable: `web-root: disable` wouldn't work as mentioned in the FAQ?
I can't find any server.yml file to edit it so figured this would work...

On 12/7/2022 at 6:34 AM, Mattyfaz said:

Thanks for this container @kostecki, really like Ntfy as a self hosted solution.
Is there any reason adding the extra Variable: `web-root: disable` wouldn't work as mentioned in the FAQ?
I can't find any server.yml file to edit it so figured this would work...

You're close. As i'm using env-variables and not the server.yml you need to also use the env-variable version as listed in the table at the bottom of: https://docs.ntfy.sh/config/
But i already exposed that variable, so in the container config in unRaid you can just change NTFY_WEB_ROOT to disabled

Edited January 11, 20233 yr by kostecki

Hi,

I am trying to use it using my reverse proxy to get secured https connection. Even if I put https://subdomain.domain as NTFY_BASE_URL:

it seems to use always HTTP. Sorry as I am a noob this is probably stupid thing I miss.

Anyone get email publishing to work? I have tried everything and so far no go

Anyone get web push to work, the new feature? I add the 4 needed lines as variables, but it doesn't seem to do anything.

thanks for doing this template... though not working for me. Every time I launch the logs and console menu items they appear briefly and the window then dissapears. Also nothing gets written to the appdata ntfy folder. Permission issues? Not sure what is going on here....

 

Edited October 3, 20232 yr by bucky2076

Is it possible to send attachments with this template? Seems to require https.

Hi, thanks a lot for your docker. I've been using it for years.
However, from time to time, I got 429 error, even visitor limit is set to 1000 and no way it will ever reach 1000 messages a day, even bursting up to 60, because messages are automatically sent from my server on certain rare conditions. I'm not sure what else I need to do.

Edited May 19, 20242 yr by bthoven

Hello,
I don't really get how to get this docker up and running.
Normally when I have to get internet faced docker container, I'm using Traefik.

I've tried to set the variable to let Traefik create an https cert (which is working), and to set the docker variable   NTFY_BASE_URL: ntfy.mydomain

Also for me it's not totally clear the point:

"By default, the ntfy server is open for everyone, meaning everyone can read and write to any topic (this is how ntfy.sh is configured). To restrict access to your own server, you can optionally configure authentication and authorization using NTFY_AUTH_FILE and NTFY_AUTH_DEFAULT_ACCESS.
After that, simply create an admin user:
ntfy user add --role=admin phil
password: mypass
confirm: mypass
user phil added with role admin
Once you've done that, you can publish and subscribe using Basic Auth with the given username/password."

I created the user&pwd in any case, becasue i want only my service to be able to publish and send things through my server of course.

I don't know what I'm missing here :-)

Does it have to be externally accessible at all? If yes, how?

Thanks in advance

On 11/15/2025 at 6:20 AM, TDA said:

Hello,
I don't really get how to get this docker up and running.
Normally when I have to get internet faced docker container, I'm using Traefik.

I've tried to set the variable to let Traefik create an https cert (which is working), and to set the docker variable   NTFY_BASE_URL: ntfy.mydomain

Also for me it's not totally clear the point:

"By default, the ntfy server is open for everyone, meaning everyone can read and write to any topic (this is how ntfy.sh is configured). To restrict access to your own server, you can optionally configure authentication and authorization using NTFY_AUTH_FILE and NTFY_AUTH_DEFAULT_ACCESS.
After that, simply create an admin user:
ntfy user add --role=admin phil
password: mypass
confirm: mypass
user phil added with role admin
Once you've done that, you can publish and subscribe using Basic Auth with the given username/password."

I created the user&pwd in any case, becasue i want only my service to be able to publish and send things through my server of course.

I don't know what I'm missing here :-)

Does it have to be externally accessible at all? If yes, how?

Thanks in advance

I'm in exact same boat. Any resolution?

On 11/15/2025 at 6:20 AM, TDA said:

Hello,
I don't really get how to get this docker up and running.
Normally when I have to get internet faced docker container, I'm using Traefik.

I've tried to set the variable to let Traefik create an https cert (which is working), and to set the docker variable   NTFY_BASE_URL: ntfy.mydomain

Also for me it's not totally clear the point:

"By default, the ntfy server is open for everyone, meaning everyone can read and write to any topic (this is how ntfy.sh is configured). To restrict access to your own server, you can optionally configure authentication and authorization using NTFY_AUTH_FILE and NTFY_AUTH_DEFAULT_ACCESS.
After that, simply create an admin user:
ntfy user add --role=admin phil
password: mypass
confirm: mypass
user phil added with role admin
Once you've done that, you can publish and subscribe using Basic Auth with the given username/password."

I created the user&pwd in any case, becasue i want only my service to be able to publish and send things through my server of course.

I don't know what I'm missing here :-)

Does it have to be externally accessible at all? If yes, how?

Thanks in advance

I added this to docker configuration and all good now!

NTFY_BEHIND_PROXY=TRUE variable

Edited January 18Jan 18 by paladin
spelling error