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

PAS doesnt work anymore #25

Closed
mondychan opened this issue Jul 23, 2020 · 6 comments
Closed

PAS doesnt work anymore #25

mondychan opened this issue Jul 23, 2020 · 6 comments

Comments

@mondychan
Copy link

mondychan commented Jul 23, 2020

hello

with the latest image of PAS "sabrsorensen/alpine-plex_autoscan:latest" commited to github at 7/23/2020 at 9:52 am (dunno the timezone github uses, if it uses my default then its CET) - DIGEST = (2247ea93f9d4)

PAS starts to throw error

2020-07-23_20-04-35

can be fixed with editing the binding inside the docker container for /rclone_config to

2020-07-23_21-04-17

and edit the rclone config entry in the file
/opt/appdata/plexautoscan/config/config.json
to
"CONFIG": "/rclone_config/rclone.conf",

fixes the issue

could anyone incorporate this workaround into the deployment code?

@dallensmith
Copy link

same issue here

@smashingtags
Copy link

Will look at this shortly am at the beach atm, thanks guys

@pazport
Copy link

pazport commented Jul 24, 2020

mine as done the update last night. and now. i can't access it on web-browser. but it is still sending signal to plex for time being. so i restarted plexautoscan and now. it just keeps saying i don't have PAS setup

@smashingtags
Copy link

hello

with the latest image of PAS "sabrsorensen/alpine-plex_autoscan:latest" commited to github at 7/23/2020 at 9:52 am (dunno the timezone github uses, if it uses my default then its CET) - DIGEST = (2247ea93f9d4)

PAS starts to throw error

2020-07-23_20-04-35

can be fixed with editing the binding inside the docker container for /rclone_config to

2020-07-23_21-04-17

and edit the rclone config entry in the file
/opt/appdata/plexautoscan/config/config.json
to
"CONFIG": "/rclone_config/rclone.conf",

fixes the issue

could anyone incorporate this workaround into the deployment code?

I have tried to implement this fix, working from the beach so much appreciated if you guys can test and make sure I got it right. Then I can close out this issue.

@mondychan
Copy link
Author

when you recreate the container now, it creates an internal storage for /config binding, instead of the "Regular" "/opt/appdata/plexautoscan/config" binding to "/config" , so the log now shows "no config.json found" error

2020-07-25_10-30-49
2020-07-25_10-31-56

after fixing this lil hiccup to the regular binding path, it works, so the other problem with rclone.conf has been fixed :slight_smile:
2020-07-25_10-33-35

tho i would advise (not rly sure if it matters, but better be safe than sorry) to make this binding read-only
2020-07-25_10-30-41

@smashingtags
Copy link

Should be all good now worked for me no errors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants