Unirest connection timeout
I'm encountering a network problem and I'm running out of ideas to check. I have this unirest request that I'm trying to send but I keep receiving this reply:
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.13.4</center>
</body>
</html>
Along with the error message connection time out. This error also happens when I try to run other non-unirest requests so I figured that this is a network issue.
Here is what I have done so far:
1. Requested that the IP of the client's web service be added to our network's whitelist
2. Requested that my IP be whitelisted to our UAT server's network, just in case my local computer tries to communicate with it
3. Check on our client side if they do any whitelisting in which they said that they don't
4. Tried to run my code from my home computer wherein my code worked perfectly
Any suggestion(s) is very much welcome and appreciated
EDIT:
Here is my configuration for nginx:
server {
listen 443;
server_name api.nuvelco.com;
location /{
proxy_pass http://api.nuvelco.com/;
}
}
nginx networking unirest
asked Nov 23 '18 at 9:06
Uzi
8713
add a comment |
I'm encountering a network problem and I'm running out of ideas to check. I have this unirest request that I'm trying to send but I keep receiving this reply:
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.13.4</center>
</body>
</html>
Along with the error message connection time out. This error also happens when I try to run other non-unirest requests so I figured that this is a network issue.
Here is what I have done so far:
1. Requested that the IP of the client's web service be added to our network's whitelist
2. Requested that my IP be whitelisted to our UAT server's network, just in case my local computer tries to communicate with it
3. Check on our client side if they do any whitelisting in which they said that they don't
4. Tried to run my code from my home computer wherein my code worked perfectly
Any suggestion(s) is very much welcome and appreciated
EDIT:
Here is my configuration for nginx:
server {
listen 443;
server_name api.nuvelco.com;
location /{
proxy_pass http://api.nuvelco.com/;
}
}
nginx networking unirest
asked Nov 23 '18 at 9:06
Uzi
8713
add a comment |
I'm encountering a network problem and I'm running out of ideas to check. I have this unirest request that I'm trying to send but I keep receiving this reply:
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.13.4</center>
</body>
</html>
Along with the error message connection time out. This error also happens when I try to run other non-unirest requests so I figured that this is a network issue.
Here is what I have done so far:
1. Requested that the IP of the client's web service be added to our network's whitelist
2. Requested that my IP be whitelisted to our UAT server's network, just in case my local computer tries to communicate with it
3. Check on our client side if they do any whitelisting in which they said that they don't
4. Tried to run my code from my home computer wherein my code worked perfectly
Any suggestion(s) is very much welcome and appreciated
EDIT:
Here is my configuration for nginx:
server {
listen 443;
server_name api.nuvelco.com;
location /{
proxy_pass http://api.nuvelco.com/;
}
}
nginx networking unirest
asked Nov 23 '18 at 9:06
Uzi
8713
I'm encountering a network problem and I'm running out of ideas to check. I have this unirest request that I'm trying to send but I keep receiving this reply:
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.13.4</center>
</body>
</html>
Along with the error message connection time out. This error also happens when I try to run other non-unirest requests so I figured that this is a network issue.
Here is what I have done so far:
1. Requested that the IP of the client's web service be added to our network's whitelist
2. Requested that my IP be whitelisted to our UAT server's network, just in case my local computer tries to communicate with it
3. Check on our client side if they do any whitelisting in which they said that they don't
4. Tried to run my code from my home computer wherein my code worked perfectly
Any suggestion(s) is very much welcome and appreciated
EDIT:
Here is my configuration for nginx:
server {
listen 443;
server_name api.nuvelco.com;
location /{
proxy_pass http://api.nuvelco.com/;
}
}
nginx networking unirest
nginx networking unirest
asked Nov 23 '18 at 9:06
Uzi
8713
asked Nov 23 '18 at 9:06
Uzi
8713
edited Nov 26 '18 at 3:48
asked Nov 23 '18 at 9:06
Uzi
8713
asked Nov 23 '18 at 9:06
Uzi
8713
asked Nov 23 '18 at 9:06
Uzi
8713
8713
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Probably nginx has several 'server' configurations, which can differ by IP/hostname/port. And you connect to that differently when it works and when it does not?
In most cases 404 means that there is no resource, or PHP is not configured to handle the url.
Checking out nginx access/error logs can be helpful.
answered Nov 23 '18 at 9:26
Andrey
1164
I'll try this out. Thanks
– Uzi
Nov 23 '18 at 9:44
Problem was found in the nginx.conf file. Thanks for the help.
– Uzi
Nov 28 '18 at 6:46
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53443539%2funirest-connection-timeout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Probably nginx has several 'server' configurations, which can differ by IP/hostname/port. And you connect to that differently when it works and when it does not?
In most cases 404 means that there is no resource, or PHP is not configured to handle the url.
Checking out nginx access/error logs can be helpful.
answered Nov 23 '18 at 9:26
Andrey
1164
I'll try this out. Thanks
– Uzi
Nov 23 '18 at 9:44
Problem was found in the nginx.conf file. Thanks for the help.
– Uzi
Nov 28 '18 at 6:46
add a comment |
Probably nginx has several 'server' configurations, which can differ by IP/hostname/port. And you connect to that differently when it works and when it does not?
In most cases 404 means that there is no resource, or PHP is not configured to handle the url.
Checking out nginx access/error logs can be helpful.
answered Nov 23 '18 at 9:26
Andrey
1164
I'll try this out. Thanks
– Uzi
Nov 23 '18 at 9:44
Problem was found in the nginx.conf file. Thanks for the help.
– Uzi
Nov 28 '18 at 6:46
add a comment |
Probably nginx has several 'server' configurations, which can differ by IP/hostname/port. And you connect to that differently when it works and when it does not?
In most cases 404 means that there is no resource, or PHP is not configured to handle the url.
Checking out nginx access/error logs can be helpful.
answered Nov 23 '18 at 9:26
Andrey
1164
Probably nginx has several 'server' configurations, which can differ by IP/hostname/port. And you connect to that differently when it works and when it does not?
In most cases 404 means that there is no resource, or PHP is not configured to handle the url.
Checking out nginx access/error logs can be helpful.
answered Nov 23 '18 at 9:26
Andrey
1164
answered Nov 23 '18 at 9:26
Andrey
1164
answered Nov 23 '18 at 9:26
Andrey
1164
answered Nov 23 '18 at 9:26
Andrey
1164
1164
I'll try this out. Thanks
– Uzi
Nov 23 '18 at 9:44
Problem was found in the nginx.conf file. Thanks for the help.
– Uzi
Nov 28 '18 at 6:46
add a comment |
I'll try this out. Thanks
– Uzi
Nov 23 '18 at 9:44
Problem was found in the nginx.conf file. Thanks for the help.
– Uzi
Nov 28 '18 at 6:46
I'll try this out. Thanks
– Uzi
Nov 23 '18 at 9:44
I'll try this out. Thanks
– Uzi
Nov 23 '18 at 9:44
Problem was found in the nginx.conf file. Thanks for the help.
– Uzi
Nov 28 '18 at 6:46
Problem was found in the nginx.conf file. Thanks for the help.
– Uzi
Nov 28 '18 at 6:46
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fstackoverflow.com%2fquestions%2f53443539%2funirest-connection-timeout%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
