Error message if IIS 5.1 is stopped? - php

Is there a way to show any error message if IIS(5.1) is stopped or not working? We have got few websites on server 2000 and we want to show some message to end user if IIS doesn't respond due to any reasons.
I have tested this scenario on the test server, i just stopped the IIS and then try to access one of the website to see if i get any error message from IIS but i didn't get any IIS error message (IE: Internet Explorer cannot display the webpage)

Since IIS is the web server that receives HTTP requests and responds to them, you'd need to run another web server that does the same thing instead of IIS. If you're running a web server that can respond to HTTP requests with an error message though, you may as well use it to run your website. In short, unless you have another system sitting in front of your actual web server that can detect when the web server is down (say, a load balancer)... it's kind of an unrealistic proposal.

Related

Strange error An error just occured please try your request again: in yii2 application

H have a yii2 application running on a server with the following specification
yii2 version: 2.0.39.3
server : vultr VPS centos 8, running PHP version 7.2.24
web server NGINX ginx version: nginx/1.14.1
I have used it for months and everything works fine but in the past 3 days suddenly sometime it An error just occured please try sometime at the top of the page and sometime at the end of my page. This randomly appear when i refresh my server I am not sure. This happen whenever a request to the server is made and if an ajax request is made the server will receive the request but the client will receive and error message instead of a reply from he server, and also the message change the layout of the page it appears on. I have no clue as to where this could come from as i didn't do any server update of recent. Any help on this would be appreciated. attached is an image of what the error looks like from the page
Seems this errors related with Google Site Verification API. Check if you've not enabled "Maintenance Mode" etc.

500 Internal server error on php GET variables (CGI)

I'm currently writing a php API returning a JSON array. On my development environment everything seems to work fine.
So it was time for us to upload it on our dedicated server. But here is the deal. While our code is perfectly working on most environments, it is not on our server.
As I'm not an expert on multi-domain sites, we decided to try cPanel WHM, to easily configure our web server. Everything seems to work well, our API default page is running perfectly, showing the correct responses when a user is not permitted. As we are using custom urls, our .htaccess seems to work as well. But here is the rub! When I'm entering a $_GET variable to enter the API by using the correct keys, the server is automatically responding a 500 internal error.
I tried to look at the apache log file, it shows a
AH02812: attempt to invoke directory as script
I directly understood it was a httpd.conf problem. I replaced ScriptAlias by Alias, as most topics were saying. Now I don't have this error on my log, but its still showing the 500 internal server error.
We are currently running on Debian 7, with the latest stable version of cPanel. Our PHP version is 5.6.

Server returning 501 error, on file upload, when using nginx redirect

I have a multi-server architecture i.e Server a and server b, Now I want all the URL's hit containg a perticuler keyword should always go to server a, So I added a nginx rule (if url have keyword redirect to server a)
Now every thing is working fine but file upload is returning error code 501, But the issue resolves if I make an entry for server a IP in my /etc/hosts.
Using Angular and php
Ok So finally I found the issue. It was happening because of the options request.
Options is a special kind of request which is used when the client wants to determine other available methods to retrieve or process a document on the Web server.
So in my case my web server a and b have options method implemented while the server c (which is acting as a load balancer) does not resulting in 501 not implemented error

New IIS 7 site not loading any PHP/HTML pages

we have an IIS 7 server hosting different sites/applications.
Take not that this server is hosting other site/site-applications running on either asp or php. There is already an existing site application running thru fastCGI php.
I now added a new site (not a site-application) - a laravel 5.1 framework, to the IIS server, but this new site is not loading anything. Tried a test php page which echos phpinfo() only and i also made a static html file with just "Hello world" on it but to no avail.
Checked my handlers, and my php handler is there.
When i try to browse the sites host name I get this error:
The server at [mysubdom].[domain].com can't be found, because the DNS
lookup failed. DNS is the network service that translates a website's name to
its Internet address. This error is most often caused by having no connection to
the Internet or a misconfigured network. It can also be caused by an
unresponsive DNS server or a firewall preventing Google Chrome from accessing
the network.
Is this really a DNS problem?
Can you open it local? http://127.0.0.1/{websitename}/index.html with the hello world ... Don't always go directly to your binding address.. try to load on the server itself first.

Locally Hosted Website / Email went down. Website still works on localhost. Firewall, or PHP error?

I'm working IT at a small company. We host our own exchange servers, and web server. Yesterday, at around 2pm, external emails stopped getting through to us, and our website began serving a 500 error to everyone.
I didn't do much to the firewall (sonicwall 240) or the servers yesterday to cause this. We run WordPress and do not have automatic updates turned on. Also PHP did not update itself.
I'm not sure where to look first. Any ideas on how to track down what's throwing the 500 error? It's not a single page or script that's doing it. Even if I create my own .php file, it'll have a 500 error.
Fixed: Our web server lost it's internal IP address. I changed it back to 192.168.0.3 as it was before, and all is well.

Categories