Internal Error The Directory Does Not Exists Admin
from Files tab in Power User Vi Discussion in 'Plesk 10.x for Windows Issues, Fixes, How-To' started by PatrickSR, Feb 22, 2012. PatrickSR Kilo Poster Messages: 14 I have a new install of Plesk Panel 10.3. I have created a subscription for my website. When I manage the Webspace from the Power User View and go to the Files tab, or click on the Manage Files link under the Files section I get the following error: Internal error: The directory does not exists "admin" I,ve gone into the File Sharing settings under Server Management and I see the following settings: Web Folder root URL: my-domain.com/files Folder for public files storage: my-domain.com/files/public URL for visitor access to public files: my-domain.com/files/public-docs Enable password-protection of public files: Checked Enable password-protection of public files: my-domain.com/files/protected I'm assuming these values were created by default. Do I need to change these, and should it be in the httpdocs directory (my-domain.com/httpdocs)? My question is: Where exactly are the directories created? In the domain web root, or the root/httpdocs? The error appears to be correct, the admin directory does not exist in either of these 2 folders. Thanks for the help. Patrick PatrickSR, Feb 22, 2012 #1 PatrickSR Kilo Poster Messages: 14 Ok so looking at IIS I see in the website an files application, but its url is vhosts/fs?? Now i'm really confused. Do all webspace file sharing happen from this url? PatrickSR, Feb 22, 2012 #2 (You must log in or sign up to reply here.) Show Ignored Content Share This Page Tweet Your name or email address: Do you already have an account? No, create an account now. Yes, my password is: Forgot your password? Stay logged in Odin Forum Home Forum > More Products Discussion > Older Panel Software Versions > Plesk 10.x for Windows > P
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base Documentation Downloads Plesk University Release notes Blog Become a Partner Russian German French Spanish Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any Search File Sharing fails with:Internal error: The directory does not exist "admin" Article ID: 121263, created on Apr 22, 2014, last review on May http://forum.odin.com/threads/internal-error-the-directory-does-not-exists-admin-from-files-tab-in-power-user-vi.257554/ 8, 2014 Applies to: Plesk 11.5 for Linux Symptoms The following error appears upon an attempt to open subscriptions File Sharing tab: Internal error: The directory does not exist "admin" Cause The dav_module (shared) and dav_fs_module (shared) Apache modulus were not loaded. Resolution Run the following command to check if dav_module (shared) https://kb.plesk.com/en/121263 and dav_fs_module (shared) are presented: # httpd -M | grep dav Make sure that files are presented on the server: # ls -l /usr/lib64/httpd/modules/mod_dav* -rwxr-xr-x 1 root root 52016 Apr 4 06:57 /usr/lib64/httpd/modules/mod_dav_fs.so -rwxr-xr-x 1 root root 93328 Apr 4 06:57 /usr/lib64/httpd/modules/mod_dav.so Add the following string in /etc/httpd/conf/httpd.conf: LoadModule dav_module modules/mod_dav.so LoadModule dav_fs_module modules/mod_dav_fs.so Reload httpd: #service httpd reload Search Words file sharing The directory does not exist "admin" mod_dav a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f Email subscription for changes to this article RSS subscription for changes to this article Save as PDF Was this article helpful? Tell us how we may improve it. No Yes University Training & Certification Product Expert Program Partners Become a Partner Company About Us Leadership Team Press Room Contact Us Keep in touch © 2016 Parallels IP Holdings GmbH. All rights reserved. Plesk and the Plesk logo are trademarks of Parallels IP Holdings GmbH. Terms and Conditi
Cloud apps, the contents of this article cannot be applied to Atlassian Cloud applications. About the Health Check This health check scans your current user directories to determine if there https://confluence.atlassian.com/confkb/health-check-internal-administrator-user-829068290.html is an internal administrator available.When Confluence is set up for the first time, a local administrative account is created - separate from any LDAP or external user management that is set up. In the event that external user management is inaccessible, this user account allows administrative access to the instance. Understanding the Results Icon Result What this means Healthy status if internal error the internal directory exists, the directory have at least 1 admin user, Confluence is not configured to use SSO. The Health Check has passed and your Internal Admin user is configured according to best practices. Confluence is configured to use Crowd SSO. The Health Check has passed because the environment uses SSO technologies. Confluence internal user directory does not exist or is internal error the disabled. This environment does not have an active Internal User Directory, or it is not active. See the Configuring User Directories user guide for instructions on creating a new User Directory or alternatively review instructions to activate your Internal Directory if your Internal User Directory is disabled. Confluence has an enabled internal user directory, however there are no users in this directory. The Internal User directory does not contain any users. Create an Admin User within this user directory by following the steps in: Add users and set permissions. Confluence has an enabled internal user directory, however it's administrator user does not exist or is disabled. The Health Check has failed to detect a user with enough permissions to quickly gain access to the environment in the event of an External User Directory failure. Create an Admin User within this user directory by following the steps in: Add users and set permissions. Confluence wasn't able to access the directory with the ID