I created a new virtual host on a VPS. i already point the domain to the server IP address. when I access the website it's gives me error 403 even the public_html has 755 file permission. what could be the problem?
EDIT: i found the following error log.
cannot server directory /home/batiktridaya/public_html: No matching directory (index.html, index.html, index.php, index.php4, index.php5) found, and server generated directory index forbidden by Options directive.
What are the permissions of the files within public_html, also what user is apache running as?
Related
I am using amazon linux ec2 instance i.e working fine with IP address.
My apache root directory is
/var/www/html
that is working fine when I am accessing my instance IP address.
Issue is when I am using my domain name. It's working only when I am adding "html" after domain name, like
domain/html
I implemented SSL certificate using let's encrypt library, may be that is reason of this issue
I tried to change my httpd.conf directory URL with www directory but that's not working.
Domain name continuously showing below error message but working when I am adding "html" at the end of domain name
Forbidden
You don't have permission to access this resource.
Looks like issue is with your vhost config, as you mentioned SSL certificates generated using Let's encrypt, check host file on below path and change document root directory with your original directory. Also check is there any other host file as well or not.
/etc/httpd/conf.d/vhost-le-ssl.conf
I own a domain on GoDaddy and am attempting to point it to my DigitalOcean-hosted website. Here are the steps I have taken so far:
I cloned the git repo containing all of my website files from local to my DigitalOcean server.
I added an # record on godaddy for my domain and pointed it to my DigitalOcean IP address.
IMPORTANT!! I modified /etc/apache2/sites-enabled/000-default.conf with my new VirtualHost pointing mydomain.com to index.html, NOT THE ROOT DIRECTORY.
I then proceeded to do 'service apache2 restart' while sshed to DigitalOcean on terminal.
I assumed this would work and then tested it out and went to mydomain.com. Not so much. This is the error I got:
Forbidden
You don't have permission to access / on this server.
Apache/2.4.7 (Ubuntu) Server at mydomain.com Port 80
This was obviously pretty surprising given that it was not redirecting to index.html, so I manually appended /index.html to mydomain.com only to find that it gave me an identical error only I could not access /index.html instead of /.
I have done this kind of things many times before, however I used subdomain records for godaddy on an existing domain instead of using a brand new domain with no subdomains. Where did I go wrong?
Thanks!
Brandon
UPDATE: I tried on a test subdomain with test.mydomain.com and got this new error:
Not Found
The requested URL / was not found on this server.
Apache/2.4.7 (Ubuntu) Server at test.mydomain.com Port 80
You noted you modified the virtual host to point to index.html but not the root directory. Apache would still use the root directory (DocumentRoot) to locate the index.html file. If it is looking in the wrong location it could explain the 403 error (looking in a place that the web server user [www-data] cannot read as an example).
Beyond that, a 403 like that could be permission related. You would want to ensure the DocumentRoot and index.html file have the ownership of www-data:www-data and they are all readable by the web server itself (755 for folders and 644 for files is the norm).
I have been installed LAMP server on Fedora 22 , but when i need access
my server localhost/myapp/public , I see this error
Forbidden
You don't have permission to access /myapp/public/ on this server.
Server unable to read htaccess file, denying access to be safe
How I can solve this isuue, I think this issue may be solving by modify
httpd.conf file ,but i don't know How do it , i am use apache2
Any Suggestions ?
You should have a corresponding error_log acess referencing an on-disk htaccess file.
If you use the "itk" MPM, it's likely an ITK problem. Otherwise, make sure all directories between root and your content directory are world readable and world executable, and that any .htaccess files are readable by the servers ID (www-data, apache, etc)
we just moved our Magento 1.7.0.2 shop from one server to the other. We did the following:
In root folder we adjusted rewrite base in .htaccess
We activated "using rewrite url" in System=>Configuration=>General=>Web
But now every time we open any link (e.g. domain.com/about) we get following error:
403 Forbidden
You don't have permission to access /var/www/***/index.php on this server.
Apache/2.2.16 (Debian) Server at www.domain.com Port 80
Only start page can be opened. If we turn off "using rewrite url" in System=>Configuration=>General=>Web everything works again, but then any URL has an index.php included e.g. domain.com/index.php/about. We use hosted vServer with Confixx 3pro as server management software. WebServer mod_rewrite is activated for every user in Confixx user management. register_globals, safe_mode, and open_basedir are tuned off for all users.
We checked all file permissions with standard magento-check.php and also checked user with chown command via ssh several times. All mandatory files are writable and are owned by necessary user.
Do you have any idea how we can fix this? Thank you in advance!
Best regards,
Marcus
A friend and I are using MAMP to develop a site. On my computer I can access CSS files in any folder under our /application root directory. On his computer, many of them have permission forbidden.
We did CHMOD 755 and checked that his htaccess wouldn't be restricting anything. What else could cause this difference in permissions?
Error:
GET http://mysite.loc/application/javascripts/bootstrap/bootstrap-typeahead.js 403 (Forbidden) wefinance/:26
ensure the higher level permissions are properly set as well (higher level is enforced first). Also did you sudo when setting the permissions?
Ensure permissions are set properly for the www group.
Make sure your apache is configured to allow the connection, as well.