HTTP forwarding on a non-80 port

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

HTTP forwarding on a non-80 port

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
HTTP forwarding on a non-80 port
HTTP forwarding on a non-80 port
2015-12-20 02:39:24
Model : TL-WR841N

Hardware Version : WR841N v8 00000000

Firmware Version : 3.13.27 Build 121101 Rel.38183n


Hi, folks. Thanks for reading.

My current project involves a Raspberry Pi connected to my home network. It will eventually be serving a simple Wordepress homepage, but at the moment it is just set up with the default Apache homepage.

I'm using freedns.afraid.org and have set up my TL-WR841N to forward the port I want to use, and have tested it using my mobile phone browser. Unfortunately, it doesn't work when I put http://[webpage]:[portnumber] into the address bar.

As a test, I (also) forwarded port 80 to the internal IP of the RasPi and accessing the site without any port number served up the homepage on my mobile.

Would I be correct in thinking that this means the dynamic dns site does not support port numbers, or could there be another explanation?

(I'm fairly new to hosting a web server, in case it's not obvious.)

Thanks for any and all idea.
  0      
  0      
#1
Options

Information

Helpful: 0

Views: 623

Replies: 0

Related Articles