I have an annoying problem with a new installation of Ci4.
I followed the official installation guide from CI4 official website.
I unpack the archive in the domain root directory (in my case it is /home/user/public_html) and then updated my nginx vhost file to point to /home/user/public_html/public.
It get 403 access forbidden.
I'm sure that it points to a proper directory because if i load doman.ext/robots.txt it show the file content.
I can't figure out where I'm going wrong
Related
I have an OpenLiteSpeed VPS WordPress install over at Vultr, and am trying to install a non-WordPress website into a sub-folder I created.
Ex.) https://example.com/test that is pointed to a new folder I created in the WordPress root install directory of /var/www/html/test
I created the directory and placed the files needed there that include an index.php file, however when I go to https://example.com/test, I receive a 404 Not Found error. I believe it has something to do with modifying the .htaccess file in the root of my WordPress install, but am unsure of what to modify 100%.
Any help is appreciated!
I tried modifying the Rewrite rules but am not confident in the options I chose. I since reverted the .htaccess file back to my default settings in which OpenLiteSpeed defines.
This can be closed out - I have it defined in my index.php file that resides in that folder point to a database I created in phpMyAdmin and I had the database field filled out incorrectly. Thank you to everyone who replied though. Oops!
Im on a mac running Sierra 10.12.2 and apache 2.4.23
I set up a localhost environment and a virtualhost for the domain cumsa.mx and installed wordpress on it. Without getting too into detail now, some changes were made on Git that modified the wp permalinks, and hence the .htaccess file through wp.
I went to my main httpd.conf file and told it to load the module mod_rewrite as suggested by a colleague since that was necessary to be able to modify the htaccess file. Regardless of that, activating this module results in my local environment for cumsa.mx to become "Forbidden".
Can anyone think of any idea why this wouldbe the case or which permissions I need to modify and how? Thanks!
After changing file permissions it worked but after 2 days started getting the same error in wordpress. I am working on server I had changed the .htaccess file too but there is no effect.
Delete your .htaccess file and update your permalink structure in admin,
This Snap may be help you
the problem cames when I tried to use the plugin OneSignal, once configured I get errors like "Failed to load resource: net::ERR_INVALID_RESPONSE", in fact, I get 403 - Forbidden. This is the file which can not be load:
wp-content/plugins/onesignal-free-web-push-notifications/sdk_files/OneSignalSDKWorker.js.php
I have create the following tests files: (with same permissions and owner)
wp-content/test.php // Error 403
test/test.php // OK, 200
wp-contest/test.php // OK, 200
so I came to the conclusion that for some reason, anything is blocking any php file located in /wp-content/ to be loaded.
I already checked .htaccess, I also backed it up and removed it, error persists.
File and folder permissions are also ok, 755 for folder and 644 for files.
I have installed OneSignal several tens of times in different webs and thats the first time I get this error, the site affected is a web that I just migrated from hosting to our vps.
Currently I have a single drupal site installed on apache 2.2 with php 5.3 on RHEL 6. I am moving servers and am trying to migrate the site. I have imported the database and htaccess, but I cannot access any of the pages other than the root of the site.
You may need to disable clean URLs before exporting the database, try to add ?q= before each path.
That happens when:
a) Apache mod_rewrite is not enabled. If you have root access then do sudo a2enmod rewrite
or
b) .htaccess file at the root folder isn't there, so you need to copy it again.
Here's a troubleshoot check list for mod_rewrite issues:
Make sure Apache's rewrite module is enabled: sudo a2enmod rewrite.
Make sure original .htaccess file is there in the root of your Drupal installation.
Make sure that the existing .htaccess file is getting read by Apache. To test it, add a this line in the beginning of the file and you should get a 500 Internal Server Error: ThisIsReallyABadSyntax.
If the .htaccess file is not in effect, make sure that the AllowOverride directive in the main Apache config file (usually /etc/apache2/httpd.conf on debian-based distros) is set to All. It might be set to None by default.
Finally, make sure that the clean URLs feature is enabled in Drupal settings.
With the phpinfo(); compare all the server specs, just to be sure both server are quite the same or similar.
Steps to migrate Drupal correctly:
Go to Configuration
find Clean URLs
Disable tick inside!
Clean cache!
Download your site file
Download your database
Create new database in your new site
Transfer file and database
Log in
10.Do this step to enable Clean URLs:
It's work 100% guaranteed !
Steps:
1. Download - Dev version (7.x-dev)
2. Find file .htaccess
3. just copy it to your server
4. That's it !