apache

[ahri]

"connection refused"

[Calum]

while using mozilla 1.0 on macos9.1, it took about 20 seconds while 'connecting to...' then told me that 'the connection timed out while connecting to...'

[Master of Reality]

I have RedHat 7.3 on my server with squid and httpd already installed now. Squid is runing perfectly.

Apache still gives me the same error as above.
I did 'netstat -a | grep http' and it says:
tcp    0    0 *:http  *:* LISTEN
what does this mean? As you said above, this is what i should get... but it still doesnt work.

[ June 28, 2002: Message edited by: Master of Reality / Bob ]

[voidmain]

You can't even access it from one of your inside machines?  That is, http://192.168.0.1/ if that is the inside IP address of your server.  Is there any ipchians/iptables rules that would be restricting access to the http port (80)?

[Master of Reality]

I can get to it from my internal machines still.

[voidmain]

Ok, what is your external IP address?  Can you get to that from your inside machines?  If you can't, then you must have some firewall issues.

[the_black_angel]

Lookup has started ...


; <<>> DiG 8.3 <<>> @(null) chatroom.fuckmicrosoft.com
; Bad server: (null) -- using default server and timer opts
; (2 servers found)
;; res options: init recurs defnam dnsrch
;; got aswer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;;   chatroom.fuckmicrosoft.com, type = A, class = IN

;; ANSWER SECTION:
chatroom.fuckmicrosoft.com.  23h34m40s IN A  204.92.81.125

;; AUTHORITY SECTION:
fuckmicrosoft.com.   1d4h56m43s IN NS  NS1.I2NET.com.
fuckmicrosoft.com.   1d4h56m43s IN NS  NS2.I2NET.com.

;; ADDITIONAL SECTION:
NS1.I2NET.com.      1d4h56m43s IN A  208.179.142.2
NS2.I2NET.com.      1d4h56m43s IN A  208.179.142.3

;; Total query time: 181 msec
;; FROM: localhost to SERVER: default -- 139.134.5.51
;; WHEN: Sat Jun 29 10:18:26 2002
;; MSG SIZE  sent: 44  rcvd: 134

cannot connect to chatroom.fuckmicrosoft.com through http as you can see it is there, although Whois says that its not there

i can traceroute back to 204.92.81.125 and ping it properly so it is there and responding just not to http ?

is there a utility that can see what is listening at each port? there should be one somewhere though i don't know where?

hope this is helpful

[voidmain]

We already know that apache is listening on port 80.  What I asked him to do was to see if he could verify his outside address by doing an "ifconfig" and then seeing if he can get to that address from machine inside his house.  If he can, then his provider is blocking port 80 and there is nothing he can do about it other than call them and bitch.  But if his providers do not allow web servers then that is that, other than putting it on a port other than 80.  Like 8000 might be a good one.

[voidmain]

Or master could set me up with an account and let me ssh in and check it out...  I could tell pretty quickly where the problem is.

[Master of Reality]

it gives the same error in the error log when i tried running it on port 8000.
How do i setup an ssh account?

[KernelPanic]

Could it be a problem with your domain registrar??

[voidmain]

quote:Originally posted by Master of Reality / Bob:
it gives the same error in the error log when i tried running it on port 8000.
How do i setup an ssh account?

You've already got SSH up and running, you just need to create me a userid:

# adduser voidmain
# password voidmain

Then send me a PM with the password and I'll change it as soon as I log in.

[Master of Reality]

now someone can try to go to http://chatroom.fuckmicrosoft.com

[voidmain]

quote:Originally posted by Master of Reality / Bob:
now someone can try to go to http://chatroom.fuckmicrosoft.com

Nope, not yet...

[Master of Reality]

try http://chatroom.fuckmicrosoft.com:8000

[ June 29, 2002: Message edited by: Master of Reality / Bob ]