[BUG] Discord bot /inv not working

[TrollCLGT]

Jellyfin 10.10.3 running as a LXC container in Proxmox, installed via this script
jfa-go 0.5.1 stable installed on the same LXC
Discord stable 348981 (ff756ae)

Problem: /inv command not working in Discord

How to reproduce the issue:
Follow these steps
No "Authorization Method" and no "Read Message/View Channels" options

Jfa-go settings for Discord:

[0belous]

Did you find a solution?

[TrollCLGT]

Installing the unstable branch works for me.

[raku-cat]

Not working here either, setup as below:

Added to server with https://discord.com/oauth2/authorize?client_id=[REDACTED]&integration_type=0&scope=bot&permissions=1127824320752641

(went a little overkill as part of debugging, though i started with the wiki listed perms.

Other commands run fine, but when I try inv on a user that has access to the channel the bot is in:

Invite gets created in jfa-go admin dash, I can see one as "DIscord: @[username i picked]", that's about it though, even with debug logging on there's nothing logged when the commands is ran.
Tried compiling latest git main as suggested above:

It behaves the same.

[TrollCLGT]

It's been a long time since I first set this up so there has been updates to the unstable branch. Here's is a screenshot of my jfa-go version:

If you really want to test out with my outdated image, feel free to download it here:

https://drive.google.com/file/d/1Nbxl-w62Zapq3TIqu62-5K0xc5kN0pXw/view?usp=drive_link

I can confirm that the /inv is still working for me on this image. If it still doesn't work then it might be some configuration issues on your end.

[raku-cat]

It's been a long time since I first set this up so there has been updates to the unstable branch. Here's is a screenshot of my jfa-go version:

If you really want to test out with my outdated image, feel free to download it here:

https://drive.google.com/file/d/1Nbxl-w62Zapq3TIqu62-5K0xc5kN0pXw/view?usp=drive_link

I can confirm that the /inv is still working for me on this image. If it still doesn't work then it might be some configuration issues on your end.

I'll give it a shot I suppose but ya I agree, I assume it's a configuration nuance, perhaps a change in discord API that needs a specific config that just needs to be documented.

[hrfee]

Sorry, I guess I didn't review this well enough when it was PRed and I missed that it checked locally whether the user was a jfa-go admin, (i.e. not a Jellyfin admin, but had had "access jfa-go" checked by their name in Accounts), rather than in all relevant locations (i.e. the same way it's done when you try to log into the admin page). That commit should fix it, could you all try? Thanks.

[raku-cat]

Sorry, I guess I didn't review this well enough when it was PRed and I missed that it checked locally whether the user was a jfa-go admin, (i.e. not a Jellyfin admin, but had had "access jfa-go" checked by their name in Accounts), rather than in all relevant locations (i.e. the same way it's done when you try to log into the admin page). That commit should fix it, could you all try? Thanks.

Built latest master, the webui fails to load (white screen) and the command gives the same error, though I'm assuming for different reasons now, and gives no errors for either issue in the logs.

[raku-cat]

Not sure if it was because of 07d02f8 but I just rebuilt after making some adjustments to my compilation process and the webui loads now, but still not having inv command give "application did not respond", I will note though that now the invites aren't even being silently created in the webui like before.
Just to clarify how I'm setup, I login with my jellyfin login, which is a jellyfin admin account, and that account is the one marked "access jfa-go" in the ui, and also is the one linked to my discord that I'm trying the command from.

In verifying all of the above, I found that when I manually unliked my discord from admin account and then tried to add it back, when i typed my username and then clicked add, I get a red error in the bottom right corner with the following in logs:

Details

