Hi, For a webserver like apache, explicitly stating the desired listening port number and internal IP (optional) in the respective VirtualHost configuration file, it would then be conceivable to achieve port forwarding from say, the default http port 80 to ANY other desired destination port provided the said destination port is not in use by another process. If you have already successfully achieved forwarding from port 80 to 8080, then it seems to me it might be a configuration problem at the web-server and not at the router. On 8/24/15, Maisiba Bravo via skunkworks <skunkworks@lists.my.co.ke> wrote:
Thanks ok3ch, Yes 443 can work but I need an http option and not htpps
On Mon, Aug 24, 2015 at 10:29 AM, Okechukwu <okechukwu@gmail.com> wrote:
HTTPS port 443
./Ok3ch
On Mon, Aug 24, 2015 at 8:05 AM, Maisiba Bravo via skunkworks < skunkworks@lists.my.co.ke> wrote:
Hi Skunks,
I am doing port forwarding for HTTP servers on my router. I have managed to port forward http servers on port 80 and 8080 only. Are there any other workable http ports? tried port 8000, 2020, 4040, all in vain.
Maisiba
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Kind Regards, Njung'e N. Lloyd Cell: +254 723 739 733