Skip to content

Create a self-hosted instance of NTFY

Moved Guides
63 4 34.8k 1
  • wrote on last edited by
    #31

    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.

  • 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.

    wrote on last edited by
    #32

    @dave1904 From the desktop PC or your phone?

  • @dave1904 From the desktop PC or your phone?

    wrote on last edited by
    #33

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

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

    wrote on last edited by
    #34

    @dave1904 Yes, always

  • wrote on last edited by
    #35

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

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

    wrote on last edited by
    #36

    @dave1904 Good to hear!

  • wrote on last edited by
    #37

    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.

  • 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.

    wrote on last edited by
    #38

    @dave1904 you should be able to use

    sudo service ntfy stop
    sudo service ntfy start
    

    Or simpler

    sudo service ntfy restart
    
  • wrote on last edited by
    #39

    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?

  • 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?

    wrote on last edited by
    #40

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

  • wrote on last edited by
    #41

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

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

    wrote on last edited by
    #42

    @dave1904 what’s the output of

    ps aux | grep ntfy

  • wrote on last edited by
    #43

    @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
    
  • wrote on last edited by
    #44

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

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

    wrote on last edited by
    #45

    @dave1904 good. Thanks

  • wrote on last edited by
    #46

    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?

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

    wrote on last edited by
    #47

    @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.

  • @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.

    wrote on last edited by
    #48

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

    @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.

    you are right. Next config change I have to search for the pid again.

  • 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?

    wrote on last edited by
    #49

    @dave1904 there won’t be any notification in iOS unless you refresh. This is a known issue - see below

    https://docs.ntfy.sh/known-issues/

  • wrote on last edited by
    #50

    I hate iOS.


Related Topics