Why would Nginx 1.14.2 show version 1.10.3 in error messagesNginx Error 413Nginx 413 error does not get to the browserApplication reports timeouts. However nginx has no record or lognginx large file upload gives HTTP Error 413 Request entity too large in railsnginx: try next upstream on http 200 response with custom header setis it normal for NGINX to accumulate connections in writing state?Apply client_max_body_size for a single URL onlyNginx: disconnect when client sends chunked body exceeding desired sizeclient_max_body_size not workingFile size increases while uploading to nginx server and fails
Can dirty bird feeders make birds sick?
How is dynamic resistance of a diode modeled for large voltage variations?
Is there a way to generate a mapping graph like this?
Are there any nuances between "dismiss" and "ignore"?
Circuit construction for execution of conditional statements using least significant bit
How does the +1 Keen Composite Longbow (+2 Str) work?
How can sister protect herself from impulse purchases with a credit card?
How could Dwarves prevent sand from filling up their settlements
Eigenvalues of the Laplace-Beltrami operator on a compact Riemannnian manifold
Do most Taxis give Receipts in London?
Why was Harry at the Weasley's at the beginning of Goblet of Fire but at the Dursleys' after?
Best practice for printing and evaluating formulas with the minimal coding
Separate the element after every 2nd ',' and push into next row in bash
Farthing / Riding
Is there a word for pant sleeves?
400–430 degrees Celsius heated bath
Do seaplanes need to get clearance for takeoff?
How to tease a romance without a cat and mouse chase?
Germany rejected my entry to Schengen countries
Why is there no current between two capacitors connected in series?
Why does an injection from a set to a countable set imply that set is countable?
What should I wear to go and sign an employment contract?
Vehemently against code formatting
Keeping the dodos out of the field
Why would Nginx 1.14.2 show version 1.10.3 in error messages
Nginx Error 413Nginx 413 error does not get to the browserApplication reports timeouts. However nginx has no record or lognginx large file upload gives HTTP Error 413 Request entity too large in railsnginx: try next upstream on http 200 response with custom header setis it normal for NGINX to accumulate connections in writing state?Apply client_max_body_size for a single URL onlyNginx: disconnect when client sends chunked body exceeding desired sizeclient_max_body_size not workingFile size increases while uploading to nginx server and fails
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I'm running nginx 1.14.2 on ubuntu 16. I'm having trouble figuring out a 413 error (which I'll address separately), but I noticed that when I post a file to the nginx server, it reports, presumably, the error message and the version of nginx:
<html>
<head>
<title>413 Request Entity Too Large</title>
</head>
<body bgcolor="white">
<center>
<h1>413 Request Entity Too Large</h1>
</center>
<hr>
<center>nginx/1.10.3 (Ubuntu)</center>
</body>
The command nginx -v shows the version to be 1.14.2. I checked the startup files to see if maybe they were pointing to some other version, but they all point to /usr/sbin/nginx which is what is telling me the version is 1.14.2.
So why does it say 1.10.3 in the error message?
I need to rule out this discrepancy as the cause of my other problem.
nginx
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
|
show 2 more comments
I'm running nginx 1.14.2 on ubuntu 16. I'm having trouble figuring out a 413 error (which I'll address separately), but I noticed that when I post a file to the nginx server, it reports, presumably, the error message and the version of nginx:
<html>
<head>
<title>413 Request Entity Too Large</title>
</head>
<body bgcolor="white">
<center>
<h1>413 Request Entity Too Large</h1>
</center>
<hr>
<center>nginx/1.10.3 (Ubuntu)</center>
</body>
The command nginx -v shows the version to be 1.14.2. I checked the startup files to see if maybe they were pointing to some other version, but they all point to /usr/sbin/nginx which is what is telling me the version is 1.14.2.
So why does it say 1.10.3 in the error message?
I need to rule out this discrepancy as the cause of my other problem.
nginx
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
Where did you get nginx 1.14.2? How did it get onto your system?
– Michael Hampton♦
May 7 at 17:35
I got nginx 1.14.2 by following these instructions: tecklyfe.com/…
– Bruce Van Horn
May 7 at 18:27
Those directions seem reasonable. But did you actually do the last one: restart nginx?
– Michael Hampton♦
May 7 at 18:28
At this point I've restarted it many times trying different combinations of configuration parameters in pursuit of fixing the 413 error. I should have mentioned that before I upgraded, nginx -v indicated I had 1.14.1. It should have never been 1.10.3.
– Bruce Van Horn
May 7 at 18:31
Have you tried to stop nginx and check that it really stopped?
– Alexey Ten
May 7 at 20:37
|
show 2 more comments
I'm running nginx 1.14.2 on ubuntu 16. I'm having trouble figuring out a 413 error (which I'll address separately), but I noticed that when I post a file to the nginx server, it reports, presumably, the error message and the version of nginx:
<html>
<head>
<title>413 Request Entity Too Large</title>
</head>
<body bgcolor="white">
<center>
<h1>413 Request Entity Too Large</h1>
</center>
<hr>
<center>nginx/1.10.3 (Ubuntu)</center>
</body>
The command nginx -v shows the version to be 1.14.2. I checked the startup files to see if maybe they were pointing to some other version, but they all point to /usr/sbin/nginx which is what is telling me the version is 1.14.2.
So why does it say 1.10.3 in the error message?
I need to rule out this discrepancy as the cause of my other problem.
nginx
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
I'm running nginx 1.14.2 on ubuntu 16. I'm having trouble figuring out a 413 error (which I'll address separately), but I noticed that when I post a file to the nginx server, it reports, presumably, the error message and the version of nginx:
<html>
<head>
<title>413 Request Entity Too Large</title>
</head>
<body bgcolor="white">
<center>
<h1>413 Request Entity Too Large</h1>
</center>
<hr>
<center>nginx/1.10.3 (Ubuntu)</center>
</body>
The command nginx -v shows the version to be 1.14.2. I checked the startup files to see if maybe they were pointing to some other version, but they all point to /usr/sbin/nginx which is what is telling me the version is 1.14.2.
So why does it say 1.10.3 in the error message?
I need to rule out this discrepancy as the cause of my other problem.
nginx
nginx
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
asked May 7 at 17:01
Bruce Van HornBruce Van Horn
62
62
Where did you get nginx 1.14.2? How did it get onto your system?
– Michael Hampton♦
May 7 at 17:35
I got nginx 1.14.2 by following these instructions: tecklyfe.com/…
– Bruce Van Horn
May 7 at 18:27
Those directions seem reasonable. But did you actually do the last one: restart nginx?
– Michael Hampton♦
May 7 at 18:28
At this point I've restarted it many times trying different combinations of configuration parameters in pursuit of fixing the 413 error. I should have mentioned that before I upgraded, nginx -v indicated I had 1.14.1. It should have never been 1.10.3.
– Bruce Van Horn
May 7 at 18:31
Have you tried to stop nginx and check that it really stopped?
– Alexey Ten
May 7 at 20:37
|
show 2 more comments
Where did you get nginx 1.14.2? How did it get onto your system?
– Michael Hampton♦
May 7 at 17:35
I got nginx 1.14.2 by following these instructions: tecklyfe.com/…
– Bruce Van Horn
May 7 at 18:27
Those directions seem reasonable. But did you actually do the last one: restart nginx?
– Michael Hampton♦
May 7 at 18:28
At this point I've restarted it many times trying different combinations of configuration parameters in pursuit of fixing the 413 error. I should have mentioned that before I upgraded, nginx -v indicated I had 1.14.1. It should have never been 1.10.3.
– Bruce Van Horn
May 7 at 18:31
Have you tried to stop nginx and check that it really stopped?
– Alexey Ten
May 7 at 20:37
Where did you get nginx 1.14.2? How did it get onto your system?
– Michael Hampton♦
May 7 at 17:35
Where did you get nginx 1.14.2? How did it get onto your system?
– Michael Hampton♦
May 7 at 17:35
I got nginx 1.14.2 by following these instructions: tecklyfe.com/…
– Bruce Van Horn
May 7 at 18:27
I got nginx 1.14.2 by following these instructions: tecklyfe.com/…
– Bruce Van Horn
May 7 at 18:27
Those directions seem reasonable. But did you actually do the last one: restart nginx?
– Michael Hampton♦
May 7 at 18:28
Those directions seem reasonable. But did you actually do the last one: restart nginx?
– Michael Hampton♦
May 7 at 18:28
At this point I've restarted it many times trying different combinations of configuration parameters in pursuit of fixing the 413 error. I should have mentioned that before I upgraded, nginx -v indicated I had 1.14.1. It should have never been 1.10.3.
– Bruce Van Horn
May 7 at 18:31
At this point I've restarted it many times trying different combinations of configuration parameters in pursuit of fixing the 413 error. I should have mentioned that before I upgraded, nginx -v indicated I had 1.14.1. It should have never been 1.10.3.
– Bruce Van Horn
May 7 at 18:31
Have you tried to stop nginx and check that it really stopped?
– Alexey Ten
May 7 at 20:37
Have you tried to stop nginx and check that it really stopped?
– Alexey Ten
May 7 at 20:37
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f966227%2fwhy-would-nginx-1-14-2-show-version-1-10-3-in-error-messages%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f966227%2fwhy-would-nginx-1-14-2-show-version-1-10-3-in-error-messages%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Where did you get nginx 1.14.2? How did it get onto your system?
– Michael Hampton♦
May 7 at 17:35
I got nginx 1.14.2 by following these instructions: tecklyfe.com/…
– Bruce Van Horn
May 7 at 18:27
Those directions seem reasonable. But did you actually do the last one: restart nginx?
– Michael Hampton♦
May 7 at 18:28
At this point I've restarted it many times trying different combinations of configuration parameters in pursuit of fixing the 413 error. I should have mentioned that before I upgraded, nginx -v indicated I had 1.14.1. It should have never been 1.10.3.
– Bruce Van Horn
May 7 at 18:31
Have you tried to stop nginx and check that it really stopped?
– Alexey Ten
May 7 at 20:37