I'm trying to set up Nagios on Nginx and I'm having trouble. I used this as a guide, but I still can't access Nagios from the web.
Just to confirm, I have nagios, fcgiwrap and php-cgi running. When i go to example.com/nagios, it brings up the nagios pages. But when i click on anything substantial, i get a message saying "Error: Could not read host and service status information!". I am sure it has something to do with permissions, but I can't figure out what the problem is.
Anyone know what i can do?
thanks in advance!
Found out my problem. It had to do with file permissions for the nagios files. Nginx ran under a different user, so it didn't have the right permissions to access the nagios files.
Related
I had to install Windows again today. The Laragon folder stayed in the same place. I installed Laragon again too and it worked again but when I access the sites locally the images do not appear.
When I try to access the file via browser like this:
http://localhost:90/mysite/wp-content/uploads/2022/08/logo.png
The message appears:
Forbidden
You don't have permission to access this resource.
It seems to be a folder permission issue.
Does anybody know how to solve this? I use Windows 10.
I am using Laragon 4.0.16 with Apache httpd-2.4.47-win64.
Thank you for your help.
This can have several causes.
You may not have set the required permissions for the folder or file.
The .htaccess does not contain all the required information.
The VirtualHost has an invalid value.
I have an ubuntu 14 server running nginx. I use it for a WordPress website
Out of the blue for no reason the php5-fpm shuts down automatically (I am not sure it even is called shutdown, I get the nginx error page).
This is the message I get now on my site::
An error occurred.
Sorry, the page you are looking for is currently unavailable. Please
try again later.
If you are the system administrator of this resource then you should
check the error log for details.
Faithfully yours, nginx.
I restarted the php5-fpm from the command line and my site goes up for 30-40 seconds and then it goes down again.
What can be the reason? How can the php5-fpm decided on itself to do this? If it helps I'll add that this is a digital ocean server
Thanks upfront!
I faced the same problem, Click here! to solve.
Its because your resource was fully utilized by xmlrpc.php. Possibly Brute force attack.
Block access to xmlrpc.php in nginx config.
I have XAMPP running fine on one machine and I have 2 WordPress installs running fine on that machine. I would like to be able to access and work on those WordPress installs on other machines on my network.
Right now, I have it set so that if I try to access those directories from another computer on the network, all I get is either the XAMPP splash screen, or a 404 error if I try to access specific folders.
I've researched this and researched this and I have found numerous posts about how to do this.... but only in bits and pieces.
Does anyone know of a step by step, start to finish, guide of how to do this? In layman's terms?
Remote (from another network) would be great too. But I'll cross that bridge once I figure this out.
Any help would be appreciated.
Thanks!
I would suggest rather than shared folders you use an FTP client / server - I use Filezilla server and client for my local sandbox testing server. This will give you additional info like file and folder groups and permissions.
Got to ask the question what OS? have you opened port 80 on the server machine?
Things like this can also occur on Linux if the folders and files do not have the correct groups for access and or permissions.
chown -R apache:apache /var/www/html
the above if on linux will assign all the folders and files to be accessed by the apache process. not having the correct groups assigned can give you 404 when you know the files are actually there.
also check the file and folder permissions,
different files and directories have permissions that specify who and what can read, write, modify and access them - this wordpress page gives a good overview of permissions
http://codex.wordpress.org/Changing_File_Permissions
edit p.s. to access then from other networks all you will have to do is forward ports from your router to your internal server then your ftp and www services will be accessable from the outside world. I would suggest using a .htpass htaccess password to protect your services at this point.
I had created a folder in my site, and uploaded drupal in it. But when I access it, the following error is coming
Internal Server Error
The server encountered an internal error or misconfiguration and was unable
to complete your request.
Please contact the server administrator, webmaster#xxxxxx.xx and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
There are literally thousands of things that can be wrong
Do you have access to the webserver logs? Check /log/apache/error.log for errors.
Have you already configured drupal correctly? Normally, when you surf to the drupal root directory, you get presented with an installer message.
Does your server support PHP?
I'd recommend any of the following:
Checking that you meet the Drupal requirements
Re-uploading the whole Drupal folder
Testing the Drupal folder (is this a custom installation, or just straight from the drupal website?) on local LAMPP webserver.
Assuming you're trying to run Drupal for the first time (ie run the installer), have you followed the pre-install setup?
Here's Drupal's "Quick install guide for beginners": http://drupal.org/documentation/install/beginners
Since you've already uploaded the code and you have your domain set up, you can probably skip down to the big labelled "Create the configuration file and grant permissions".
The first thing in this section is to create your settings.php file. Drupal won't work without this. You also need to set its file permissions to that Drupal's installer can update it.
My guess is that this is why you're getting the error. Follow the instructions on the page I linked you to above and you should be okay.
You'll also need to have a database ready for use by Drupal. The Drupal installer will populate the DB tables, but you need to at least have the empty DB ready for it to use.
Hope that helps.
When I attempt to update the code on a IIS webserver by replacing the old code with my new code, I receive 503 Service Unavailable replys when attempting to access any of the replaced pages on the server.
What is the cause of this failure and what steps can I take to correct such errors?
Thanks!
I would do a few things:
Check the windows event logs for any web related errors.
Check the IIS logs to see if there is anything odd with the requests.
Double check the permissions of all the new files, make sure they match the files that do work.
Perform an IISReset after you deployed.
Make sure your virtual directory, or sub folders are set up correctly in IIS and didn't change in the deployment.
If the associated ApplicationPool is disabled you also get the 'Service Unavailable' exception. (can be seen in the logs)
Re this answer, I seem to remember having a problem like this, and it turned out that it was because I was updating the files via ftp, and the there was some conflict between the rights of the FTP user and the IIS user.
I have spent hours looking for solution for Service Unavailable, 503 on IIS in Windows 2012 Server. In the end it helps to restart the server and everything works. Restart the IIS was not enough.
It is not the first time the restart help, the same issue was with FTP server on Windows 2012 Server.
Could be lots of things. Did you try iisreset after updating the pages?
I agree with Eugene. It could be lots of things. If you publish locally, can your local IIS run the pages?
You probably need to get together with whomever has access to the server to look at the errors. Short of that, can you try putting the old code back to see if it still works? If not, it's likely a configuration error.
Also, editing the web.config will get the application restarted. It's a useful trick when you can't access IIS.