<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>I am trying to open Facebook,                Yahoo!, Yandex, Tumblr, Google etc., and                instead I am getting “Welcome to nginx!” page</title><meta name="viewport" content="width=device-width,initial-scale=1"><link rel="stylesheet" href="../../css/style_en.css">

Planning your ingress-nginx migration? Start here:
kubernetes.nginx.org.

<input class="side-menu" type="checkbox" id="side-menu">

english

русский

news

about

download

security

documentation

faq

books

community

enterprise

community forum (new)

x.com

blog

njs

ingress controller

gateway fabric

I am trying to open Facebook,                Yahoo!, Yandex, Tumblr, Google etc., and                instead I am getting “Welcome to nginx!” page

Q:
I am trying to open Facebook, Yahoo!, Yandex, Google, or some
other well known web site and instead I am getting a blank web page
with a message referring to nginx: “Welcome to nginx!” or
“404 Not Found / nginx”.

I suspect something is wrong and there is probably a malicious attempt
to direct me to a rogue web page (to break into my computer, do
phishing etc.). Why is that, and what has nginx to do with my attempts
to connect to Facebook (Yahoo!, Google, etc.) ?

A:
First of all, the “Welcome to nginx!” page you see is
NOT our website. At nginx, we write and distribute a free

open source web server software. A web page saying
“Welcome to nginx!” is just a diagnostics response that
can be produced by any of the websites out there, running nginx
web server. Currently, nginx is the 2nd most popular open source
web server in the world, it’s being used by over 126,000,000 (or
14% of the Internet) websites. Most of these websites are
legitimate, but some aren’t. Our software was created with a good
reason of enabling performance and scalability on the Internet,
it is licensed under
popular open source license, and has nothing to do with any
kind of threatening or malicious activity per se —
nginx is NOT a malware, and it is NOT on your computer. But someone’s
malware could have indeed tampered with your computer or router,
redirecting you to a fraudulent Internet server.

We recommend running an anti-virus check on your computer, and
we recommend to check and verify your entire system setup with the
help of your ISP, or another support personnel:

(Disclaimer: at nginx we are not responsible for any negative
impact or effects that the actions below might cause. Use the
following recommendations at your own risk, especially if
you aren’t an experienced user of your operating system and/or
Internet applications. In no event shall nginx be liable for
any direct, indirect, incidental, special, exemplary, or
consequential damages, including, but not limited to loss of
use, data, or profits; or business interruption).

Check your TCP/IP settings and see if the DNS servers
configuration matches the valid one (suggested by your Internet
service provider or IT support personnel).

Use Google
Public DNS, and see if it fixes the problem. From Google’s
description of its Public DNS — "Google Public DNS is a free,
global Domain Name System (DNS) resolution service,
that you can use as an alternative to your current DNS
provider. [..] By using Google Public DNS you can: Speed up your
browsing experience. Improve your security."

Clear your DNS resolver cache. On Microsoft Windows XP go to
Start > Run, and then type the following command:
"ipconfig /flushdns". On Microsoft Vista, Windows 7, and
Windows 8 click on Start logo, follow All Programs > Accessories,
right-click on Command Prompt, choose "Run As Administrator",
type in "ipconfig /flushdns" and hit Enter.

Click the "page reload" button in your browser. Clear browser
data (cache, cookies etc.). E.g. with Chrome find and click
"Clear Browsing Data" (Settings > Under the Hood). With Internet
Explorer find Tools > Internet Options > General.
Caution: you may be deleting saved passwords information
here, so do it carefully and check what exact actions you are
performing.

Check if the "hosts" file doesn’t contain entries other
than "127.0.0.1 localhost", and if so — if these entries are for
the web site you’re trying to reach. The "hosts" files is located in
C:\WINDOWS\system32\drivers\etc directory. Typically there should
be just one entry in it, for "127.0.0.1 localhost", that’s it. The
"hosts" file can be viewed and edited with your standard
Notepad application.

