[5.800] Error with Surfprotection

Hello,
I has the following errors with the surfen with firefox
" Beim Versuch Seite XXX aufzurufen wurde die Verbindung zurück gesetzt"
and the following error with the Internet Explorer
"Die Seite kann nicht angezeigt werden."

the config is the same as with 5.202 and it works good as 5.202

I have teste with Transparent Proxy and Standart Proxy its the same
Franz

Parents

0 Markus Hennig over 20 years ago

Hi Franz

please send us more details about your config and the URL you tried to surf.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 extraem over 20 years ago in reply to Markus Hennig

Hi Markus,

I have  Operation Mode: Transparent
Anonymity:  none
Allowed Networks:  Internal(Network)
SurfProtection :  On
2 Pofiles:    Default and Kids   Default everything may
Kids only reduced  Assigned Network Blocks   every Host

Block CONNECT method on HTTP port: ON

The URL:  www.astaro.org   www.heise.de is all the same

Franz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Xeno over 20 years ago in reply to extraem

Please goto Webadmin -> Reporting -> Advanced -> Process List and search for "squidf" and "hyperdyper". If one is missing you have to restart it manually.

Also check Webadmin -> Packet Filter -> Advanced -> Current System Packet Filter Rules and Current System NAT Rules. There have to be some rules matching port 80 and port 8080. Just post the information.

Is there a firewall in front of ASL? Is ASL able to connect on port 80 and 6000?

Have you tried to disable and reenable the whole http proxy? Do that AFTER you copied the requested informations from the webadmin.

Xeno
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 extraem over 20 years ago in reply to Xeno

Hi

here the Process List

USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root         1  0.2  0.0   588   68 ?        S    19:16   0:06 init [3]
root         2  0.0  0.0     0    0 ?        SN   19:16   0:02 [ksoftirqd/0]
root         3  0.0  0.0     0    0 ?        S
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Xeno over 20 years ago in reply to extraem

Hmm, deamons are running and packetfilters are in place.

Please make the following tests:

- Execute 'dev-install.sh' to install telnet

1) Find out if Hyperdyper is working:

telnet localhost 3128
GET http://www.google.de/ HTTP/1.1
(press return 3 times)

2) Find out if Squid is working:

telnet localhost 16497
GET http://www.google.de/ HTTP/1.1
(press return 3 times)

Do you get some HTML output?

Xeno
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Xeno over 20 years ago in reply to extraem

Hmm, deamons are running and packetfilters are in place.

Please make the following tests:

- Execute 'dev-install.sh' to install telnet

1) Find out if Hyperdyper is working:

telnet localhost 3128
GET http://www.google.de/ HTTP/1.1
(press return 3 times)

2) Find out if Squid is working:

telnet localhost 16497
GET http://www.google.de/ HTTP/1.1
(press return 3 times)

Do you get some HTML output?

Xeno
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 extraem over 20 years ago in reply to Xeno
Hallo,

when i type

telnet localhost 3128
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused

after repeated test 3 or 4 times I get HTML expenditure

when i type
telnet localhost 16497

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET http://www.google.de/ HTTP/1.1

HTTP/1.0 407 Proxy Authentication Required
Server: squid/2.5.STABLE8
Mime-Version: 1.0
Date: Tue, 10 May 2005 19:23:46 GMT
Content-Type: text/html
Content-Length: 1355
Expires: Tue, 10 May 2005 19:23:46 GMT
X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
Proxy-Authenticate: Basic realm="Squid proxy-caching web server"
X-Cache: MISS from firewall.dom1.privat.maier-localnet.local
Proxy-Connection: close

ERROR: Cache Access Denied

ERROR

Cache Access Denied

While trying to retrieve the URL:
">http://www.google.de/

The following error was encountered:

Cache Access Denied.

Sorry, you are not currently allowed to request:

">http://www.google.de/
from this cache until you have authenticated yourself.

You need to use Netscape version 2.0 or greater, or Microsoft Internet
Explorer 3.0, or an HTTP/1.1 compliant browser for this to work.  Please
contact the cache administrator if you have
difficulties authenticating yourself or
change your default password.

Generated Tue, 10 May 2005 19:23:46 GMT by firewall.dom1.privat.maier-localnet.local (squid/2.5.STABLE8)

Connection closed by foreign host.
firewall:/root #

In process List   hyperdyper  is running all time

Franz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 extraem over 20 years ago in reply to extraem

Hallo,

I have determined that the hyperdyper daemon am always again started

is this the problem??

as one can repair it

Franz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Vukasin over 20 years ago in reply to extraem
try doing the following (as root):
Code:

touch /etc/no-selfmonitor/all
killall hyperdyper
chroot /var/chroot-http/ hyperdyper

and post what happens [;)]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 extraem over 20 years ago in reply to Vukasin

Hello,

this is a peace from the output

start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
querry failed: connect error:socket error:Connection refused
marking myself as invalid: 203.197.173.171:6000 for 300 sec
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
start configure
iterate servers
set io timeout
set retry timeout
set customer id
set enc key
discover servers
reload cat names
done loading cat names
Initialize IO (1024 select slots)...
Initialize Response Scanners...
Initialize Request Scanners...
Listening...
Accepting
firewall:/root #

after this is o.k.

Franz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Vukasin over 20 years ago in reply to extraem

and are there any entried in the selfmonitor log from the time when the proxy was restarting?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 extraem over 20 years ago in reply to Vukasin

Hi

this is the selfmonitor log

2005:05:11-19:10:54 (none) selfmonng[996]: child returned status: exit='0' signal='0'
2005:05:11-19:11:56 (none) selfmonng[996]: check Failed increment hyperdyper_working counter 1 - 1
2005:05:11-19:11:56 (none) selfmonng[996]: DEBUG: NOTIFYEVENT Name=hyperdyper_working Level=INFO Id=171 suppressed
2005:05:11-19:11:56 (none) selfmonng[996]: triggerAction: 'cmd'
2005:05:11-19:11:56 (none) selfmonng[996]: actionCmd(+): '/var/mdw/scripts/hyperdyper.sh restart'
2005:05:11-19:11:58 (none) selfmonng[996]: child returned status: exit='0' signal='0'
2005:05:11-19:13:00 (none) selfmonng[996]: check Failed increment hyperdyper_working counter 1 - 1
2005:05:11-19:13:00 (none) selfmonng[996]: DEBUG: NOTIFYEVENT Name=hyperdyper_working Level=INFO Id=171 suppressed
2005:05:11-19:13:00 (none) selfmonng[996]: triggerAction: 'cmd'
2005:05:11-19:13:00 (none) selfmonng[996]: actionCmd(+): '/var/mdw/scripts/hyperdyper.sh restart'
2005:05:11-19:13:03 (none) selfmonng[996]: child returned status: exit='0' signal='0'
2005:05:11-19:14:04 (none) selfmonng[996]: check Failed increment hyperdyper_working counter 1 - 1
2005:05:11-19:14:04 (none) selfmonng[996]: DEBUG: NOTIFYEVENT Name=hyperdyper_working Level=INFO Id=171 suppressed
2005:05:11-19:14:04 (none) selfmonng[996]: triggerAction: 'cmd'
2005:05:11-19:14:04 (none) selfmonng[996]: actionCmd(+): '/var/mdw/scripts/hyperdyper.sh restart'
2005:05:11-19:14:06 (none) selfmonng[996]: child returned status: exit='0' signal='0'
2005:05:11-19:15:07 (none) selfmonng[996]: check Failed increment hyperdyper_working counter 1 - 1
2005:05:11-19:15:07 (none) selfmonng[996]: DEBUG: NOTIFYEVENT Name=hyperdyper_working Level=INFO Id=171 suppressed
2005:05:11-19:15:07 (none) selfmonng[996]: triggerAction: 'cmd'
2005:05:11-19:15:07 (none) selfmonng[996]: actionCmd(+): '/var/mdw/scripts/hyperdyper.sh restart'
2005:05:11-19:15:11 (none) selfmonng[996]: child returned status: exit='0' signal='0'
2005:05:11-19:16:13 (none) selfmonng[996]: check Failed increment hyperdyper_working counter 1 - 1
2005:05:11-19:16:13 (none) selfmonng[996]: DEBUG: NOTIFYEVENT Name=hyperdyper_working Level=INFO Id=171 suppressed
2005:05:11-19:16:13 (none) selfmonng[996]: triggerAction: 'cmd'
2005:05:11-19:16:13 (none) selfmonng[996]: actionCmd(+): '/var/mdw/scripts/hyperdyper.sh restart'
2005:05:11-19:16:15 (none) selfmonng[996]: child returned status: exit='0' signal='0'

Franz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Vukasin over 20 years ago in reply to extraem

hmm... looks like the selfmonitor initiates a restart of the http proxy before he has a chance to start up. this will be fixed in the next version. until then, you can just keep the file (touch) /etc/no-selfmonitor/all to disable the selfmonitor.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

[5.800] Error with Surfprotection

ERROR

Cache Access Denied