I am trying to install a package from URL into my local server and I am getting this error:
Error
Archive does not exist
Warning
JFolder: :files: Path is not a folder. Path: C:\xampp\htdocs\Joomla\tmp\install_53170ad5161e0
JFolder: :folder: Path is not a folder. Path: C:\xampp\htdocs\Joomla\tmp\install_53170ad5161e0
JFolder: :files: Path is not a folder. Path: C:\xampp\htdocs\Joomla\tmp\install_53170ad5161e0
JInstaller: :Install: Cannot find Joomla XML setup file
The tmp paths are correct and the remote file URL link is correct too. I've also tried by clearing the tmp folder but still does not help. The package installs correctly when the package file is uploaded.
Does anyone know what's happening?
If you are using Linux
You may need to fix the directory permissions. Check if there is any directory of which CHMOD is not 0777. If there are folders which their CHMOD value is lower than 0777 set them to 0777. After installation you have to change chmod back to 0755
Even though this post is quite old I hope that someone searching for a solution will stumble upon this question and answer:
I had the same problem when installing and updating Joomla on a Windows host, problems were related to directory permissions on various directories like "tmp", "modules" etc not being set. When I used the FTP client's chmod functionality the server responded with 504 Command not implemented for that parameter (showing in green instead of red in my FTP protocol so I ) so permissions were never changed. I had to alter the security settings using the hoster's web interface, after that installing packages worked as expected.
only for this folder:
chmod 777 /opt/lampp/htdocs
OR
project folder -
chmod 777 /opt/lampp/htdocs/project_name
in /var/www/you_site/httpdocs/configuration.php change value:
$ftp_enable = '0'; set 0 from 1
Related
I've been trying to set up my own web server with the raspberry pi3 b+ and it was going good so far i could made a ddns and access it from any other wifi or anything, the only problem was that i couldn't change the default "Debian apache" site.
I googled a lot about it and everybody said that all i have to do is change the root directory /var/www/to my directory but i just couldn't save the files, as it asked me if I wanna overwrite it - I pressed yes but it told me that I don't have permission for that I also couldn't overwrite the index.html file that was in the default folder. Is there anything I can do about it?
I had the same problem while doing this myself. You need to open terminal from the Raspberry Pi, or SSH. You need to change the folder type to 755, which allows the user to read,write,execute. Make sure that the directory you do this to is the /var/www/html folder.
All you need to do is type:
chmod -R 755 (dir)
dir = directory of the file.
If you'd like to change a file, such as the default index.html file in there, use 744 instead of 755.
After this, if you want to start the server, just type in
sudo service apache2 start
Here's a link for how to install the apache2 package.
https://pimylifeup.com/raspberry-pi-web-server/
This is a weird one... On Ubuntu 14.04 I have a directory called /lib. As root, or on the server as a user with group privileges, I can write to this directory. Over FTP as the same user with group privileges I cannot, I get a Permission Denied error...
If I rename the /lib directory to anything else (in this case /lib-new) I can write to the directory over FTP.
What could be causing a Permission Denied error based purely on the name of the directory?
I've checked and tested the permissions of the directory (777, 775, 755, 664 and 644) as well as the directory above (/public_html - the root directory for the server) and nothing helps, unless I rename the directory something other than lib.
Please help, as SSH-ing into the server to make changes to anything within /lib is time consuming!
EDIT: The FTP server I'm using is ProFTP if it helps.
Try adding RLimitChroot off to /etc/proftpd.conf. May need to restart X for this change to take affect. By default, I think it will do the same thing to /etc directory as well.
I have a website which I copied to this location. The public_html folder was also uploaded with the other folders but it is not showing up. Please guide me. Thanks.
As you are using DreamHost web hosting you wont have any control over ssh and chmod , chown commands. I think dreamhost wont use cPanel for shared hosting, they have their own control panel, so there is nothing you can do, Ask dreamHost support to reinitialize your public_html directory. Surely they will do that. I searched on dreamhost forum and found these link-
https://discussion.dreamhost.com/thread-13646-post-13647.html#pid13647
https://discussion.dreamhost.com/thread-128630.html
Currently in your case i saw that there is no issue related to public_html (technically "Document Root" ) directory coz as your http://www.inspuratesystems.com/second/ is pointing to correct directory , and your documentRoot is parent of that directory, So if your documentRoot was wrong then there were no chance to access that that url, currently your domain is opening a correct index.html file which indicates that your documentRoot is there.
Create a index.html or home.html file there manually (from their web based file manager) and see if it is working or not, if it works then there is some issue with your uploading.
Your hosting provider seems to be dreamhost.com
Please check out this thread, according to which public_html seems to be a special case on dreamhost:
https://discussion.dreamhost.com/thread-144453.html
and/or this:
Getting a 'Not Found' error on my website?
Hope it helps!
Make sure that the public_html folder has execute permissions
chmod a+x public_html
That will allow execute permissions for everybody.
Perhaps it's possible that server (apache?) hides folders named public_html? Also check that group others have read and execute permissions for that folder.
In folder /path/to/second/ run
chmod ugo+rx .
chmod -R ugo+rx public_html
to set folder visible.
cpanel may handle the "public_html" folder in a unique way. Try uploading to a folder like: /home/yourusername/public_html/second/files/ instead of /home/yourusername/public_html/second/public_html/
If you are wanting to create a new distinct website at inspuratesystems.com/second/ you don't need a second "public_html" folder. Just put them in the /home/yourusername/public_html/second directory.
If you are using a linux or OS X server, you may need to change the permissions on the folder.
Did you checked if the folder is hidden attribute?
If you execute ls -a in terminal, you will know about it's existence. If it is present then please try giving it read & execute permission (using chmod 555 command). Give write permission if you are planning to write something or take feedback from users (using chmod 777).
I tried some of this options above but unfortunately none worked. Instead I discovered that in CPanel you have a "Preferences" tab and in that tab you have a "User Manager" function. You can there edit the ftp user that you created before in CPanel. On the "User Manager" funcion you can find the "Home Directory" configuration. On that home directory you just choose the "public_html". When you configure the user in the ftp account on your ftp platform, it goes directly to the path you defined in CPanel.
I have a local development environment setup on my mac and I am having permission issues accessing a folder in my ~/Sites directory.
Essentially I have Folder A in my Dropbox folder.
I created a SymLink of Folder A to my ~/Sites folder
ln -s ~/Sites ~/Dropbox/FolderA
When I try to access Folder A like so: localhost/~username/FolderA
The page says You don't have permission to access /~username/FolderA on this server
Can someone help me figure out this problem. When I do the same thing on MAMP I don't have this issue. Thanks in advance.
Go on private/etc/apache2/users/, edit your usernamefile.conf, add to the Options line, the option SymLinksIfOwnerMatch, don't use FollowSymLinks if the directory contains important personal files, if for example the dir that you want link is are under your Documents or Dropbox.
Remember that the directory linked by your symbolic link must have 755 permission, and so her parents!
Let's suppose you have /Users/foo/Dropbox/MySites/BarSite, both Users, foo, Dropbox, MySites, BarSite must be 755.
when i´ll look over my site, created with Kohana 3.2 the wild error "Kohana_Exception [ 0 ]: Directory APPPATH\cache must be writable" appears.
Im using windows 7 with XAMPP and have no idea what to do.
Because the directory "logs" is writable and there are no problems with this dir, but with the cache directory.
please give 777 permission for application/logs folder.
also give 777 permission for application/cache folder.
mod_rewrite and Curl Should be enabled for kohana. These are all are basic requirements of kohana.
Oh yeah, I read an answer from someone yesterday but I only figured it out today. What I did was this:
Go inside application/
Create a new folder cache/
Go inside cache/
Create a empty textfile. (I created empty.txt)
Then thats it. hope it helps
Does folder 'cache' exist in your application folder ?