[GH-ISSUE #1373] Selfhosted ntfy + upstream server to ntfy.sh for ios -> other rate limits? #971

New issue

Closed

opened 2026-05-07 00:29:15 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:29:15 +02:00

Owner

Originally created by @m4ntic0r on GitHub (Jun 25, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1373

I have a really simple question for you and i could not find an answer anywhere.

Now i have a selfhosted ntfy server running and for my ios push notifications the upstream enabled to ntfy.sh.
Do i have other restrictions with that like messages/day than without the upstream?

Thanks for your great work.

Originally created by @m4ntic0r on GitHub (Jun 25, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1373 I have a really simple question for you and i could not find an answer anywhere. Now i have a selfhosted ntfy server running and for my ios push notifications the upstream enabled to ntfy.sh. Do i have other restrictions with that like messages/day than without the upstream? Thanks for your great work.

BreizhHardware

2026-05-07 00:29:15 +02:00

closed this issue
added the
question
label

BreizhHardware commented

2026-05-07 00:29:15 +02:00

Author

Owner

@wunter8 commented on GitHub (Jun 25, 2025):

When using the public ntfy.sh instance as your upstream, you're limited to 250 messages/day, unless you pay for an account on that instance and get higher rate limits.

I don't think attachment size or other limits on the public instance will matter very much since that server never sees the message contents.

@wunter8 commented on GitHub (Jun 25, 2025): When using the public ntfy.sh instance as your upstream, you're limited to 250 messages/day, unless you pay for an account on that instance and get higher rate limits. I don't think attachment size or other limits on the public instance will matter very much since that server never sees the message contents.

BreizhHardware commented

2026-05-07 00:29:16 +02:00

Author

Owner

@m4ntic0r commented on GitHub (Jun 25, 2025):

Ok thanks for that.
I think then i will do 2 dockers, one for "push" with upstream and one for "spam" and do manually refresh :)

@m4ntic0r commented on GitHub (Jun 25, 2025): Ok thanks for that. I think then i will do 2 dockers, one for "push" with upstream and one for "spam" and do manually refresh :)

BreizhHardware commented

2026-05-07 00:29:16 +02:00

Author

Owner

@Elefai commented on GitHub (Jul 2, 2025):

@wunter8 hello, I use the below stack into my swarm. So the problem is I´m not recieving the pushs on my IOS even using upstream base. Do you know What I need to do?

version: "3.7"

services:
ntfy1:
image: binwiederhier/ntfy:v2.12
container_name: ntfy
command:
- serve
- --upstream-base-url
- https://ntfy.sh
networks:
- network_public
volumes:
- ntfy_cache:/var/cache/ntfy
- ntfy_config:/etc/ntfy
environment:
- TZ=America/Sao_Paulo
- upstream-base-url=https://ntfy.sh
- NTFY_BASE_URL=https://mysite.com
- NTFY_UPSTREAM_BASE_URL=https://ntfy.sh
- NTFY_BEHIND_PROXY=true
- NTFY_LOG_LEVEL=trace

@Elefai commented on GitHub (Jul 2, 2025): @wunter8 hello, I use the below stack into my swarm. So the problem is I´m not recieving the pushs on my IOS even using upstream base. Do you know What I need to do? version: "3.7" services: ntfy1: image: binwiederhier/ntfy:v2.12 container_name: ntfy command: - serve - --upstream-base-url - https://ntfy.sh networks: - network_public volumes: - ntfy_cache:/var/cache/ntfy - ntfy_config:/etc/ntfy environment: - TZ=America/Sao_Paulo - upstream-base-url=https://ntfy.sh - NTFY_BASE_URL=https://mysite.com - NTFY_UPSTREAM_BASE_URL=https://ntfy.sh - NTFY_BEHIND_PROXY=true - NTFY_LOG_LEVEL=trace