-
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
Locast2Plex closes at login again #288
Comments
I've read from others using this and similar tools for Locast that they are enforcing some sort of captcha during login. It may not be a simple fix. |
Yet when I login on the Locast website, it never asks for a captcha. |
I've noticed this too and can't give a reason why. Only relaying what I've heard from others. |
Hi, |
Same issue as above, I can't see anything to edit on our side that's making a difference. It was working fine holding the connection until I rebooted and the script kicked off on login. |
Hello all 0.6.7 should fix this issue. |
overwrote the files in my lib folder with 0.6.7 version and it's working again. Thanks! |
"Locast2Plex is now online." Words I love to see. Thanks for all you do! |
I can't seem to get the latest update to work. It's still picking up version 0.6.5 when I do a Docker Run: docker run -v /share/CACHEDEV1_DATA/appdata/locast2plex/config.ini:/app/config.ini -p 6077:6077 tgorg/locast2plex Do I need to remove the old instance and how eactly do I do that? |
Stop the container then do a docker-compose pull to get the latest files and try again. |
Ok. I've gotten teh docker compose to build a container with v 0.6.7 but it still fails on the login. I thought v 0.6.7 was supposed to fix everything without me needing to copy in the special app rgistration key. |
Sorry. I still ended up with V 0.6.5 not 0.6.7. I downloaded adn extracted the latest verision with a folder and set up the docker-compose.yml as indicated on tgorg/locast2plex and ran the docker-compose up in the same folder yet it didn't create the new version. I also not only stopped the old container. I deleted instances with QNAP container station then deleted all fo teh folders in my share having to do with locast2plex though the folders I delted were for a much older version. |
If your using 'latest' tag try replacing it with '0.6.7'. Worked for me on unraid. I was pulling 0.6.5 still days later. tgorg/locast2plex:0.6.7 |
That worked to some degree. 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 ws 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 seem bvious but I don't use docker much and online documentation can leave a bit to be desired as in teh docker rm. |
I'm reopening this issue because it's doing the same thing again tonight. I downloaded locast2plex again incase there was a new version and it still does it.
The text was updated successfully, but these errors were encountered: