I have a problem with my installation in Centos. The problem is I can't access my front end page. If I open the front end there's only a blank page. But the admin part is ok. I already change the permission to 777.
These are the catalog, admin, download, image, system and vqmod.
I already checked the database connections and it is working in the admin part.
I don't know where did I go wrong.
If I navigate the folder like image. I got this error
Forbidden
You don't have permission to access /image/ on this server.
Apache/2.2.15 (CentOS) Server at giftregistrys3.metro.com.ph Port 80
I think the reason are the permissions. But I already change the permissions.. :(
Hope you can help me with this.
Related
Currently running a WHM / Cpanel server running Centos. Server seems to be running fine no issues there. However I'm using a deployment process to put files outside of the document root. e.g.
~/deployment
instead of:
~/public_html
Obviously I need to point public_html to this folder so my site will run. So, I'm removing the public_html and creating a symlink and pointing it to the new deployment folder. This results in a 500 error.
So looking at the logs I've discovered that it produces the following error:
Directory "/home/xyz/deployment" is writeable by group
Checking the file permissions looks as though the symlink is 777 where i need it to be 755 for the server to allow viewing.
Is there a setting in WHM ? Is there a setting in Centos? I have another box running that doesn't have this issue so I'm assuming that this is related to the current setup of this machine.
Any help would be appreciated, thanks.
when you create a hard link from a file or folder, This file/folder inherits the accesses and permissions of the original file/folder, and in soft link it will be 777 permission, so i think you can use rsync options for both purpose :
1- have a folder with all files in source
2- have your own permissions in folder
After installation tableau server i'm not redirected to Create Admin User page, instead i'm redirected to page for Sign In, with Sign in failed error.
I'm trying to Sign in with my active directory user but still i'm getting sign in failed error.
i set username like this:
Domain\user
would you please someone tell me what is wrong?
The problem was i didn't have unrestricted admin privilege access on server.
I am currently running a fresh install of CentOS 7 (64-bit). This machine isn't used for anything except for storage via Samba. However, for some strange reason, I can't see to get the share to be writable through windows. With the drive mapped, I can read the file lists and browse (even accessing files), but I cannot write any new files.
The steps that I took was to install samba via yum. I added a system user, bdawson, and then added that same user as a Samba user. I then logged in as that user and make a directory called storage (path being /home/bdawson/Storage).
I then edited my Samba config and added the following:
[Storage]
valid users = bdawson,#bdawson
path = /home/bdawson/Storage
write list = bdawson,#bdawson
/home/bdawson was chown -R'd to be owned by bdawson:bdawson. File permissions are set to 0755 for both /home/bdawson and /home/bdawson/Storage.
At this point, I am not sure what I'm doing wrong that is preventing me from being able to write. This same configuration worked just fine on a different machine, so I'm at a complete loss. (Side note: Samba logs aren't showing any issues and watching the Samba connections via Webmin does show that I am connecting and reading from the share, but attempts to write to it fail saying I need permission.)
After a lot of digging, I discovered this was due to a missing SELinux label. This was not an issue with my Ubuntu share, since Ubuntu doesn't use SELinux.
There is a possibility to install Owncloud with a php script setup-owncloud.php.
I have uploaded this file to my domain.
and startet the script with the Webbrowser.
I found out it has downloaded the files to the server, so far the script is working.
then it will request a admin name/pwd a db name, db user and db pwd.
I add this information hit the next button - then nothing happen except a white page (no error, no Information)
if i go to www.domain.com/owncloud/
the starting page come requesting again a admin name/pwd a db name, db user and db pwd
so the information are not stored nor the page corectly started
thanks for feedback
have a nice day
vinc
I think your file is not named correctly. The setup file with your values for database, etc, is
config/config.php
I´m trying to follow the Zend Lucene Search Tutorial from Ganesh H S and it´s giving me an error.
Message: fopen(/home/zerego/application/lucene-data/read.lock.file) [function.fopen]: failed to open stream: Permission denied
And if i click in "function.fopen" it show me an other message:
Exception
Message: Resource 'function.fopen' not found
Stack trace:
#0 /home/zerego/library/Zend/Acl.php(774): Zend_Acl->get('function.fopen')
#1 /home/zerego/application/plugins/AccessCheck.php(26): Zend_Acl->isAllowed('admin', 'function.fopen', 'index')
My folder is with 755 permissions and i have tried with 777 but i thing the problem is with my ACL.
I need to give some kind of permissions in my ACL ? or i need to give those kind of permissions in de .htaccess ?
I think you "click" on the Link shown on your Browser when the error appears or? Your Application trys to open an action "function.fopen" wich is not configured in your acl. But thats not important, the link will send you to php documentation and has nothing to do with your application.
The Error is an permission problem, talk to your webhost if you or the "server" is allowed to write/read from the provided directory (group/user).
I had this problem.
What worked in my case is that, aside from chmod 777, is that I changed the owner of the files to the web server user.
In my case my web server runs as daemon. Make sure that the web server user is set as the owner of the index directory and the index files within the directory.
You can use the chown command to change the owner of the files and the folder.
you might have to do 'sudo chown daemon'. I had to on my mac because the daemon user isn't an actual user on the mac system.