-
Notifications
You must be signed in to change notification settings - Fork 478
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
Error 403 from the begining #199
Comments
Have you used the auto-installer ? and please give some details on your OS etc |
I've used Vagrant 100% autoinstaller, and my OS is Ubuntu 14.04 x64. I've also have tried to replace from .htaccess -"Indexes" to "+Indexes" |
I think I see the problem: drwx------ 1 vagrant vagrant 4096 Dec 9 11:04 html drwxrwxr-x 1 vagrant vagrant 4096 Dec 9 11:05 myproject I believed that the owner must be www-data So i tried this: # Share an additional folder to the guest VM. The first argument is the path on the host to the actual folder.
# The second argument is the path on the guest to mount the folder.
config.vm.synced_folder "./", "/var/www/html",
owner: "www-data",
group: "www-data",
mount_options: ["dmode=775,fmode=775"] and I fix it |
Becuse i've changed the permissions composer doesn't work... |
Hey, thanks for the feedback! I think you are right, this was also a problem in another project that used nearly the same auto-installer, and there's I've fixed it by replacing
with
I cannot explain exactly why and how this works better, but it does in lots of installation of HUGE (https://github.com/panique/huge/blob/master/_one-click-installation/bootstrap.sh), therefore it should be the same for MINI. I've changed this now in develop and master branch inside this project here, please gimme some time for testting ! :) |
better mkdir to prevent problems (issue #199)
I've just install mini, and it happens that some how when I access 192.168.33.44 apache shows a 403 forbbiden message.
This is my site configuration:
The rewrite mod is enabled.
If I disabled the site, I can access to the server but not to the myproject folder.
The text was updated successfully, but these errors were encountered: