Beantwoord

External webserver acces

  • 10 november 2018
  • 4 reacties
  • 506 Bekeken

Hi!
I have exactly the same issue with the HG659: I have a secure webserver https and I would like to access it from the WiFi, but I receive the Certificate Error (from mediarouter.home).
If I access it from the external network (4G), I don't have any problem.
How did you solve it?
Thanks
icon

Beste antwoord door Brian 12 november 2018, 16:26

Hi gabriele, I made a new topic for your question like agentx suggested 🙂
As for an answer to your question, sometimes issues arise because the Huawei modem does not support NAT loopback. We've contacted our supplier but we're currently not able to support/activate this feature. You can find more information here and herefor possible workarounds. My apologies for the inconvenience!
Bekijk origineel

4 reacties

Reputatie 2
Hi!
I have exactly the same issue with the HG659: I have a secure webserver https and I would like to access it from the WiFi, but I receive the Certificate Error (from mediarouter.home).
If I access it from the external network (4G), I don't have any problem.
How did you solve it?
Thanks


I suggest you open a new topic for your issue as this topic has already been marked as resolved and of course your situation is likely to differ 🙂
Reputatie 7
Badge +7
Hi gabriele, I made a new topic for your question like agentx suggested 🙂
As for an answer to your question, sometimes issues arise because the Huawei modem does not support NAT loopback. We've contacted our supplier but we're currently not able to support/activate this feature. You can find more information here and herefor possible workarounds. My apologies for the inconvenience!
I understand, thanks for managing my post and the answer.

Unfortunately the workaround does not work for me, since the https certificate is linked to my domain name and not my IP, so I still get an error if I use the network address of the webserver.

Can someone suggest another workaround? I have a raspberry pi which should give me some flexibility...
Sorry, my mistake! The DNS solution worked: I set PiHole in the Raspberry and I forced the name to be redirected to the webserver! Perfect, thanks!

Reageer