starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

[GH-ISSUE #446] Configuration not reload on systemctl restart. #342

New issue

Closed

opened 2026-05-07 00:23:15 +02:00 by BreizhHardware · 6 comments

BreizhHardware commented

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

Owner

Originally created by @Microwave-WYB on GitHub (Oct 21, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/446

When received a link to an attachment, the port number is missing and must be manually added.

For example the topic is at "example.com:8000/ntfy"

The file link will appear to be "example.com/files/hash.png"

Originally created by @Microwave-WYB on GitHub (Oct 21, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/446 When received a link to an attachment, the port number is missing and must be manually added. For example the topic is at "example.com:8000/ntfy" The file link will appear to be "example.com/files/hash.png"

BreizhHardware

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

closed this issue
added the
question
label

BreizhHardware commented

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

Author

Owner

@binwiederhier commented on GitHub (Oct 21, 2022):

Can you be more specific where you see this? Android app, web app?

The generated attachment URL is based on the base-url configured in the server.yml file. If that does not have the correct port, then your generated attachment URL will be incorrect.

@binwiederhier commented on GitHub (Oct 21, 2022): Can you be more specific where you see this? Android app, web app? The generated attachment URL is based on the `base-url` configured in the `server.yml` file. If that does not have the correct port, then your generated attachment URL will be incorrect.

BreizhHardware commented

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

Author

Owner

@Microwave-WYB commented on GitHub (Oct 21, 2022):

Can you be more specific where you see this? Android app, web app?

The generated attachment URL is based on the base-url configured in the server.yml file. If that does not have the correct port, then your generated attachment URL will be incorrect.

I have the port number in the base url. This is not a problem about android or web app, it's the back-end sending the wrong url. I restarted the server to make sure the configuration is reloaded.

@Microwave-WYB commented on GitHub (Oct 21, 2022): > Can you be more specific where you see this? Android app, web app? > > The generated attachment URL is based on the `base-url` configured in the `server.yml` file. If that does not have the correct port, then your generated attachment URL will be incorrect. I have the port number in the base url. This is not a problem about android or web app, it's the back-end sending the wrong url. I restarted the server to make sure the configuration is reloaded.

BreizhHardware commented

2026-05-07 00:23:17 +02:00

Author

Owner

@Microwave-WYB commented on GitHub (Oct 21, 2022):

From here it seems like the base url should be used, but I've tested multiple times that this is not including the port number

@Microwave-WYB commented on GitHub (Oct 21, 2022): ![Screenshot_20221021-135448](https://user-images.githubusercontent.com/68882116/197287090-f31e023f-a126-415f-8c03-7caf9e950d4b.png) From here it seems like the base url should be used, but I've tested multiple times that this is not including the port number

BreizhHardware commented

2026-05-07 00:23:17 +02:00

Author

Owner

@Microwave-WYB commented on GitHub (Oct 21, 2022):

I found the problem here. systemctl restart ntfy does not reload configuration. I had to do systemctl stop ntfy; systemctl start ntfy

@Microwave-WYB commented on GitHub (Oct 21, 2022): I found the problem here. `systemctl restart ntfy` does not reload configuration. I had to do `systemctl stop ntfy; systemctl start ntfy`

BreizhHardware commented

2026-05-07 00:23:17 +02:00

Author

Owner

@binwiederhier commented on GitHub (Oct 21, 2022):

I found the problem here. systemctl restart ntfy does not reload configuration. I had to do systemctl stop ntfy; systemctl start ntfy

This is the second instance of this that I'm hearing about. I use systemctl restart ntfy when I deploy a new version and it works nicely. What system are you on? What does journalctl say when you issue a restart? Are you using the .deb/.rpm or something custom?

@binwiederhier commented on GitHub (Oct 21, 2022): > I found the problem here. `systemctl restart ntfy` does not reload configuration. I had to do `systemctl stop ntfy; systemctl start ntfy` This is the second instance of this that I'm hearing about. I use `systemctl restart ntfy` when I deploy a new version and it works nicely. What system are you on? What does journalctl say when you issue a restart? Are you using the .deb/.rpm or something custom?

BreizhHardware commented

2026-05-07 00:23:17 +02:00

Author

Owner

@binwiederhier commented on GitHub (Nov 19, 2022):

Closed due to inactivity

@binwiederhier commented on GitHub (Nov 19, 2022): Closed due to inactivity