Just a few weeks ago before the port forwarding page was moved from the blucurve admin page to the shaw webpage (Why?) ports 80 and 443 worked just fine, however the switch seemed to have kept port 80 intact but not 443.
I tried to remove and add 443 again to no avail. Is anyone else experiencing this? Whenever I ask shaw technical support they only tell me that they do not know anything about port forwarding and only can show us how to find the port forwarding page.
I'm really starting to regret signing on for a plan at this point, can I fix this by setting the modem to bridge and portforward via a thirdparty modem? Or is there a way to fix this? My domain is a .dev domain and by default does not work via http, I need port 443 open.
Has shaw decided that they can not trust us users with port forwarding anymore?
> can I fix this by setting the modem to bridge ...
This should work, because in "bridge" mode, all TCP/IP traffic goes "over" the bridge, directly to your web-server, i.e., no port-filtering by your modem.
What firewall software are you using on your web-server? Windows Firewall? Something with some variant of Linux? Could that firewall be "blocking" 443/TCP ?
> and port-forward via a third-party modem?
If the "uplink" port on your router is connected via Ethernet to the Shaw device, then you should be able to configure port-forwarding within your router. Again, check the firewall software on your web-server, to ensure that it allows 443/TCP to your web-server program.
> What firewall software are you using on your web-server? Windows Firewall? Something with some variant of Linux? Could that firewall be "blocking" 443/TCP ?
Iptables, it is configured properly yes. This all worked fine BEFORE shaw made this ridiculous change with where port forwarding functionality is found.
Does anyone know why the new port forwarding solution doesn't work? It's annoying that I'll need to buy a third party router just to get around this.