Gotify plugin not working

[taker1988 21]

Hi,

I just downloaded the Gotify plugin. I copied the MediaBrowser.Plugins.GotifyNotifications.dll file to the plugin folder and then restarted the server.

I configured the plugin, but it's not working. As soon as I try to send a test message, I get an “Error - Unauthorized” message, but I don't know why.

 

I'm running Emby in Docker. I'm using the latest beta 4.9.2.7 with a Premier license.

The whole thing is running on Synology DS720+ with DSM 7.3.1-86003 Update 1.

Gotify is also running in Docker with the :latest tag.

I created a new client in Gotify and copied the token. In Emby, I entered the token in the plugin settings and entered my reverse proxy address, which points to Gotify, as the address.

 

Gotify works this way with other programs. Could it be that the plugin no longer works with the latest version of Emby? Or have I configured something incorrectly?

 

 

Best regards

[Happy2Play 9780]

Odds are something changed in BETA and forces plugin devs to run two branches of their plugin also and some third party devs will not do that and only update plugins when stable releases are done.

@fredflixdoes the plugin work with beta server?

Mod probably needs to move to plugins forum or plugin topic.

[GrimReaper 4739]

An old plugin Dev's post re: keeping up with beta branch, chances are they are not maintaining separate version for any beta, so @Happy2Playis likely correct in his assumption. 

 

[Luke 42077]

There's hardly any difference between beta and stable right now so I don't think being on 4.9.2 should matter, although the plugin is not ours so I can't say for sure.

[fredflix 31]

@taker1988Could you double-check your Gotify token? The error you're getting is when the token is wrong. You're getting declined from your Gotify server.

As @GrimReapermentioned, I only run the latest stable version of Emby and don't really want to maintain 2 code bases, though, that forum post was a while ago pertaining to a different Beta version.
@Lukementions that, currently, there isn't any difference between the beta and stable in the plugin department, so I feel inclined to suspect your Gotify token being the culprit here.

Edited December 3, 2025 by fredflix

[taker1988 21]

Okay, I understand.

I also suspected that it was due to the token. That's why I deleted the old one yesterday and created a new one. The error persisted.

That's why I created this thread.

Would it be possible to find out more from a log file? If so, how should I proceed so that I can post it here?

 

//edit: 

I just went into the server settings and clicked on “Send test message” again to trigger the error. Then I downloaded the server log, which was also updated at 8:55 a.m. on my end.

I have attached the file here.

 

//edit2:

I have now also tried to specify the reverse proxy address, simply the local address of Gotify.

http://192.168.178.123:8815/#/login // NotFound

http://192.168.178.123:8815/#/ // NotFound

http://192.168.178.123:8815/ // NotFound

http://192.168.178.123 // MethodNotAllowed

These attempts didn't work either. Other errors occurred.
NotFound and MethodNotAllowed.

 

embyserver.txt

Edited December 3, 2025 by taker1988

[fredflix 31]

16 hours ago, taker1988 said:

Okay, I understand.

I also suspected that it was due to the token. That's why I deleted the old one yesterday and created a new one. The error persisted.

That's why I created this thread.

Would it be possible to find out more from a log file? If so, how should I proceed so that I can post it here?

 

//edit: 

I just went into the server settings and clicked on “Send test message” again to trigger the error. Then I downloaded the server log, which was also updated at 8:55 a.m. on my end.

I have attached the file here.

 

//edit2:

I have now also tried to specify the reverse proxy address, simply the local address of Gotify.

http://192.168.178.123:8815/#/login // NotFound

http://192.168.178.123:8815/#/ // NotFound

http://192.168.178.123:8815/ // NotFound

http://192.168.178.123 // MethodNotAllowed

These attempts didn't work either. Other errors occurred.
NotFound and MethodNotAllowed.

 

embyserver.txt 8.22 MB · 1 download

Not sure what to tell you... I just spun a new fresh install of the beta version 4.9.2.7 (docker) and it works just fine.
Can you enter the container:

docker exec -it name_of_your_emby_container sh

and run the following curl command (replacing "YOUR_TOKEN" with your Gotify token):

curl -v "https://gotify.synotaker88.synology.me/message?token=YOUR_TOKEN" -F "title=A title" -F "message=A test message"

Can you then provide the ouput? Please remove any IP addresses and Gotify token beforehand!

[Luke 42077]

16 hours ago, taker1988 said:

Okay, I understand.

I also suspected that it was due to the token. That's why I deleted the old one yesterday and created a new one. The error persisted.

That's why I created this thread.

Would it be possible to find out more from a log file? If so, how should I proceed so that I can post it here?

 

//edit: 