May 15 14:15:58 partyvan jfa-go[578046]: [GIN] DELETE(/users/discord) => 500 <--- unlinking discord
May 15 14:15:58 partyvan jfa-go[578046]: [GIN] GET(/users/announce) => 200
May 15 14:15:58 partyvan jfa-go[578046]: [GIN] GET(/users/announce) => 200
May 15 14:15:58 partyvan jfa-go[578046]: [GIN] GET(/users) => 200
May 15 14:15:58 partyvan jfa-go[578046]: [GIN] GET(/users) => 200
May 15 14:16:01 partyvan jfa-go[578046]: [GIN] GET(/accounts) => 200
May 15 14:16:01 partyvan jfa-go[578046]: [GIN] GET(/lang/admin) => 200
May 15 14:16:01 partyvan jfa-go[578046]: [INFO] 14:16:01  Token requested (refresh token)
May 15 14:16:01 partyvan jfa-go[578046]: [GIN] GET(/token/refresh) => 200
May 15 14:16:01 partyvan jfa-go[578046]: [GIN] GET(/config/update) => 200
May 15 14:16:01 partyvan jfa-go[578046]: [GIN] GET(/users/announce) => 200
May 15 14:16:01 partyvan jfa-go[578046]: [GIN] GET(/profiles/names) => 200
May 15 14:16:01 partyvan jfa-go[578046]: [GIN] GET(/users) => 200 <--- refreshing the page
May 15 14:16:08 partyvan jfa-go[578046]: [GIN] GET(/users/discord/raku) => 200
May 15 14:16:10 partyvan jfa-go[578046]: 2025/05/15 14:16:10 [Recovery] 2025/05/15 - 14:16:10 panic recovered: <-- error after clicking add
May 15 14:16:10 partyvan jfa-go[578046]: runtime error: invalid memory address or nil pointer dereference
May 15 14:16:10 partyvan jfa-go[578046]: /usr/lib/go/src/runtime/panic.go:262 (0x4808d8)
May 15 14:16:10 partyvan jfa-go[578046]:         panicmem: panic(memoryError)
May 15 14:16:10 partyvan jfa-go[578046]: /usr/lib/go/src/runtime/signal_unix.go:925 (0x4808a8)
May 15 14:16:10 partyvan jfa-go[578046]:         sigpanic: panicmem()
May 15 14:16:10 partyvan jfa-go[578046]: /home/glizzy/aur/jfa-go-git/src/jfa-go-git/api-messages.go:683 (0xf48ca2)
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf66ec5)
May 15 14:16:10 partyvan jfa-go[578046]:         (*Context).Next: c.handlers[c.index](c)
May 15 14:16:10 partyvan jfa-go[578046]: /home/glizzy/aur/jfa-go-git/src/jfa-go-git/auth.go:138 (0xf66de6)
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0x98b7ae)
May 15 14:16:10 partyvan jfa-go[578046]:         (*Context).Next: c.handlers[c.index](c)
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0x98b79b)
May 15 14:16:10 partyvan jfa-go[578046]:         CustomRecoveryWithWriter.func1: c.Next()
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0x98a8e4)
May 15 14:16:10 partyvan jfa-go[578046]:         (*Context).Next: c.handlers[c.index](c)
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0x98a8cb)
May 15 14:16:10 partyvan jfa-go[578046]:         LoggerWithConfig.func1: c.Next()
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0x989cf1)
May 15 14:16:10 partyvan jfa-go[578046]:         (*Context).Next: c.handlers[c.index](c)
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0x989780)
May 15 14:16:10 partyvan jfa-go[578046]:         (*Engine).handleHTTPRequest: c.Next()
May 15 14:16:10 partyvan jfa-go[578046]: /tmp/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0x9892a9)
May 15 14:16:10 partyvan jfa-go[578046]:         (*Engine).ServeHTTP: engine.handleHTTPRequest(c)
May 15 14:16:10 partyvan jfa-go[578046]: /usr/lib/go/src/net/http/server.go:3301 (0x72ac2d)
May 15 14:16:10 partyvan jfa-go[578046]:         serverHandler.ServeHTTP: handler.ServeHTTP(rw, req)
May 15 14:16:10 partyvan jfa-go[578046]: /usr/lib/go/src/net/http/server.go:2102 (0x7096e4)
May 15 14:16:10 partyvan jfa-go[578046]:         (*conn).serve: serverHandler{c.server}.ServeHTTP(w, w.req)
May 15 14:16:10 partyvan jfa-go[578046]: /usr/lib/go/src/runtime/asm_amd64.s:1700 (0x486ae0)
May 15 14:16:10 partyvan jfa-go[578046]:         goexit: BYTE        $0x90        // NOP
May 15 14:16:10 partyvan jfa-go[578046]: 
May 15 14:16:10 partyvan jfa-go[578046]: [GIN] POST(/users/discord) => 500
May 15 14:16:10 partyvan jfa-go[578046]: [GIN] GET(/users/announce) => 200
May 15 14:16:10 partyvan jfa-go[578046]: [GIN] GET(/users) => 200 <-- refresh

After refreshing the page or closing the dialog though, the discord account is still shown on my account as though I'd linked it. Similar effect happens from trying to link in the My Account area, though this time it offers a code, when I go through the linking process with the bot it gives an error in the logs, and then shows no indication on the webui that its worked, but after refreshing it shows my account as linked.

[raku-cat]

Apologies for comment spam, I've gone through and re-added my bot with the following settings per the wiki here as shown:

Privileged permissions (tried to adapt the instructions, assuming it needs message content intent)

Bot/oauth perms

And after I re-added it, the I was able to actually properly relink my discord without any errors as opposed to the above, but the command still doesn't work:

Still no associated logs after this error, but now it does actually create the invite in the admin panel again:

So its back to working exactly the same as it was in #378 (comment)
I will note, the whole time I've been using an admin jellyfin account, marked as admin in jfa-go, it's never seemed like a perms issue, as even before the recent commits, the command created invites when I ran it and didn't when non-admins tried, as it does now, though now it shows a proper "no permission" message for non-admins trying it.

I should also say I'm not actually sure what the behavior I should be expecting when its working, like how the invite is delivered if the command was to run as intended, I've tried manually creating an invite and checking send to with a user entered and it also doesn't do anything.

[raku-cat]

It's been a long time since I first set this up so there has been updates to the unstable branch. Here's is a screenshot of my jfa-go version:

If you really want to test out with my outdated image, feel free to download it here:

https://drive.google.com/file/d/1Nbxl-w62Zapq3TIqu62-5K0xc5kN0pXw/view?usp=drive_link

I can confirm that the /inv is still working for me on this image. If it still doesn't work then it might be some configuration issues on your end.

Forgot to test this, got docker set up and gave this image a shot, to my surprise invites work!

I did have to kick and re-add my bot, but I used identical bot permissions as I've shown above, so the only change was the jfa-go version, and a quick glance over the diff of the two (here) doesn't show anything obvious.
On a hunch, I moved my jfa config from my currently running verison to re-trigger the onboarding, and the invites also worked!
I then narrowed this down to likely being a quirk in the config.ini, and diffed the new config.ini and my old existing one, and based on that, went and enabled Invite emails:

And it works now!

So this seems to be the issue, maybe an older version of jfa during the onboarding didn't enable this, or maybe I turned it off manually, either way it is a little confusing that global invite enabled/disabled is controlled by a setting named "Invite emails", so it probably just needs a wording change or perhaps make it so this global "invite enabled" state is controlled by if any of the invite methods are enabled, or something similar

[hrfee]

Wow, thank you for all your work on figuring this out. I'm still parsing through everything here but in 41ddf73 i've renamed "Invite Emails" to "Invite Messages" as I should've a long time ago, and the program now prints a message in the console if the setting is disabled when you try /inv or "Send To" from the admin page

[raku-cat]

No problem! Appreciate the fix!