-
Notifications
You must be signed in to change notification settings - Fork 43
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
Error in Function login: Forbidden Version 1.24.1.4931 #297
Comments
@fastdaddyboy Your screenshot shows you are using version V0.6.5 You need the latest (v0.6.7) for Locast login to work. |
D'oh. You're correct. I updated Plex, and forgot to update the locast2plex code. All better now. |
I've tried loading v0.6.7. It's now returning an error about port 6077 already in use. When I display used ports it shows it's used by locast2plex. I thought perhaps it ws because it was running under admin when I was trying to create under my own userid. That wasn't the case. I've tried to remove the container but it won't accept the names I'm using. I don't see docker rm needing the container id. I've tried removing instances and via Container Station where it appeared to be successful but when I do a docker image LS they still appear and I can't deelete the app from container station (it can't find it). Sorry if this seems obvious but I don't use docker much and online documentation can leave a bit to be desired as in teh docker rm. |
So, Locast announced today that they were ceasing operations immediately. I received this while watching LIVE with Kelly & Ryan this morning around 9:30 AM Eastern. |
Thanks. I received an email about cancelling my subscription but no reason given and allowed me to supposedly re-subscribe. I saw the announcment about shutting down a few hours later. |
Greetings,
This issue first appeared maybe a month ago, and I found some code to insert a session ID to get past the login challenge. However, it appears to be back. I am running the latest version:
This just started today, September 1, 2021.
The text was updated successfully, but these errors were encountered: