[prev in list] [next in list] [prev in thread] [next in thread] 

List:       privoxy-users
Subject:    [privoxy-users] [ ijbswa-Support Requests-3511973 ] error 500 with normal forward
From:       SourceForge.net <noreply () sourceforge ! net>
Date:       2012-03-29 21:49:36
Message-ID: E1SDNDu-0003zf-85 () sfs-ml-4 ! v29 ! ch3 ! sourceforge ! com
[Download RAW message or body]

Support Requests item #3511973, was opened at 2012-03-27 08:47
Message generated for change (Comment added) made by fabiankeil
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=211118&aid=3511973&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: other
Group: None
> Status: Pending
Priority: 5
Private: No
Submitted By: borgcube (teh-borgcube)
Assigned to: Fabian Keil (fabiankeil)
Summary: error 500 with normal forward

Initial Comment:
Hello.

I filed this bug in Action Scripts before, though i guess it rather belongs here, \
since it's 2 errors occuring sequentially.

I'm attempting to configure Privoxy in a way that it transparently redirects all \
                Browser Traffic to
- .onion sites: the TOR network (localhost:9050, SOCKS proxy)
- .i2p sites: the I2P network (localhost:4444, HTTP proxy)
- the rest: just normally forwarding.

Platform is Gentoo x86_64. The used version is Privoxy-3.0.19.

I created this configuration:

user-manual /usr/share/doc/privoxy-3.0.19/user-manual/
confdir /etc/privoxy
logdir /var/log/privoxy
actionsfile match-all.action
actionsfile default.action
actionsfile user.action
filterfile default.filter
filterfile user.filter
logfile privoxy.log
listen-address 127.0.0.1:8118
toggle 1
enable-remote-toggle 0
enable-remote-http-toggle 0
enable-edit-actions 1
enforce-blocks 0
buffer-limit 4096
forward / .
forward-socks5 .onion/ 127.0.0.1:9050 .
forward .i2p/ 127.0.0.1:4444
forwarded-connect-retries 0
accept-intercepted-requests 1
allow-cgi-request-crunching 0
split-large-forms 0
keep-alive-timeout 5
socket-timeout 300
debug 1
debug 2
debug 4
debug 128
debug 512
debug 1024
debug 8192


Browser request are intercepted successfully by my firewall (linux) and redirected to \
Privoxy. TOR traffic works. I2P traffic works. But normal traffic isn't forwarded, i \
receive an Error 500: Internal error. 500 Internal Privoxy Error

Privoxy encountered an error while processing your request:

Could not load template file no-such-domain or one of its included components.

These are the files associated with privoxy by my package manager (portage). I \
                verified that the no-such-domain file is readable by any user.
/etc/init.d/privoxy
/etc/logrotate.d/privoxy
/etc/privoxy/config
/etc/privoxy/default.action
/etc/privoxy/default.filter
/etc/privoxy/match-all.action
/etc/privoxy/templates
/etc/privoxy/templates/blocked
/etc/privoxy/templates/cgi-error-404
/etc/privoxy/templates/cgi-error-bad-param
/etc/privoxy/templates/cgi-error-disabled
/etc/privoxy/templates/cgi-error-file
/etc/privoxy/templates/cgi-error-file-read-only
/etc/privoxy/templates/cgi-error-modified
/etc/privoxy/templates/cgi-error-parse
/etc/privoxy/templates/cgi-style.css
/etc/privoxy/templates/connect-failed
/etc/privoxy/templates/connection-timeout
/etc/privoxy/templates/default
/etc/privoxy/templates/edit-actions-add-url-form
/etc/privoxy/templates/edit-actions-for-url
/etc/privoxy/templates/edit-actions-for-url-filter
/etc/privoxy/templates/edit-actions-list
/etc/privoxy/templates/edit-actions-list-button
/etc/privoxy/templates/edit-actions-list-section
/etc/privoxy/templates/edit-actions-list-url
/etc/privoxy/templates/edit-actions-remove-url-form
/etc/privoxy/templates/edit-actions-url-form
/etc/privoxy/templates/forwarding-failed
/etc/privoxy/templates/mod-local-help
/etc/privoxy/templates/mod-support-and-service
/etc/privoxy/templates/mod-title
/etc/privoxy/templates/mod-unstable-warning
/etc/privoxy/templates/no-server-data
/etc/privoxy/templates/no-such-domain
/etc/privoxy/templates/show-request
/etc/privoxy/templates/show-status
/etc/privoxy/templates/show-status-file
/etc/privoxy/templates/show-url-info
/etc/privoxy/templates/show-version
/etc/privoxy/templates/toggle
/etc/privoxy/templates/toggle-mini
/etc/privoxy/templates/untrusted
/etc/privoxy/templates/url-info-osd.xml
/etc/privoxy/trust
/etc/privoxy/user.action
/etc/privoxy/user.filter
/usr/sbin/privoxy
/usr/share/doc/privoxy-3.0.19
/usr/share/doc/privoxy-3.0.19/AUTHORS.bz2
/usr/share/doc/privoxy-3.0.19/ChangeLog.bz2
/usr/share/doc/privoxy-3.0.19/README.bz2
/usr/share/doc/privoxy-3.0.19/TODO.bz2
/usr/share/doc/privoxy-3.0.19/developer-manual
/usr/share/doc/privoxy-3.0.19/developer-manual/coding.html
/usr/share/doc/privoxy-3.0.19/developer-manual/contact.html
/usr/share/doc/privoxy-3.0.19/developer-manual/copyright.html
/usr/share/doc/privoxy-3.0.19/developer-manual/cvs.html
/usr/share/doc/privoxy-3.0.19/developer-manual/documentation.html
/usr/share/doc/privoxy-3.0.19/developer-manual/index.html
/usr/share/doc/privoxy-3.0.19/developer-manual/introduction.html
/usr/share/doc/privoxy-3.0.19/developer-manual/newrelease.html
/usr/share/doc/privoxy-3.0.19/developer-manual/seealso.html
/usr/share/doc/privoxy-3.0.19/developer-manual/testing.html
/usr/share/doc/privoxy-3.0.19/developer-manual/webserver-update.html
/usr/share/doc/privoxy-3.0.19/faq
/usr/share/doc/privoxy-3.0.19/faq/configuration.html
/usr/share/doc/privoxy-3.0.19/faq/contact.html
/usr/share/doc/privoxy-3.0.19/faq/copyright.html
/usr/share/doc/privoxy-3.0.19/faq/general.html
/usr/share/doc/privoxy-3.0.19/faq/index.html
/usr/share/doc/privoxy-3.0.19/faq/installation.html
/usr/share/doc/privoxy-3.0.19/faq/misc.html
/usr/share/doc/privoxy-3.0.19/faq/trouble.html
/usr/share/doc/privoxy-3.0.19/images
/usr/share/doc/privoxy-3.0.19/index.html
/usr/share/doc/privoxy-3.0.19/man-page
/usr/share/doc/privoxy-3.0.19/man-page/privoxy-man-page.html
/usr/share/doc/privoxy-3.0.19/p_doc.css
/usr/share/doc/privoxy-3.0.19/user-manual
/usr/share/doc/privoxy-3.0.19/user-manual/actions-file.html
/usr/share/doc/privoxy-3.0.19/user-manual/appendix.html
/usr/share/doc/privoxy-3.0.19/user-manual/config.html
/usr/share/doc/privoxy-3.0.19/user-manual/configuration.html
/usr/share/doc/privoxy-3.0.19/user-manual/contact.html
/usr/share/doc/privoxy-3.0.19/user-manual/copyright.html
/usr/share/doc/privoxy-3.0.19/user-manual/files-in-use.jpg
/usr/share/doc/privoxy-3.0.19/user-manual/filter-file.html
/usr/share/doc/privoxy-3.0.19/user-manual/index.html
/usr/share/doc/privoxy-3.0.19/user-manual/installation.html
/usr/share/doc/privoxy-3.0.19/user-manual/introduction.html
/usr/share/doc/privoxy-3.0.19/user-manual/p_doc.css
/usr/share/doc/privoxy-3.0.19/user-manual/proxy2.jpg
/usr/share/doc/privoxy-3.0.19/user-manual/proxy_setup.jpg
/usr/share/doc/privoxy-3.0.19/user-manual/quickstart.html
/usr/share/doc/privoxy-3.0.19/user-manual/seealso.html
/usr/share/doc/privoxy-3.0.19/user-manual/startup.html
/usr/share/doc/privoxy-3.0.19/user-manual/templates.html
/usr/share/doc/privoxy-3.0.19/user-manual/whatsnew.html
/usr/share/man/man1/privoxy.1.bz2
/var/log/privoxy/.keep_net-proxy_privoxy-0

Suggestions?

----------------------------------------------------------------------

> Comment By: Fabian Keil (fabiankeil)
Date: 2012-03-29 14:49

Message:
The problem seems to be that Privoxy is talking to itself until it runs
into the file descriptor limit enforced by the operating system at which
point various libc functions no longer work. DNS resolution temporarily
stops working and the template files can't be opened.

As you aren't using all the debug directives recommend at:
http://www.privoxy.org/user-manual/contact.html#CONTACT-BUGS
the cause isn't obvious from the log, but the most likely explanation is
that the packet filter used to intercept request from other programs has no
exception for Privoxy's own requests.

This has to be configured in the packet filter as Privoxy can't evade the
packet filter on its own.

If the intercepting happens on the system running Privoxy you should be
able to make an exception for the privoxy user.

Additionally you might want to limit the number of client connections to
detect and stop such loops before file descriptor limit is reached:
http://www.privoxy.org/user-manual/config.html#MAX-CLIENT-CONNECTIONS

Note that it's also recommended to configure Privoxy to prevent a hostile
user from intentionally letting Privoxy connect to itself:
http://www.privoxy.org/user-manual/config.html#ACCEPT-INTERCEPTED-REQUESTS

This can be done by redirecting requests to Privoxy's port or forwarding
them to closed port on the same machine.

----------------------------------------------------------------------

Comment By: borgcube (teh-borgcube)
Date: 2012-03-28 07:13

Message:
Taking a closer look, it really seems like the requests are being fed back
into privoxy.
Bummer.

Any suggestions on how to enable privoxy to evade this?

PS: logfile attached. I had to zip it - 1 request amounted to 1.2mB of log.

----------------------------------------------------------------------

Comment By: borgcube (teh-borgcube)
Date: 2012-03-28 06:58

Message:
the re-fed traffic might be a good explanation of what i'm seeing.

I'll attach a log.

----------------------------------------------------------------------

Comment By: Fabian Keil (fabiankeil)
Date: 2012-03-27 10:08

Message:
What does a failing request look like in the logfile?

Did you make sure that traffic from Privoxy isn't redirected into Privoxy
again?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=211118&aid=3511973&group_id=11118

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ijbswa-users mailing list
Ijbswa-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ijbswa-users


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic