Create a self-hosted instance of NTFY

[phenomlab]

@dave1904 No, you only need that if you are using a proxy from recollection (which of course, you aren’t for upstream internet access) - I only use

base-url: "https://<your domain fqdn>"

[dave1904]

@phenomlab said in Create a self-hosted instance of NTFY:

@dave1904 No, you only need that if you are using a proxy from recollection (which of course, you aren’t for upstream internet access) - I only use

base-url: "https://<your domain fqdn>"

If upstream-base-url is not set, notifications will still eventually get to your device, but delivery can take hours, depending on the state of the phone. If you are using your phone, it shouldn’t take more than 20-30 minutes though.

As I don’t have an iOS device I cannot test it. Will have to observe this. Thanks!

[phenomlab]

@dave1904 Interesting! I might actually add that, but message delivery for me is almost instant.

[dave1904]

Hmm. For me this is all still working weird. Right now I had to go to ntfy.mydomain.com to receive a notification that was sent before.

[phenomlab]

@dave1904 From the desktop PC or your phone?

[dave1904]

@phenomlab From my phone. Maybe better to use the native app?

[phenomlab]

@dave1904 Yes, always

[dave1904]

Yes, working flawlessly with the native app including my icon.

[phenomlab]

@dave1904 Good to hear!

[dave1904]

One more question, how can I restart the ntfy server? I’ve edited the config and want to restart it but I only find the ntfy serve command and it’s already serving of course.

[phenomlab]

@dave1904 you should be able to use

sudo service ntfy stop
sudo service ntfy start

Or simpler

sudo service ntfy restart

[dave1904]

Thanks, I already tried that but when I use

sudo service ntfy stop

and then

ntfy serve

it still says

2023/10/03 18:26:23 INFO Listening on 127.0.0.1:2586[http], ntfy 2.7.0, log level is INFO (tag=startup)
2023/10/03 18:26:23 FATAL listen tcp 127.0.0.1:2586: bind: address already in use (exit_code=1)
listen tcp 127.0.0.1:2586: bind: address already in use

I’m confused, it should stop serving right?

[phenomlab]

@dave1904 not if you have another window running where ntfy serve is still running? That message would indicate you have it running somewhere already.

[dave1904]

Yes, that’s the problem of Droplet Web Console… But I should be able to stop the process?

[phenomlab]

@dave1904 what’s the output of

ps aux | grep ntfy

[dave1904]

@phenomlab

root     2443566  0.0  1.6 1274412 16272 ?       Sl   10:06   0:09 ntfy serve
root     2449599  0.0  0.0   8160   656 pts/0    S+   18:32   0:00 grep --color=auto ntfy

[dave1904]

Alright, I’ve killed the process and could do ntfy serve again. Thanks!

[phenomlab]

@dave1904 good. Thanks

[dave1904]

I can’t get this to work for my iOS buddy. He receives the notification messages in ntfy but doesn’t get any notification on iOS. I’ve tried upstream-base-url: "https://ntfy.sh" but no luck. @phenomlab do you have an iOS device?

[phenomlab]

@dave1904 said in Create a self-hosted instance of NTFY:

Alright, I’ve killed the process and could do ntfy serve again. Thanks!

Is better to run as a service rather than a daemon.