网页应用无法访问NAS图片：FreeBSD服务器挂载配置求助

Let’s walk through the most common issues that could be blocking your web app from accessing those NAS-hosted images, even though you can view them locally:

1. Verify Web Server Process Permissions #

First, remember that your local user has access, but the web server (like nginx, Apache, or whatever your app uses) runs under a dedicated user (usually www on FreeBSD). Here’s how to check if this user can read the mounted directory and follow the symlink:

• Run ls -ld /path/to/webroot/images_origin to confirm directory permissions match your mount_smbfs flags (0755 for directories, 0644 for files). The "other" group needs read + execute for directories and read for files.
• Double-check the UserID and GroupID you used in the mount_smbfs command. Are these IDs mapped to the web server’s user/group? If not, permissions won’t apply correctly for the web process.
• Test access directly as the web server user: su - www then try cat /path/to/webroot/images_origin/test.jpg. If this fails, permissions are the root cause.

2. Check Symlink Configuration #

Symlinks can trip up web servers in a few ways:

• If you used an absolute path for the symlink, the web server might restrict access to directories outside the web root. Try a relative symlink instead:

  cd /path/to/webroot
  ln -s ../nas/mount/images_origin images_origin
  

• Verify your web server allows following symlinks:
  • For nginx: Ensure disable_symlinks is not set to on (add disable_symlinks off; to your server block if needed).
  • For Apache: Make sure Options FollowSymLinks is enabled in your web root’s <Directory> block.

3. Validate NAS Share Permissions #

Your OVH NAS CIFS share might be restricting access even if the mount looks correct:

• Log into your OVH control panel to confirm the share allows the IP addresses of both FreeBSD servers.
• Check that the CIFS user you’re using for mounting has read access to the images_origin directory on the NAS.
• Ensure there are no NAS-side ACLs overriding basic share permissions.

4. Check for FreeBSD Security Restrictions #

FreeBSD’s built-in security tools might be blocking access:

• Use getfacl /path/to/webroot/images_origin to check for extra Access Control Lists that could deny the web server user access.
• If you’ve enabled the MAC Framework (e.g., MAC Portacl), verify there are no rules preventing the web server process from accessing the mount point or NAS IP.

5. Confirm Web App Path Configuration #

Double-check your web app’s setup:

• Is the app pointing to the correct path (e.g., /images_origin/) relative to the web root? A typo here would break links even if the filesystem is configured properly.
• Some apps cache file paths or permissions—try restarting the web app and web server to clear stale cache.

6. Verify Mount Stability #

SMB mounts can drop silently or have connectivity issues:

• Run mount to confirm the NAS share is still mounted properly. If it’s missing, add it to /etc/fstab to ensure it remounts on boot, and check /var/log/messages for mount errors.
• Test connectivity to the NAS with ping IP_NAS and smbutil status //IP_NAS to confirm the SMB connection is active.

内容的提问来源于stack exchange，提问作者Thomas Durand