You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the extension requires (and warns it wont work otherwise) the port. So the required output is HTTPS://Sub.Domain.com:/
when i click on the "Media Not Found" overseerr link in plex web in Chrome browser.
Again, any way to ignore the port?
If it helps, the port I use is 5055, however, reverse proxy omits that requirement under the sub-domain i have setup.
Thank you for taking a look at this question.
The text was updated successfully, but these errors were encountered:
Using version 1.7.1 of the extension on Chrome browser, and I have configured overseerr with the correct path, API and host.
My installation is proxied and on a sub-domain such as my use case. So i dont use the port to access it.
I get HTTPS://Sub.Domain.com/ and connect to overseerr.
However, the extension requires (and warns it wont work otherwise) the port. So the required output is HTTPS://Sub.Domain.com:/
when i click on the "Media Not Found" overseerr link in plex web in Chrome browser.
Again, any way to ignore the port?
If it helps, the port I use is 5055, however, reverse proxy omits that requirement under the sub-domain i have setup.
Thank you for taking a look at this question.
The text was updated successfully, but these errors were encountered: