You are here
ChrisD - Tue, 2011/05/24 - 22:51
I set up a Turnkey Linux WordPress appliance as a sandbox for development. I'd like my clients to be able to see what I’m working on but unfortunately my ISP blocks port 80.
So I set port forwarding on my router to forward port 8081 (WAN) to port 80 (LAN). This works fine from outside for my main site using http://mywebaddress.com:8081
But I created a sub site at (LAN) http://192.168.1.100/newsite That works fine from inside but when I try to access from outside using http://mywebaddress.com:8081/newsite I get a timeout error.
Is this the right syntax?
Thanks in advance. - Chris
Forum:
Tags:
Hmm that sounds strange
The format you use should work and I don't really understand why http://mywebaddress.com:8081
works but http://mywebaddress.com:8081/newsite doesn't. Especially considering it seems to work inside your LAN but not from outside.
Not sure whether it will help in your scenario or not but some dynamic DNS providers (many listed and discussed in this thread) allow to redirect ports at the DNS level. So instead of requiring http://mywebaddress.com:8081 you can just use http://mywebaddress.com from outside and it will resolve to the desired port. As I say, I'm not sure whether that will solve your issue, but it may? Also another thing you could try is setting up the server to listen on 8081 (rather than 80) that way hopefully you will at least get consistent results from inside and outside your LAN.
Add new comment