When I run wordpress folder in my localhost, (localhost/wordpress) I am getting the error as
Warning: Unknown: failed to open stream: Permission denied in Unknown on line 0
Fatal error: Unknown: Failed opening required 'C:/xampp/htdocs/wordpress/index.php' (include_path='.;\xampp\php\PEAR') in Unknown on line 0
Have you installed Apache or are you using EasyPHP or xampp for this install? Most likely its a permissions issue (chmod 777 in linux on the folder OR read/write in windows for the htdocs or www folder)
Related
I was able to save my GoDaddy site locally that was built with their website builder. I installed Wampserver and got the site to run locally on my Windows laptop.
when I uploaded the site to Hostinger I got the following messages on the page:
Warning: require(../scripts/config.inc.php): failed to open stream: No such file or directory in /home/u350095573/domains/mywebsite.com/public_html/index.php on line 12
Fatal error: require(): Failed opening required '../scripts/config.inc.php' (include_path='.:/opt/alt/php74/usr/share/pear') in /home/u350095573/domains/mywebsite.com/public_html/index.php on line 12
I am new to this, when looking at the index.php in Windows Notepad i noticed it says "require" config.inc.php and wampserver.lib.php under the scripts folder on my Windows laptop.
I am not sure if I'm supposed to change that, delete that, or upload all of Winamp to the host.
Thank you,
Ricardo
I'm trying to setup a Laravel project on Valet.
I'm getting this error:
Warning: require(/Users/davina/Developer/learn-laravel-graphql/public/../vendor/autoload.php): failed to open stream: No such file or directory in /Users/davina/Developer/learn-laravel-graphql/public/index.php on line 24
Fatal error: require(): Failed opening required '/Users/davina/Developer/learn-laravel-graphql/public/../vendor/autoload.php' (include_path='.:/usr/local/Cellar/php/7.3.1/share/php/pear') in /Users/davina/Developer/learn-laravel-graphql/public/index.php on line 24
Trying to link either the project root or /public folders results in the above error instead of Laravel's default welcome screen.
How do I resolve this?
Try to navigate to the project folder root and run the command:
composer -i
sudo chmod 755 -R folder_name
Create the .env file, if is fresh application just copy the content of the .env.example file.
inside the project folder again: php artisan key:generate
After those steps all up and running for me :)
Solves the issue for me.
Looks like you have a fresh installation of laravel here...or, you just cloned the repo?
If so, the first thing you should do is to try and install the packages that Laravel uses.
Within those packages is a file called "autoload.php" which your server is looking for here.
Now, to do that, simply navigate within your terminal to the directory of your project and run: composer install.
Wait for it to finish and then, try to continue from there.
I am using Artifactory Professional, version 5.6.0 rev 50600900
When I try to deploy a file through the Artifactory web UI, I'm getting an error: '<filename> is undefined' in a red popup box.
When I look in the system log, I see:
2018-05-15 08:25:41,037 [http-nio-8081-exec-123] [ERROR] (o.a.r.c.e.GlobalExceptionMapper:48) - Permission denied
java.io.IOException: Permission denied
The time corresponds to the time I tried the deploy
Uploads using a curl command or via the Artifactory plugin in Jenkins work without any problems.
I am an administrator on Artifactory. other users with Delete/Overwrite, Deploy/Cache, Annotate and Read also are not able to upload to repos via the web UI.
I get the undefined error with all files i try to deploy, large or small. this error occurs for users on windows, mac os and linux.
thanks in advance for any help.
Looks like an file system permissions issue. Make sure that the OS user running Artifactory has write permissions to <ARTIFACTORY_HOME>/data/tmp.
The artifacts uploaded from the UI are temporally saved under this folder.
I ssh to my VPS where there is a vagrant box that runs a symfony project.
When i try to access the project i am getting the error:
`Fatal error: Uncaught RuntimeException: Failed to write cache file` and
`Fatal error: Uncaught exception 'RuntimeException' with message 'Could not create cache directory`
I have tried fixing file permissions as mentioned here: http://symfony.com/doc/current/setup/file_permissions.html
and even changed chmod to 777. But still getting same error.
I also tried everything there: symfony2 : failed to write cache directory
It just won't work. Any help would be much appreciated.
My VPS is running ubuntu 16.04 and vagrant is latest version with image ubuntu/trusty
If you are running Apache check your /etc/httpd/conf/httpd.conf file and find your entry for your website in there. Check to see what user Apache is running the site as. You'll want to make sure the directories and files that make up your Symfony app belong to that user and the group the user is in as well. If you are logged in as root and are in the your Symfony directory you can run:
chown -R user:group *
to change all the files and directories to that user and group. Note to replace user and group in the command above with the actual username and group.
If you still have troubles after you've found the user apache is running as, try removing your symfony files completely (if it is a fresh project that you haven' been working on) and rebuild it while you are superuser'd (su) as that user. You probably built your project as root or another user.
A fresh plone install is failing with this error:
Copying buildout skeleton
Fixing up bin/buildout
Building Zope/Plone; this takes a while...
Buildout returned an error code: 126; Aborting.
Buildout failed. Unable to continue
Installation has failed.
See the detailed installation log at /home/adrigen/Downloads/Plone-4.3.2-UnifiedInstaller/install.log
The log says
/bin/sh: 1: /home/adrigen/Develop/Plone-4.3.2/zinstance/bin/buildout: Permission denied
The folder permissions say
drwxr-sr-x 7 plone_buildout plone_group 4096 Nov 21 19:01 Plone-4.3.2
This is when I run the install with and without a sudo prefix. What might the issue be here?