I just went into the server settings and clicked on “Send test message” again to trigger the error. Then I downloaded the server log, which was also updated at 8:55 a.m. on my end.

I have attached the file here.

 

//edit2:

I have now also tried to specify the reverse proxy address, simply the local address of Gotify.

http://192.168.178.123:8815/#/login // NotFound

http://192.168.178.123:8815/#/ // NotFound

http://192.168.178.123:8815/ // NotFound

http://192.168.178.123 // MethodNotAllowed

These attempts didn't work either. Other errors occurred.
NotFound and MethodNotAllowed.

 

embyserver.txt 8.22 MB · 2 downloads

It is a service on your network right? So I would think there must be a way to find out why it is sending back those responses?

[taker1988 21]

8 hours ago, fredflix said:

Not sure what to tell you... I just spun a new fresh install of the beta version 4.9.2.7 (docker) and it works just fine.
Can you enter the container:

docker exec -it name_of_your_emby_container sh

and run the following curl command (replacing "YOUR_TOKEN" with your Gotify token):

curl -v "https://gotify.synotaker88.synology.me/message?token=YOUR_TOKEN" -F "title=A title" -F "message=A test message"

Can you then provide the ouput? Please remove any IP addresses and Gotify token beforehand!

Sure. I don´t know how to copy & paste in the terminal. So I had to type it with my hand. I added a screenshot for you.

Seems to be a problem with curl? I also have portainer installed. Should I try that with that bash console thing?

 

@LukeYes, it is on my network. All those things am I running with Docker.

 

 

//edit: Portainer terminal is showing me also an error. :(

 

Edited December 4, 2025 by taker1988

[fredflix 31]

1 hour ago, taker1988 said:

Sure. I don´t know how to copy & paste in the terminal. So I had to type it with my hand. I added a screenshot for you.

Seems to be a problem with curl? I also have portainer installed. Should I try that with that bash console thing?

 

@LukeYes, it is on my network. All those things am I running with Docker.

 

 

//edit: Portainer terminal is showing me also an error. :(

 

My mistake. You're on the right track. It's just that I forgot Emby's docker image doesn't ship with Curl.
It does ship with Wget on the other hand. So can you try this wget command? (Same thing, make sure to mask your IP and Gotify token)

wget "https://gotify.synotaker88.synology.me/message?token=YOUR_TOKEN" -S --no-check-certificate --post-data "title=Hello&message=Test message" -O /dev/null

To paste into a terminal, usually the keyboard shortcut is Ctrl + Shift + V
To copy from the terminal it's usually Ctrl + Shift + C

Edited December 4, 2025 by fredflix

[taker1988 21]

Ok, that command worked now. See Screenshot. Authentication failed.

[taker1988 21]

[fredflix 31]

21 minutes ago, taker1988 said:

Yep, this shows this has nothing to do with the plugin nor Emby.
Your container OS is getting denied as well.
Your problem goes way beyond the scope of support I can provide.

All I can say is at a quick glance, here's what I'd do for troubleshooting this:
- check your reverse proxy. Do you have HTTP Auth (also called "Basic Authentication") on your Gotify server/endpoint? The fact that you're getting a "Username/Password Authentication Failed." message suggests so.
- do you have more than 1 Gotify instance and "maybe" your domain is pointing to the wrong instance where your API key does not exist, hence you're getting denied?
- run that exact same wget command on your host server (not the container) where your docker containers reside and see if you're getting denied as well.
- triple check the API key you're using matches the one on your Gotify server. All it takes is one wrong character or rogue trailing space for it to fail.

Edited December 5, 2025 by fredflix

[taker1988 21]

Okay, it's working now. It was my mistake.

In the Gotify web interface, I always clicked on “Clients” in the top right corner and created a client there. But I have to click on “Apps” and create the Emby app there. I then entered this token on the Emby server in the plugin settings and it worked.

 

Additional information: In the plugin settings, where you enter the Gotify URL, it didn't work like this: https://gotify.synotaker88.synology.me/ - I had to enter it like this: https://gotify.synotaker88.synology.me (i.e., without / at the end)

 

Now everything works. Thanks for your help

 

Best regards

 

[fredflix 31]

3 hours ago, taker1988 said:

Additional information: In the plugin settings, where you enter the Gotify URL, it didn't work like this: https://gotify.synotaker88.synology.me/ - I had to enter it like this: https://gotify.synotaker88.synology.me (i.e., without / at the end)

 

Glad you got it working
Also, just to re-iterate: right above your red arrow, it literally says "no trailing slash" along with a url example 

[taker1988 21]

Haha, yes, I just wanted to mention it explicitly once more.

 

Best regards