I'm unable to get Port Forwarding working on my new HomeHub. I believe I've set it up correctly as using https://portchecker.co/check shows that the ports I need to be open are open.
I'd found this post and followed the advice in it, but still seeing the same issues.
This is most likely because you are trying to test it from a device connected locally to your hub, routing out over the internet & back into your router to the forwarded device. This will never work because this traffic, termed loopback traffic, is considered a security risk by all TalkTalk routers and so they block it.
You need to test from say a smart phone having disconnected from Wi-Fi & use mobile data. Alternatively, test from a different broadband connection.
Thanks @KeithFrench. I've tried the connection now from my mobile on 4G, however I still can't connect to the server on my network. Is there anything else I can try?
Send me a screenshot of the port forwarding configuration. It may be a while before I can respond due to being very busy currently.
There is definitely nothing wrong with that config at all. Exactly what part of this server are you trying to access & with what type of software? What are you using TCP port 8123 for?
I'm trying to access a local server that runs a webUI on HTTPS. The actual server software port is 8123 on my local network, but the proxy redirects WAN traffic on HTTPS to the local server port of 8123.
I think the issue might be that because the TalkTalk router can't do a loopback then the proxy is unable to resolve the hostname and direct the traffic accordingly? The proxy software on the server manages renewals of HTTPS certificates via LetsEncrypt. And it seems like it's unable to renew them. Presumably because of this lack of lookback / resolving the DYDNS.
What DDNS provider are you using?
DuckDNS. Again this is all being handled by the proxy server rather than the DDNS service on the router.
I too use DuckDNS, but via the router utilising the very good dns-o-matic DNS proxy. The router fully supports integration with dns-o-matic. I can provide full config details if required, perhaps you could try that?
See the attached PDF.
Does this method also do HTTPS renewals via LetsEncrypt? Or is it just DDNS renewal?
Sorry can't comment on that as I do not use LetsEncrypt. It works perfectly as a DDNS proxy.