Ubuntu server 18.04 .netcore nginx not able to resolve host
0
I have asp.net core 2.0 WebAPI and this is the setup details
Ubuntu server 18.04
nginx with
/etc/nginx/sites-available/default as:
server{
listen 80;
listen [::]:80;
root /var/repos/web-api/code/src/Api;
server_name my-web-api.com *.my-web-api.com;
location / {
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
}
but when I try
curl
curl https://my-web-api/ping [ping is one of end point]
it returns Could not resolve host: my-web-api
I followed this tutorial at MSDN link
networking server nginx
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
add a comment |
0
I have asp.net core 2.0 WebAPI and this is the setup details
Ubuntu server 18.04
nginx with
/etc/nginx/sites-available/default as:
server{
listen 80;
listen [::]:80;
root /var/repos/web-api/code/src/Api;
server_name my-web-api.com *.my-web-api.com;
location / {
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
}
but when I try
curl
curl https://my-web-api/ping [ping is one of end point]
it returns Could not resolve host: my-web-api
I followed this tutorial at MSDN link
networking server nginx
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
add a comment |
0
0
0
I have asp.net core 2.0 WebAPI and this is the setup details
Ubuntu server 18.04
nginx with
/etc/nginx/sites-available/default as:
server{
listen 80;
listen [::]:80;
root /var/repos/web-api/code/src/Api;
server_name my-web-api.com *.my-web-api.com;
location / {
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
}
but when I try
curl
curl https://my-web-api/ping [ping is one of end point]
it returns Could not resolve host: my-web-api
I followed this tutorial at MSDN link
networking server nginx
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
I have asp.net core 2.0 WebAPI and this is the setup details
Ubuntu server 18.04
nginx with
/etc/nginx/sites-available/default as:
server{
listen 80;
listen [::]:80;
root /var/repos/web-api/code/src/Api;
server_name my-web-api.com *.my-web-api.com;
location / {
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
}
but when I try
curl
curl https://my-web-api/ping [ping is one of end point]
it returns Could not resolve host: my-web-api
I followed this tutorial at MSDN link
networking server nginx
networking server nginx
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
asked Mar 15 at 10:40
Bhanu ChhabraBhanu Chhabra
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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
});
}
});
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f1125879%2fubuntu-server-18-04-netcore-nginx-not-able-to-resolve-host%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
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- 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.
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f1125879%2fubuntu-server-18-04-netcore-nginx-not-able-to-resolve-host%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
