Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
7
Newest
 Editor
Impact
~4k people reached

  • 0 posts edited
  • 0 helpful flags
  • 8 votes cast
Jan
30
comment PHP page refuses to appear despite checking php-fpm, SELinux, and nginx
@Tim Yeah, I did change it from the actual address. The link to the page was a less obvious nod to what the address is. Anyways, I do have a phpinfo file on the server, and you can find it here. Also, the 404 errors just started popping up for me too. I originally had it at the root domain, but I moved the PHP files to the testing/ directory, and made the root page just raw HTML. After I did that, I started getting the 404 error too.
Jan
30
revised PHP page refuses to appear despite checking php-fpm, SELinux, and nginx
Update URL(s)
Jan
30
revised PHP page refuses to appear despite checking php-fpm, SELinux, and nginx
Improved formatting
Jan
30
asked PHP page refuses to appear despite checking php-fpm, SELinux, and nginx
Jan
30
accepted nginx not logging errors to log files
Nov
17
comment Getting 404 on any text file (including robots.txt) with nginx
@warren I did, I had to move my nginx server blocks to /var/www/ in order to get SELinux to (more easily) recognize them as web server directories. This was an issue in the past, but as far as I know, SELinux should be labeling the directory correctly.
Nov
12
comment Getting 404 on any text file (including robots.txt) with nginx
@AaronMason I don't believe so, as far as I know I haven't specified anything about that nor do I have any files (as far as I know) that are mime.types.
Nov
12
comment nginx not logging errors to log files
@AaronMason The directory is owned by root (user and group), but it's the exact same permissions as other server blocks on the machine that are successfully able to write to logs.
Nov
11
awarded  Editor
Nov
11
asked Getting 404 on any text file (including robots.txt) with nginx
Nov
11
revised nginx not logging errors to log files
Corrected minor typo
Nov
11
asked nginx not logging errors to log files
Nov
6
comment New server block returns a 403 error
@MichaelHampton Ahhhhh, I see. I had tried to create a custom policy for SELinux for nginx that seemed to get it working, but my guess is that I would have had to update it everytime I add new content... ouch. Moving it all to /var/www/ seems to have solved everything. If you want to convert that to an answer, I will accept!
Nov
6
comment Member of the nginx group but unable to edit files in the web root
@Fredi The directory above the public_html directory for the actual server block (i.e. assuming hierarchy ../example.com/public_html/ is owned and group set to root. Would that be why?
Nov
6
comment New server block returns a 403 error
@MichaelHampton Silly mistake on my part, should have paid more attention. Set it to error logging and as expected got the info I needed. 2015/11/06 15:45:35 [error] 26467#0: *1 open() "/usr/share/nginx/example.com/public_html/index.html" failed (13: Permission denied), client: XXX.XX.XX.XXX, server: example.com, request: "GET / HTTP/1.1", host: "example.com" So now why would the nginx web server not have permission to open the file? The file is owned by my user and the group is set to nginx.
Nov
6
awarded  Commentator
Nov
6
comment Member of the nginx group but unable to edit files in the web root
@Fredi I see, that makes sense. So the most secure route would likely be to set the owner of the root web directory to my own user and keep the group as nginx. Assuming that is correct, this is what I will do on the machine. However, it's still frustrating that even with group r+w, I cannot edit or even enter the public web directory. Any ideas why that might be so? At this point, I think I almost just want to figure it out just to know why it isn't working.
Nov
6
comment Receiving a 404 for a file that exists in nginx web server
Thank you for the clarification, this makes perfect sense. I understand my fault now. Thanks!
Nov
6
accepted Receiving a 404 for a file that exists in nginx web server
Nov
6
awarded  Student