Maybe someone has an idea how to fix this:
>local homeserver with apache
>router forwards https port 443
>use internal domain in hosts file https://local.lo
>external domain https://external.com points to ip address
>apache is configured to treat it as an alias, both point to the same vhost
I can access external.com only from outside my LAN just fine but from home I get ERR_CONNECTION_TIMED_OUT
Worked like a charm before, until I had to replace a broken router. Now it doesn't anymore.
Is this some kind of loopback-blockage from my new router?
How do I go about fixing this?
>>61060397
>Worked like a charm before, until I had to replace a broken router.
are you sure it was broken?
>>61060397
Does the new router give the same internal IP address to the server?
Firewall on server?
>>61060486
it was dead, even with power connected. All LEDs were out, so I figured the power unit was broken.
>>61060522
I have a cable modem from my internet provider which I replaced. It's some proprietary shit with a toddler ui, so I put a fritzbox between my home-network and the cable modem. The fritzbox didn't change at all, so it must be the cable modem.
>>61060547
I deactivated the firewall and all security functionalities and forwarded all ports on the cablemodem, the fritzbox hasn't changed.
No other firewalls have been modified
>>61060565
> I have a cable modem from my internet provider which I replaced. It's some proprietary shit with a toddler ui, so I put a fritzbox between my home-network and the cable modem. The fritzbox didn't change at all, so it must be the cable modem.
You're saying that you replaced a device that doesn't manage the internal network and it broke your internal network
That's strange
>>61060597
Exactly. I hoped to find out if there is some security feature with a name I could look for in the settings. So far I disabled all I could find but didn't touch those I couldn't identify because I don't want to break anything.
>>61060630
Traceroute it. If it goes through the cable modem it's wrong
>>61060682traceroute to ***external.com*** (*.*.*.*), 30 hops max, 60 byte packets
1 gateway (192.168.0.1) 0.297 ms 0.391 ms 0.719 ms
2 ip-*-*-*-*.hsi04.unitymediagroup.de (*.*.*.*) 5.868 ms 5.969 ms 6.465 ms
3 ip-*-*-*-*.hsi04.unitymediagroup.de (*.*.*.*) 14.925 ms !X 15.145 ms !X 15.533 ms !X
does this help?
Changed my external ip to *.*.*.*
Also this is how the cable modem ui looks like
>>61060778
Wait I don't get it anymore, weren't you using local.lo as the local domain? You're saying the registered domain works from everywhere but your own network?
>>61060810
I am home atm.
When I open https://local.lo it works.
When I open https://external.com i get timeout. But I want it to work
When I am not at home:
I open https://local.lo and obviously it wont work
https://external.com works which is fine and proof that the configuration is correct at least in the webserver.
the https://external.com points to my external IP which I cannot access from home. That's the issue I'm talking about
Configure a forwarder for external sites. I would just install bind9 for internal dns and use it for the internal traffic and forward external queries to ex. 8.8.8.8 of i were in your spot
>>61060397
The things people do to avoid installing one extension to their browser.
>>61061899
yeah thats probably a decent way to solve it.
I am just mad that it worked before and since the router replacement it just stopped working and I hate branded router/modem devices with a passion.
The new router has DNS rebind protection.
>>61061899
This (split-horizon DNS) is the solution.