Check the plugins and extensions installed with your browser.
Re-install your browser or try an alternative one if possible.

Something must be wrong with your operating
system settings, home router setup, or browser
configuration, if you are trying to access a well known web site
and what you get instead is “Welcome to nginx!”.
This should NOT happen if your computers and network are
clean and safe.

If changing DNS servers to Google Public DNS, flushing DNS resolver
cache, fixing your browser configuration, or cleaning "hosts" file
(when applicable) have helped, it might be that there’s a malware
somewhere on your PC or around. Find and clean it using
your preferred anti-virus and anti-malware tools.

Additional articles that might be helpful:

DCWG.org:

How can you detect if your computer has been violated and infected
with DNS Changer?

How to clean up or fix malicious software (“malware”)
associated with DNS Changer

Microsoft:

Malicious Software Removal Tool

How can I reset the Hosts file back to the default?

How to reset Internet Protocol (TCP/IP)

Firefox Help:

Disable or remove Add-ons

Tech-Recipes:

DNS Cache Flush, Clear, or Reset in Vista,
Windows 7, and Windows 8


<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>nginx for Windows</title><meta name="viewport" content="width=device-width,initial-scale=1"><link rel="stylesheet" href="../../css/style_en.css">

Planning your ingress-nginx migration? Start here:
kubernetes.nginx.org.

<input class="side-menu" type="checkbox" id="side-menu">

english

русский

news

about

download

security

documentation

faq

books

community

enterprise

community forum (new)

x.com

blog

njs

ingress controller

gateway fabric

nginx for Windows

Known issues
Possible future enhancements

Version of nginx for Windows uses the native Win32 API (not the Cygwin emulation
layer).
Only the select() and poll() (1.15.9)
connection processing methods are currently used,
so high performance and scalability should not be expected.
Due to this and some other known issues version of nginx for Windows
is considered to be a beta version.
At this time, it provides almost the same functionality as a UNIX version
of nginx except for
XSLT filter, image filter, GeoIP module, and embedded Perl language.

To install nginx/Windows, download
the latest mainline version distribution (1.31.0),
since the mainline branch of nginx contains all known fixes.
Then unpack the distribution, go to the
nginx-1.31.0
directory, and run nginx.
Here is an example for the drive C: root directory:

cd c:\
unzip nginx-1.31.0.zip
cd nginx-1.31.0
start nginx

Run the tasklist command-line utility
to see nginx processes:

C:\nginx-1.31.0>tasklist /fi "imagename eq nginx.exe"

Image Name           PID Session Name     Session#    Mem Usage
=============== ======== ============== ========== ============
nginx.exe            652 Console                 0      2 780 K
nginx.exe           1332 Console                 0      3 112 K

One of the processes is the master process and another is the worker process.
If nginx does not start, look for the reason in
the error log file logs\error.log.
If the log file has not been created, the reason for this should be reported
in the Windows Event Log.
If an error page is displayed instead of the expected page, also look
for the reason in the logs\error.log file.

nginx/Windows uses the directory where it has been run as the prefix
for relative paths in the configuration.
In the example above, the prefix is
C:\nginx-1.31.0\.
Paths in a configuration file must be specified in UNIX-style using
forward slashes:

access_log   logs/site.log;
root         C:/web/html;

nginx/Windows runs as a standard console application (not a service),
and it can be managed using the following commands:

nginx -s stop
fast shutdown

nginx -s quit
graceful shutdown

nginx -s reload

changing configuration,
starting new worker processes with a new configuration,
graceful shutdown of old worker processes

nginx -s reopen
re-opening log files

Known issues

Although several workers can be started, only one of them
actually does any work.

The UDP (and, inherently, QUIC) functionality is not supported.

Possible future enhancements

Running as a service.

Using the I/O completion ports as a connection processing method.

Using multiple worker threads inside a single worker process.