![]() bash: line 0: cd: /srv/shiny-server/sample-apps/demo: Permission denied ![]() The application exited during initialization'.ĥ\ so, being well-versed in various things, look at the logs, but see nothing that helps much (typical of most logs.) su: ignore -preserve-environment, it's mutually exclusive to -login. Ģ\ then, cd to /srv/shiny-server/sample-apps, and create a symbolic link to the demo directory on my desktopģ\ chown everything to root (also tried shiny, makes no difference).Ĥ\ point browser at :3838/sample-apps/demo/, but get the very popular (based on peolle who run into this) 'An error has occurred. Here is what I tried:ġ\ on desktop for my main account, created a directory called demo. Problem(s) arise when trying to run a shiny app that isn't one of the sample-apps that comes bundled with the server. Point browser at :3838, and up pops the sample-apps/hello page. Used systemctl to start and enable shiny server, using default config (meaning, usual file locations, and usual 3838 port). Yum installed the latest RPM (1.5.9.923) - no problems. Now tesla account doesn't see all my nas, and the mount is mountable now.Installing shiny server on CentOS 7 box. =>I just needed to give read + read/write access to tesla account for TeslaCam ACLs and that is it. => I still had to give read-only ACL to "all" to have access to TeslaCam share (I didn't want tesla account to see all my nas) => I had to give read-only ACL to "all" to have access to TeslaCam share (I didn't want tesla account to see all my nas) So I narrowed it down to ACL settings.Īnd the actual fix was to give read-only access to the user which I wanted to create share for. ![]() Then I tried to use main admin login which worked. I googled that the problem is not on the client, but on the server (freenas) source3/smbd/uid.c:386(change_to_user_internal)Ĭode: mount -vvv -t cifs -o 'username=tesla,password=some_password,vers=2.1' //192.168.66.22/TeslaCam /mnt/test-mountīut then I got stuck on Permission Denied. Network error - Windows cannot access \\server\homes" "Theres a problem accessing \\server\homes." (all shares using a dedicated AD server for authentication)Īfter making that change, i see this from windows 10: That U3 update should have the fix, with 'valid users=' as a aux param in home share.įor me, that has meant that the domain administrator can access their home share.īut I've not been able to get any other user to access their home share - so now i'm unsure if perhaps I've broken something else in trying to get this to work or if there is more fix required in U2.īefore making the 'valid user' change, I would be prompted to enter my credentials on the home share, where as on other shares I would not. I read in a similar bug report: (don't think it's been linked here yet) but I certainly used to be able to access my home share on both windows 10 and Linux. I can't be certain my permissions were ever setup exactly correct. ![]() I upgraded to 11.2 recently, and I have also upgraded the pool. is a symlink outside the share pathĬonn_rootdir =/mnt/storage/share/private/test source3/smbd/vfs.c:1305(check_reduced_name)Ĭheck_reduced_name: Bad access attempt. source3/smbd/uid.c:386(change_to_user_internal)Ĭhange_to_user_internal: chdir_current_service() failed!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |