Conflict with Etherpad (http) server

Bug #565958 reported by KIAaze
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
WebContentControl
New
Medium
Unassigned

Bug Description

Hi Zoidberg, i found a problem when running an Etherpad server (and probably other http servers as well). I can't connect to my own server using http://myfreednsaccount.no-ip.com/ (and neither can other internet users outside my lan), unless I shutdown Firehol. Although i can connect to http://127.0.0.1/ or http://localhost/. I tried adding "server http accept" in firehol.conf (in lan and internet interfaces), but it didn't work.

I also tried deleting this lines:
iptables -t filter -I OUTPUT -d 127.0.0.1 -p tcp --dport 3128 -m owner ! --uid-owner dansguardian -j DROP
transparent_squid 8080 "proxy root"
and I was able to connect to http://myfreednsaccount.no-ip.com/ with Firehol on, but as you probably guess that stopped dansguardian filter too!

Is there any way to use web content control and allow access to my web server at the same time?

This is my firehol.conf:
version 5
iptables -t filter -I OUTPUT -d 127.0.0.1 -p tcp --dport 3128 -m owner ! --uid-owner dansguardian -j DROP
transparent_squid 8080 "proxy root"

interface eth0 lan
 policy accept

interface pan0 internet
 policy drop
 protection strong
 server http accept
 client all accept

And here is some information about Etherpad server if you are interested:
http://pauleira.com/13/installing-etherpad/
http://lincolnloop.com/blog/2009/dec/18/running-your-own-self-hosted-etherpad-instance/
http://code.google.com/p/etherpad/wiki/Instructions
https://wiki.ubuntu.com/Etherpad

Thanks again for your time and hardwork!

KIAaze (zohn-joidberg)
Changed in webcontentcontrol:
importance: Undecided → Medium
KIAaze (zohn-joidberg)
Changed in webcontentcontrol:
milestone: none → foobar
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.