Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The URL played through jellyfin has an additional "/" #168

Closed
1 task done
ashanzzz opened this issue Jun 27, 2022 · 5 comments · Fixed by #230
Closed
1 task done

The URL played through jellyfin has an additional "/" #168

ashanzzz opened this issue Jun 27, 2022 · 5 comments · Fixed by #230

Comments

@ashanzzz
Copy link

ashanzzz commented Jun 27, 2022

Description

The URL played through jellyfin has an additional "/"
Play on Jellyfin
url:http://192.168.33.15:8096//web/index.html#!/details?id=c3c5503754676a4abec029df1fc17fec&context=home&serverId=a4b8cfd8db8f4960b585e94415b7f480

Version

1.1.1

Steps to Reproduce

Jellyfin website, fill in: http://192.168.33.15:8096/

Screenshots

No response

Logs

No response

Platform

desktop

Device

docker

Operating System

docker

Browser

Edge

Additional Context

No response

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct
@Fallenbagel
Copy link
Owner

Are you on jellyfin 10.7.7?

@ashanzzz
Copy link
Author

Are you on jellyfin 10.7.7?

jellyfin 10.8.0

@Fallenbagel
Copy link
Owner

jellyfin 10.8.0

When you set it up
Did you write
http://jellyfin:8096/
Because if so that additional trailing slash is because of that. However its an easy fix. Hop onto discord ill help you

@github-actions
Copy link

👋 @ashanzzz, we use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with Jellyseerr.

@github-actions github-actions bot locked as off-topic and limited conversation to collaborators Jun 27, 2022
notfakie added a commit to notfakie/jellyseerr that referenced this issue Sep 12, 2022
Fallenbagel added a commit that referenced this issue Sep 26, 2022
@Fallenbagel
Copy link
Owner

🎉 This issue has been resolved in version 1.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.