-
-
Notifications
You must be signed in to change notification settings - Fork 587
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
[SOLVED] ngnix 403 Forbidden / directory index of "/var/www/html/" is forbidden (firewall issues) #979
Comments
Docroot being empty has always meant a very stressed docker when it's happened to me - too many projects running, too little memory, failure to mount code. I recommend running only a few projects at a time, use |
Thanks for the response. In my case I tried to run only one project at the time. And no other VMs are running. I had the default 2 GB memory configured. I tried it with 4 GB without solving the problem. |
Yeah, do please reboot your host computer, also check the disk status on docker. Is your home directory (or directory this is mounted from) a regular NTFS volume? Is the drive it's on shared with docker? |
Oh, and please try another trivial project, to see whether it's the project. (I doubt it, but always good) |
I tested it with 2 GB memory again. This is the docker stats output:
What exactly do you referring to? I'm not a docker pro. :-)
Yes, standard NTFS. "Special" is, it uses Bitlocker for encryption. Which should not be a problem.
Yes
I tested https://github.com/drud/wordpress as mentioned here: Same 403 error. I runned ddev start
I set the host manually. ddev logs
|
The bottom line is that docker isn't mounting your /var/www/html (which is your project directory), and you can verify that by You may need to reset docker, assuming the reboot of your host computer didn't help. Here's the docker settings I was talking about: "Reset" is the bottom item on your docker settings. |
Please:
Thanks, |
I've followed your steps and stopped while trying to share the drive with Docker. I got an error caused by the firewall: The docs pointing to some possible issues: After some tries without help I force closed Kaspersky. Drive share was possible from there and the TYPO3 runs as expected. The files get linked into the container. The odd thing is, that it worked in the first place with Kaspersky and now it didn't... :-( So it seems, I have to look for Kaspersky-firewall+Docker issues. I write my results here, before closing this issue. |
In my case it's the same, as explained here: I removed the port 445 from the list and it seems to work. No error message while applying drive sharing. The DDEV project is working too. :-) EDIT:
Thank you @rfay for your time and help to nail it down. 👍 |
Thanks for working through this! I added a Stack Overflow answer at https://stackoverflow.com/questions/51227365/i-get-an-ngnix-403-forbidden-when-starting-ddev/51227366#51227366 - feel free to comment there if I didn't quite capture it. Linked to this though. |
I'd like to share, that the other opinion seems to work as well:
This is my current additional firewall network package rule: I leave the port 445 in the original ruleset and just create an additional one. |
Thanks for that! That link will be valuable to people. The bottom line is there's lots of firewall and virus checker interaction with Docker, all of which can break everything. |
Awesome, thanks @vaxul |
Describe the bug
After starting DDEV the ngnix return a 403.
To Reproduce
It worked a day ago. It just stopped working. I thought about it and the only thing I can tell is, the only thing what changed obvious, is my WIFI connection/office.
I not 100% sure, but it could be, that I forgot to
ddev stop
before closing my IDE and shutdown the computer.Expected behavior
It should show me the frontend of the TYPO3 which I tested a day ago.
Logs
Output from
ddev start
The "Unable to properly check port status" is normal in my case and were the same in the last days.
Output from
ddev logs
Version and configuration information (please complete the following information):
Additional context
I used
ddev ssh
to look into the container. The odd thing is, the DocRoot /var/www/html/ seems empty (besides .ddev-folder). Like if nothing get linked into the container.The text was updated successfully, but these errors were encountered: