Stack Exchange
sign up
|
log in
|
careers 2.0
|
Server Fault
Questions
Tags
Tour
Users
Ask Question
inman320
less info
network profile
6
reputation
2
bio
website
location
age
visits
member for
1 year, 2 months
seen
Mar 18 '12 at 1:24
stats
profile views
1
6
reputation
bio
website
visits
member for
1 year, 2 months
2
badges
location
seen
Mar 18 '12 at 1:24
summary
answers
questions
tags
badges
favorites
bounties
reputation
activity
6
Actions
suggestions
reviews
revisions
comments
badges
posts
accepts
all
Mar
18
awarded
Student
Mar
17
awarded
Editor
Mar
17
revised
proxypass apache over nonstandard port - how can it be that the 192.168.*:9999 works from the computer itself but not another computer on the network?
deleted 156 characters in body
Mar
17
comment
proxypass apache over nonstandard port - how can it be that the 192.168.*:9999 works from the computer itself but not another computer on the network?
sorry my original post was too long - the main thing is that the site already loads correctly using the lan ip 192.168.1.5:9999 from a web browser on the server itself, but it doesn't load from other computers on the same network.
Mar
17
comment
proxypass apache over nonstandard port - how can it be that the 192.168.*:9999 works from the computer itself but not another computer on the network?
hi, not sure what that's supposed to do since it seems like it wouldn't be serving the localhost app at all with those settings, but in any case, with the single change you made to ProxyPass, httpd won't even restart.
Mar
17
asked
proxypass apache over nonstandard port - how can it be that the 192.168.*:9999 works from the computer itself but not another computer on the network?
Server Fault works best with JavaScript enabled