Title: 403 error on subdomain
Last modified: October 23, 2018

---

# 403 error on subdomain

 *  [vebbmaster](https://wordpress.org/support/users/vebbmaster/)
 * (@vebbmaster)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/403-error-on-subdomain/)
 * Hi! I tried to change my default image folder to a subdomain (img.domain.com)
   and now all the files I upload there are set to permission 640 – meaning they
   are not visible to “world” (i.e. website visitors). I can’t even see them in 
   WordPress.
 * I believe this is due to iThemes Security, but I cannot figure out how to fix
   it other than MANUALLY changing the file permissions after every upload.
 * Please help!

Viewing 1 replies (of 1 total)

 *  Thread Starter [vebbmaster](https://wordpress.org/support/users/vebbmaster/)
 * (@vebbmaster)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/403-error-on-subdomain/#post-10807604)
 * Ok, I fixed it by changing the permissions on the folder in my server. It was
   set to 750 and, for whatever reason, 755 works fine.
 * Hope that helps someone else!

Viewing 1 replies (of 1 total)

The topic ‘403 error on subdomain’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [vebbmaster](https://wordpress.org/support/users/vebbmaster/)
 * Last activity: [7 years, 7 months ago](https://wordpress.org/support/topic/403-error-on-subdomain/#post-10807604)
 * Status: not resolved