Hi everyone !
Sorry if this has been asked before, This is my first post.
I have problem with apache. It always gives me a 403 forbidden error when trying to access a page.
I had everything working good for a long time running a Joomla page on my QNAP TVS-871 on QTS 4.2.4.
Then I tried to install Drupal 8, So i made a database and a user in mariasql, created a Drupal directory in /share/Web
and pointed my browser to that adress. In the middle if the installation script (right after the database setup page) it all
stopped working and are giving 403 to anything, including phpMyAdmin, joomla, etc etc.
Did Drupal change my configuration? is that even possible? I am lost here I can´t find anything wrong but still not working
what am i missing?
Anyone have any idea what i should look for?
Thank you for your time
Magnus
Apache is giving error 403 Forbidden errors
-
- Starting out
- Posts: 14
- Joined: Mon Apr 27, 2015 2:27 am
-
- Starting out
- Posts: 14
- Joined: Mon Apr 27, 2015 2:27 am
Re: Apache is giving error 403 Forbidden errors
To answer my own question, I found a hidden .htaccess file that blocked the access.
When showing hidden files i could see it. after deleting it it all works... After much
hairpulling it was a simple solution !!!
When showing hidden files i could see it. after deleting it it all works... After much
hairpulling it was a simple solution !!!
- schumaku
- Guru
- Posts: 43578
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: Apache is giving error 403 Forbidden errors
Hi Magnus,
There can be (no, there are ...) good reasons why Web app installations place a .htaccess file ... better check out what is breaking it instead of removing it please.
It is possible that some Apache modules required by the .htaccess are not loaded.
Compare wiht the list of modules, ie.
[~] # /usr/local/apache/bin/apache -M
[Fri May 26 00:43:45.370284 2017] [so:warn] [pid 22455:tid 139867010664320] AH01574: module proxy_module is already loaded, skipping
AH00558: apache: Could not reliably determine the server's fully qualified domain name, using 192.168.1.250. Set the 'ServerName' directive globally to suppress this message
Loaded Modules:
core_module (static)
so_module (static)
http_module (static)
mpm_worker_module (static)
unixd_module (shared)
access_compat_module (shared)
authz_core_module (shared)
filter_module (shared)
mime_module (shared)
setenvif_module (shared)
socache_shmcb_module (shared)
log_config_module (shared)
rewrite_module (shared)
alias_module (shared)
actions_module (shared)
dir_module (shared)
autoindex_module (shared)
http2_module (shared)
deflate_module (shared)
reqtimeout_module (shared)
cgi_module (shared)
version_module (shared)
env_module (shared)
authn_file_module (shared)
authn_core_module (shared)
authz_user_module (shared)
auth_basic_module (shared)
headers_module (shared)
fastcgi_module (shared)
proxy_module (shared)
proxy_wstunnel_module (shared)
proxy_http_module (shared)
ssl_module (shared)
-Kurt
There can be (no, there are ...) good reasons why Web app installations place a .htaccess file ... better check out what is breaking it instead of removing it please.
It is possible that some Apache modules required by the .htaccess are not loaded.
Compare wiht the list of modules, ie.
[~] # /usr/local/apache/bin/apache -M
[Fri May 26 00:43:45.370284 2017] [so:warn] [pid 22455:tid 139867010664320] AH01574: module proxy_module is already loaded, skipping
AH00558: apache: Could not reliably determine the server's fully qualified domain name, using 192.168.1.250. Set the 'ServerName' directive globally to suppress this message
Loaded Modules:
core_module (static)
so_module (static)
http_module (static)
mpm_worker_module (static)
unixd_module (shared)
access_compat_module (shared)
authz_core_module (shared)
filter_module (shared)
mime_module (shared)
setenvif_module (shared)
socache_shmcb_module (shared)
log_config_module (shared)
rewrite_module (shared)
alias_module (shared)
actions_module (shared)
dir_module (shared)
autoindex_module (shared)
http2_module (shared)
deflate_module (shared)
reqtimeout_module (shared)
cgi_module (shared)
version_module (shared)
env_module (shared)
authn_file_module (shared)
authn_core_module (shared)
authz_user_module (shared)
auth_basic_module (shared)
headers_module (shared)
fastcgi_module (shared)
proxy_module (shared)
proxy_wstunnel_module (shared)
proxy_http_module (shared)
ssl_module (shared)
-Kurt
- karlegas
- Know my way around
- Posts: 124
- Joined: Thu Apr 26, 2012 2:38 pm
- Contact:
Re: Apache is giving error 403 Forbidden errors
I continue have problems to access to the Apache server and other interfaces I opened a ticket but I don't see any solution yet
I tried add the modules but I don't found any htacces file on my web site for the NAS
I tried add the modules but I don't found any htacces file on my web site for the NAS
Favorite Apps: Deluge - Plex, Twonky and TVmobili streaming
Models: TVS-463 QTS 4.3.4 / TS-221 QTS 4.3.3
Website: http://www.karlegas.com Blog
Website: http://www.naseros.com Tutorials and News in Spanish for QNAP NAS
Models: TVS-463 QTS 4.3.4 / TS-221 QTS 4.3.3
Website: http://www.karlegas.com Blog
Website: http://www.naseros.com Tutorials and News in Spanish for QNAP NAS
- schumaku
- Guru
- Posts: 43578
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: Apache is giving error 403 Forbidden errors
In what aspect - is Apache not serving simple htm or html files, not serving php, ...? Start with a simple test, a simple html or php helloworld ...karlegas wrote:I continue have problems to access to the Apache server and other interfaces I opened a ticket but I don't see any solution yet ... I tried add the modules but I don't found any htacces file on my web site for the NAS