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

Permissions problem #66

Closed
Rickta opened this issue Feb 17, 2021 · 3 comments
Closed

Permissions problem #66

Rickta opened this issue Feb 17, 2021 · 3 comments
Labels
wontfix This will not be worked on

Comments

@Rickta
Copy link

Rickta commented Feb 17, 2021

I just installed gsdock from the Community Applications on Unraid server 6.8.3. The version of Goodsync seems to be 10.9.32.2. I have installed Goodsync version 11 on two Windows computers (which work fine with GoodSync and Goodsync Connect), but I am have trouble getting the gsdock server configured with my Goodsync account. From the Web GUI in gsdock, if I try to login to my Goodsync account, I get the following error:

Writing bookmark: Cannot create Bookmarks folder: Can not create folder /root/.goodsync: cannot make folder /root/.goodsync: Permission denied (error 13)

Now I am stuck. Any ideas would be appreciated.
Rick
imaslug.rt@gmail.com

@ceepeebee213
Copy link

I'm in the same boat. I picked up an N54L microserver, and have a bunch of disks configured to house GSync data, however I can't set it up. It's setup on 3 other devices fine (Windows and 2 x NAS - WD and Synology)

@Rickta
Copy link
Author

Rickta commented Feb 21, 2021

I found a solution that I found here:

https://forums.unraid.net/topic/51921-job-opportunity-need-someone-to-help-build-a-docker-for-goodsync/page/2/?tab=comments#comment-891715&searchlight=1

See "flubster" entries.

Updating the version to the latest (as described in the post above) fixes the problem. Apparently, the location of the folder for license mapping changed. This new version seems to fix it.

Change the repository to flubster/gsdock in Docker/Gsdock/repository and restart the container. It will pull the newest version from flubster and (for me) it fixed the licensing issue. Don't forget to restart the container after it updates.

Hope this works.

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions!

@stale stale bot added the wontfix This will not be worked on label Jun 2, 2021
@stale stale bot closed this as completed Jun 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants