If you're accessing the root of your CloudFront distribution, you need to set a default root object: http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/DefaultRootObject.html To specify a default root object using the CloudFront console: Sign in to the AWS Management Console and open the Amazon CloudFront console at https://console.aws....


The access control configuration changed in 2.4, and old configurations aren't compatible without some changes. See here. If your old config was Allow from all (no IP addresses blocked from accessing the service), then Require all granted is the new functional equivilent.


If you've got access to the mysql database, you can change the grant tables directly: UPDATE mysql.user SET Host='%' WHERE Host='localhost' AND User='username'; ...and an analogous UPDATE-statement to change it back. Also you might need to make changes to the mysql.db table as well: UPDATE mysql.db SET Host='%' WHERE Host='localhost' AND User='username'; ...


I've just had the same issue and while Kousha's answer does solve the problem for index.html in the root path, my problem was also with sub-directories as I used those combined with index.html to get "pretty urls" (example.com/something/ rather than "ugly" example.com/something.html) Partially it's Amazon's fault as well, because when you set up CloudFront ...


This will most likely be related to SELinux semanage port -l | grep http_port_t http_port_t tcp 80, 81, 443, 488, 8008, 8009, 8443, 9000 As you can see from the output above with SELinux in enforcing mode http is only allowed to bind to the listed ports. The solution is to add the ports you want to bind on to the list semanage port ...


I go a step further and always set the attributes of my mountpoint directories to immutable using chattr. This is accomplished with chattr +i /mountpoint (with the mount unmounted). This would error-out on new write activity and also protects the mount point in other situations. But I suppose you could use the mountpoint command, too ;)


Accessing the contents (or more specifically file metadata except for filename) of a directory requires that the directory have the execute bit set. Your recursive chmod removed that permission, so you lost that access. If you are using the -R option of chmod is better to avoid using the numeric version of the permissions, and instead run (using your ...


Adding the key from stdin worked for me: cat /path/to/id_rsa | ssh-add -k -


The permissions, content and all attributes are part of the inode. The name is in the directory entry. The permissions are not inherited recursively (except when you use default in Posix ACLs). When you delete a file, internally you just remove a hard link from the directory entry to the inode. When all hardlinks are removed and the inode is not in use, the ...


There is no way to set the UID using the definition of Pod, but Kubernetes saves the UID of sourced volume. So, you can set the UID by InitContainer, which launches before the main container, just add it to the containers path of the Deployment: initContainers: - name: volume-mount-hack image: busybox command: ["sh", "-c", "chown -R 200:200 /nexus"] ...


In Ubuntu 14.04 the file to change user and group in PHP-FPM is: /etc/php5/fpm/pool.d/www.conf. In this file change these parameters: user = www group = www listen.owner = www listen.group = www


That is one of the reasons sudo exists. Simply allow your users to run 1 single command with only the pre-authorized command-line options and most obvious circumventions are solved. e.g. #/etc/sudoers %users ALL = (some_uid) NOPASSWD: /usr/bin/ssh -i /home/some_uid/.ssh/remote-host.key username@remotehost sets up sudo so all members of the group users can ...


There are basically two different approaches: Initially start running as root, bind to the privileged port, and then drop down to an unprivileged user. inetd, or xinetd runs privileged, and forwards the requests to web server running unprivileged.


SELinux prevents you from running a system service where the binary is in a user's home directory, or in your case, the root user's home directory. To fix the problem, copy the binary to a proper directory such as /usr/local/bin and call it from there.


From info ls, under the What information is listed? section, regarding the output produced by -l: A file with any other combination of alternate access methods is marked with a '+' character. Generally, it means it has an ACL set.


You want namei. # namei -l /var/log/nginx/error.log f: /var/log/nginx/error.log drwxr-xr-x root root / drwxr-xr-x root root var drwxr-xr-x root root log drwx------ nginx nginx nginx -rw-r--r-- nginx nginx error.log Note that this command is Linux-specific and may not exist on other operating systems. Also do not confuse it with the namei() system ...


Check that your syslog daemon is working correctly; this caused the issue for me. Run the following command logger 'Hello world' Does the command return within a reasonable amount of time? Does 'Hello world' show up in /var/log/syslog? If this is not the case, the syslog daemon has crashed. Restarting it should fix your problem.


So for this you can harken back to your DOS days (if you had them) and utilize the 8.3 naming convention, which gets around the invalid NTFS security descriptors that aren't there. Steps to remove the invalid new destination folders: Open a command prompt with admin rights to the root folder where these new folders are listed. Use the command DIR /X to ...


Directories (like /var/log/httpd) require both read and execute permissions in order to be traversed. So when you add "r" to the directory, it only allows the world to see the contents, but not to enter into it and continue into other directories. Try chmod -R go+rX /var/log/httpd


From Administrative Tools > Computer Management, expand System Tools > Local Users and Groups > Groups. Double-click the Users group and click Add. Click Locations and select your computer node. Now: Type Network Service into the 'Enter the object names' OR Click Advanced, then Find Now and select it from the Search Results.


Just to expand a little on the above answers here is a real world use case. I run the enterprise log analysis application Splunk on a Redhat box. It runs under the splunk user and splunk group. This prevents splunk accessing the logs in /var/log as they are only accessible by root (or a sudo admin) In order to allow read only access for splunk only I've ...


I know it is an old post but I think that I can help more with a functional example that I always use! In apache 2.2 would be like: <Location /> Order deny, allow allow from all </Location> <Location /adm> Order deny, allow deny from all allow from myniceip </Location> <...


I had the same issue and it seems that there is some bug in docker or overlay2 if directory content is created in one layer and its permissions are changed in other. As a workaround you could copy sources to temporary directory: COPY . /src And then move it to /var/www/html and setup permissions (in one RUN command): RUN rm -rf /var/www/html && ...


Before adding a User you must first create a global Login, under Security -> Logins. Once the login exists you can add them as a User under a particular database.


You're misunderstanding both settings there: remote_user is an Ansible setting that controls the SSH user Ansible is using to connect: ssh ${REMOTE_USER}@remotehost someusername ALL=(ALL) NOPASSWD:ALL is a sudo configuration that allows the user someusername to execute all commands in any host without a password. It does not allow anyone to issue commands ...


When you own the directory you are allowed to do anything to it and the contents within it based on the directory's permissions. Therefore, despite not owning the file, you were still able to delete it because you had read/write permission to the directory in which the file resided.


I resolved this problem by the following steps: Open a Command Prompt "As Administrator" Run the following commands: takeown /f G:\folder /r /d y icacls G:\folder /grant administrators:F /T REF: http://www.richardawilson.com/2013/12/an-error-occurred-while-applying.html


It's not a caddy issue, nor a user-permissions issue. Linux doesn't allow processes to listen on low-level ports by default. To grant access: sudo setcap CAP_NET_BIND_SERVICE=+eip $(which caddy) source: superuser: Allow non-root process to bind to port 80 and 443?


To go with your accepted answer ... You can combine those commands together as: sudo setfacl -Rm d:g:groupnamehere:rwx,g:groupnamehere:rwx /base/path/members/


This could be caused by User Account Control, a feature (hated by many) which makes so that, even if you have administrative rights, you don't actually have them unless you explicitly request them. There are two distinct policies governing UAC behaviour (both found in Computer settings\Windows settings\Security settings\Local policies\Security options), one ...

Only top voted, non community-wiki answers of a minimum length are eligible