Can't access my server from within the network after changing ISPs (new router)DNS: Domain name goes to...
Why do neural networks need so many training examples to perform?
How do I prevent a homebrew Grappling Hook feature from trivializing Tomb of Annihilation?
After checking in online, how do I know whether I need to go show my passport at airport check-in?
Can you tell from a blurry photo if focus was too close or too far?
Why don't key signatures indicate the tonic?
Best way to strengthen a wheel?
Coworker asking me to not bring cakes due to self control issue. What should I do?
microtype error with lualatex: "attempt to call field warning a nil value"
Early credit roll before the end of the film
What language shall they sing in?
How to deal with possible delayed baggage?
A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?
Removing whitespace between consecutive numbers
What is a good reason for every spaceship to carry a weapon on board?
Why zero tolerance on nudity in space?
How do you funnel food off a cutting board?
Why do we have to make "peinlich" start with a capital letter and also end with -s in this sentence?
Why do all the books in Game of Thrones library have their covers facing the back of the shelf?
Potential client has a problematic employee I can't work with
How would an AI self awareness kill switch work?
Changing the laptop's CPU. Should I reinstall Linux?
What game did these black and yellow dice come from?
Does a paladin have to announce that they're using Divine Smite before attacking?
How can I find y?
Can't access my server from within the network after changing ISPs (new router)
DNS: Domain name goes to router when on the network, not the web serverNew router directs inbound requests to own WAN address to the settings pagetechnicolor router can't access localhost from public ipCan't access SMCD3G router from Comcast after a password changeDomain name goes to router login on the same network and no response from outsideCan not access to public IP from inside networkCan't access Nasbox with domain name from within the local networkAccess web server behind router from outside and inside of the network with same addressAccess external network devices from router's internal networkNew Router: Unable to download images from Instagram and WhatsApp
I have a small Django website which is hosted on a raspberry pi on my network and has been running smoothly for a few years. I recently changed my ISP from Comcast to Century Link. After the change, I discovered that my old router couldn't support the new speeds. So I decided to use Century Link's modem/router as my router (Zyxel C3000Z). Since then, I haven't been able to connect to my site from within my network.
I have updated my domain to point to my new IP address and I have forwarded the correct ports on the router.
If I am outside of my network, I can confirm that my server is receiving requests when I hit my domain. So I know that my port forwarding is set up correctly. However, I am using SSL so when I hit my site from outside of the network, the login page loads, but then it hangs and is unable to connect when I submit the login request. I assume this is because its trying to redirect to itself after authenticating and can't connect to itself within the network. If I hit the domain inside of the network the browser says it can't connect.
I'm sure this is just a configuration in the router. This router has a lot more configuration options than my old one. Are there some common router settings that I should check that might cover a scenario like this?
Edit:
The Django error page when it eventually times out says ConnectionError at /
networking router dns wireless-router
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
|
show 2 more comments
I have a small Django website which is hosted on a raspberry pi on my network and has been running smoothly for a few years. I recently changed my ISP from Comcast to Century Link. After the change, I discovered that my old router couldn't support the new speeds. So I decided to use Century Link's modem/router as my router (Zyxel C3000Z). Since then, I haven't been able to connect to my site from within my network.
I have updated my domain to point to my new IP address and I have forwarded the correct ports on the router.
If I am outside of my network, I can confirm that my server is receiving requests when I hit my domain. So I know that my port forwarding is set up correctly. However, I am using SSL so when I hit my site from outside of the network, the login page loads, but then it hangs and is unable to connect when I submit the login request. I assume this is because its trying to redirect to itself after authenticating and can't connect to itself within the network. If I hit the domain inside of the network the browser says it can't connect.
I'm sure this is just a configuration in the router. This router has a lot more configuration options than my old one. Are there some common router settings that I should check that might cover a scenario like this?
Edit:
The Django error page when it eventually times out says ConnectionError at /
networking router dns wireless-router
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
Doesn't seem like a network or SSL problem; if you can load the login page then both must be working. Did you ever hard code something on your website? For example, did your internal IP addresses change and is the old IP address of your database punched into the web server? What do you mean by 'redirect to itself after authenticating'?
– Andy
Feb 13 at 20:15
There shouldn't be anything hard-coded. I've reviewed all of the apache settings and the Django app settings to make sure there weren't any references that might be causing this issue. I'm making an assumption that once I click 'Login', the server redirects to the homepage and that's the issue, but that may be a bad assumption.
– brewcrazy
Feb 13 at 20:20
The homepage is still the same website on the same webserver with the same SSL cert, right?
– Andy
Feb 13 at 20:25
Yes its all the same server. Again this was all working just fine with my old router. I don't understand how switching a router could cause any issue unless it is a router configuration issue.
– brewcrazy
Feb 13 at 20:25
I'm stumped. Sorry. I know nothing about django, but if you start hunting down that error, do you find something useful? Does this help? stackoverflow.com/questions/32516443 Cross post your question to django and maybe they can help more.
– Andy
Feb 13 at 20:26
|
show 2 more comments
I have a small Django website which is hosted on a raspberry pi on my network and has been running smoothly for a few years. I recently changed my ISP from Comcast to Century Link. After the change, I discovered that my old router couldn't support the new speeds. So I decided to use Century Link's modem/router as my router (Zyxel C3000Z). Since then, I haven't been able to connect to my site from within my network.
I have updated my domain to point to my new IP address and I have forwarded the correct ports on the router.
If I am outside of my network, I can confirm that my server is receiving requests when I hit my domain. So I know that my port forwarding is set up correctly. However, I am using SSL so when I hit my site from outside of the network, the login page loads, but then it hangs and is unable to connect when I submit the login request. I assume this is because its trying to redirect to itself after authenticating and can't connect to itself within the network. If I hit the domain inside of the network the browser says it can't connect.
I'm sure this is just a configuration in the router. This router has a lot more configuration options than my old one. Are there some common router settings that I should check that might cover a scenario like this?
Edit:
The Django error page when it eventually times out says ConnectionError at /
networking router dns wireless-router
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
I have a small Django website which is hosted on a raspberry pi on my network and has been running smoothly for a few years. I recently changed my ISP from Comcast to Century Link. After the change, I discovered that my old router couldn't support the new speeds. So I decided to use Century Link's modem/router as my router (Zyxel C3000Z). Since then, I haven't been able to connect to my site from within my network.
I have updated my domain to point to my new IP address and I have forwarded the correct ports on the router.
If I am outside of my network, I can confirm that my server is receiving requests when I hit my domain. So I know that my port forwarding is set up correctly. However, I am using SSL so when I hit my site from outside of the network, the login page loads, but then it hangs and is unable to connect when I submit the login request. I assume this is because its trying to redirect to itself after authenticating and can't connect to itself within the network. If I hit the domain inside of the network the browser says it can't connect.
I'm sure this is just a configuration in the router. This router has a lot more configuration options than my old one. Are there some common router settings that I should check that might cover a scenario like this?
Edit:
The Django error page when it eventually times out says ConnectionError at /
networking router dns wireless-router
networking router dns wireless-router
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
edited Feb 13 at 20:23
brewcrazy
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
asked Feb 13 at 17:07
brewcrazybrewcrazy
12
12
Doesn't seem like a network or SSL problem; if you can load the login page then both must be working. Did you ever hard code something on your website? For example, did your internal IP addresses change and is the old IP address of your database punched into the web server? What do you mean by 'redirect to itself after authenticating'?
– Andy
Feb 13 at 20:15
There shouldn't be anything hard-coded. I've reviewed all of the apache settings and the Django app settings to make sure there weren't any references that might be causing this issue. I'm making an assumption that once I click 'Login', the server redirects to the homepage and that's the issue, but that may be a bad assumption.
– brewcrazy
Feb 13 at 20:20
The homepage is still the same website on the same webserver with the same SSL cert, right?
– Andy
Feb 13 at 20:25
Yes its all the same server. Again this was all working just fine with my old router. I don't understand how switching a router could cause any issue unless it is a router configuration issue.
– brewcrazy
Feb 13 at 20:25
I'm stumped. Sorry. I know nothing about django, but if you start hunting down that error, do you find something useful? Does this help? stackoverflow.com/questions/32516443 Cross post your question to django and maybe they can help more.
– Andy
Feb 13 at 20:26
|
show 2 more comments
Doesn't seem like a network or SSL problem; if you can load the login page then both must be working. Did you ever hard code something on your website? For example, did your internal IP addresses change and is the old IP address of your database punched into the web server? What do you mean by 'redirect to itself after authenticating'?
– Andy
Feb 13 at 20:15
There shouldn't be anything hard-coded. I've reviewed all of the apache settings and the Django app settings to make sure there weren't any references that might be causing this issue. I'm making an assumption that once I click 'Login', the server redirects to the homepage and that's the issue, but that may be a bad assumption.
– brewcrazy
Feb 13 at 20:20
The homepage is still the same website on the same webserver with the same SSL cert, right?
– Andy
Feb 13 at 20:25
Yes its all the same server. Again this was all working just fine with my old router. I don't understand how switching a router could cause any issue unless it is a router configuration issue.
– brewcrazy
Feb 13 at 20:25
I'm stumped. Sorry. I know nothing about django, but if you start hunting down that error, do you find something useful? Does this help? stackoverflow.com/questions/32516443 Cross post your question to django and maybe they can help more.
– Andy
Feb 13 at 20:26
Doesn't seem like a network or SSL problem; if you can load the login page then both must be working. Did you ever hard code something on your website? For example, did your internal IP addresses change and is the old IP address of your database punched into the web server? What do you mean by 'redirect to itself after authenticating'?
– Andy
Feb 13 at 20:15
Doesn't seem like a network or SSL problem; if you can load the login page then both must be working. Did you ever hard code something on your website? For example, did your internal IP addresses change and is the old IP address of your database punched into the web server? What do you mean by 'redirect to itself after authenticating'?
– Andy
Feb 13 at 20:15
There shouldn't be anything hard-coded. I've reviewed all of the apache settings and the Django app settings to make sure there weren't any references that might be causing this issue. I'm making an assumption that once I click 'Login', the server redirects to the homepage and that's the issue, but that may be a bad assumption.
– brewcrazy
Feb 13 at 20:20
There shouldn't be anything hard-coded. I've reviewed all of the apache settings and the Django app settings to make sure there weren't any references that might be causing this issue. I'm making an assumption that once I click 'Login', the server redirects to the homepage and that's the issue, but that may be a bad assumption.
– brewcrazy
Feb 13 at 20:20
The homepage is still the same website on the same webserver with the same SSL cert, right?
– Andy
Feb 13 at 20:25
The homepage is still the same website on the same webserver with the same SSL cert, right?
– Andy
Feb 13 at 20:25
Yes its all the same server. Again this was all working just fine with my old router. I don't understand how switching a router could cause any issue unless it is a router configuration issue.
– brewcrazy
Feb 13 at 20:25
Yes its all the same server. Again this was all working just fine with my old router. I don't understand how switching a router could cause any issue unless it is a router configuration issue.
– brewcrazy
Feb 13 at 20:25
I'm stumped. Sorry. I know nothing about django, but if you start hunting down that error, do you find something useful? Does this help? stackoverflow.com/questions/32516443 Cross post your question to django and maybe they can help more.
– Andy
Feb 13 at 20:26
I'm stumped. Sorry. I know nothing about django, but if you start hunting down that error, do you find something useful? Does this help? stackoverflow.com/questions/32516443 Cross post your question to django and maybe they can help more.
– Andy
Feb 13 at 20:26
|
show 2 more comments
1 Answer
1
active
oldest
votes
After speaking with some people with experience with Centurylink in similar scenarios and doing a lot of research online, I've concluded that this is caused by a limitation of some kind in the C3000Z modem/router.
I've since purchased an ASUS RT-AC68U for my routing and set the C3000Z up in transparent bridge mode only. This immediately resolved all of my issues connecting to my sever from within the network.
I highly recommend the above router so far.
answered 9 mins ago
brewcrazybrewcrazy
12
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1405363%2fcant-access-my-server-from-within-the-network-after-changing-isps-new-router%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
After speaking with some people with experience with Centurylink in similar scenarios and doing a lot of research online, I've concluded that this is caused by a limitation of some kind in the C3000Z modem/router.
I've since purchased an ASUS RT-AC68U for my routing and set the C3000Z up in transparent bridge mode only. This immediately resolved all of my issues connecting to my sever from within the network.
I highly recommend the above router so far.
answered 9 mins ago
brewcrazybrewcrazy
12
add a comment |
After speaking with some people with experience with Centurylink in similar scenarios and doing a lot of research online, I've concluded that this is caused by a limitation of some kind in the C3000Z modem/router.
I've since purchased an ASUS RT-AC68U for my routing and set the C3000Z up in transparent bridge mode only. This immediately resolved all of my issues connecting to my sever from within the network.
I highly recommend the above router so far.
answered 9 mins ago
brewcrazybrewcrazy
12
add a comment |
After speaking with some people with experience with Centurylink in similar scenarios and doing a lot of research online, I've concluded that this is caused by a limitation of some kind in the C3000Z modem/router.
I've since purchased an ASUS RT-AC68U for my routing and set the C3000Z up in transparent bridge mode only. This immediately resolved all of my issues connecting to my sever from within the network.
I highly recommend the above router so far.
answered 9 mins ago
brewcrazybrewcrazy
12
After speaking with some people with experience with Centurylink in similar scenarios and doing a lot of research online, I've concluded that this is caused by a limitation of some kind in the C3000Z modem/router.
I've since purchased an ASUS RT-AC68U for my routing and set the C3000Z up in transparent bridge mode only. This immediately resolved all of my issues connecting to my sever from within the network.
I highly recommend the above router so far.
answered 9 mins ago
brewcrazybrewcrazy
12
answered 9 mins ago
brewcrazybrewcrazy
12
answered 9 mins ago
brewcrazybrewcrazy
12
answered 9 mins ago
brewcrazybrewcrazy
12
12
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1405363%2fcant-access-my-server-from-within-the-network-after-changing-isps-new-router%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
Doesn't seem like a network or SSL problem; if you can load the login page then both must be working. Did you ever hard code something on your website? For example, did your internal IP addresses change and is the old IP address of your database punched into the web server? What do you mean by 'redirect to itself after authenticating'?
– Andy
Feb 13 at 20:15
There shouldn't be anything hard-coded. I've reviewed all of the apache settings and the Django app settings to make sure there weren't any references that might be causing this issue. I'm making an assumption that once I click 'Login', the server redirects to the homepage and that's the issue, but that may be a bad assumption.
– brewcrazy
Feb 13 at 20:20
The homepage is still the same website on the same webserver with the same SSL cert, right?
– Andy
Feb 13 at 20:25
Yes its all the same server. Again this was all working just fine with my old router. I don't understand how switching a router could cause any issue unless it is a router configuration issue.
– brewcrazy
Feb 13 at 20:25
I'm stumped. Sorry. I know nothing about django, but if you start hunting down that error, do you find something useful? Does this help? stackoverflow.com/questions/32516443 Cross post your question to django and maybe they can help more.
– Andy
Feb 13 at 20:26