Privoxy fails to start due to duplicate listen address in config file #2692

Mossop · 2023-08-30T10:30:36Z

Is there a pinned issue for this?

I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

I have searched the existing issues
I have searched the existing discussions

Is there any comment in the documentation for this?

I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

I have checked the provider repo for issues
My issue is NOT related to a provider

Are you using the latest release?

I am using the latest release

Have you tried using the dev branch latest?

I have tried using dev branch

Docker run config used

docker-compose.yml:

  transmission:
    container_name: transmission
    image: haugene/transmission-openvpn:edge
    restart: always

    dns:
      - 1.1.1.1
      - 1.0.0.1

    networks:
      - services

    cap_add:
      - NET_ADMIN

    devices:
      - /dev/net/tun

    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/lib/transmission/:/config/transmission-home
      - /pool/media/:/pool/media

    environment:
      OPENVPN_PROVIDER: "PIA"
      OPENVPN_CONFIG: "uk_london"
      PIA_OPENVPN_CONFIG_BUNDLE: "openvpn-tcp"
      OPENVPN_USERNAME: "****"
      OPENVPN_PASSWORD: "****"
      ENABLE_UFW: "true"
      LOCAL_NETWORK: "10.10.0.0/16,172.16.0.0/12"
      PUID: "137"
      PGID: "151"
      TRANSMISSION_DOWNLOAD_DIR: "/pool/media/torrents/completed"
      TRANSMISSION_INCOMPLETE_DIR: "/pool/media/torrents/incomplete"
      TRANSMISSION_WATCH_DIR: "/pool/media/torrents/watch"
      TRANSMISSION_WEB_UI: flood-for-transmission
      WEBPROXY_ENABLED: "true"
      WEBPROXY_PORT: "8888"

Current Behavior

Privoxy fails to start, logs the following error:

2023-08-30 11:15:52.884 7f5f921d0b80 Fatal error: can't bind to 10.10.12.131:8888: There may be another Privoxy or some other proxy running on port 8888

Expected Behavior

Privoxy should start as normal.

How have you tried to solve the problem?

Tried the edge tag. Looked at the privoxy config file and spotted the issue, see discussion below.

Log output

2023-08-30 11:15:52.884 7f5f921d0b80 Fatal error: can't bind to 10.10.12.131:8888: There may be another Privoxy or some other proxy running on port 8888

HW/SW Environment

- OS: Linux
- Docker: version 24.0.5, build ced0996

Anything else?

Appears to have been introduced by this change to the privoxy startup script in #2610.

The config file looks like this before the script runs:

listen-address  127.0.0.1:8118
listen-address  [::1]:8118

Before the change above the first sed script would replace the IPv4 listen address with the correct one and the second sed script would remove the IPv6 listen address. Now the first sed script replaces both the listen addresses and the second sed script does nothing. This tells privoxy to attempt to listen on the same address twice causing it to fail.

The text was updated successfully, but these errors were encountered:

resuarez · 2023-08-30T10:40:43Z

Same problem here

ilike2burnthing · 2023-08-30T15:39:50Z

@heavygee ^

RafalHo · 2023-08-31T06:26:19Z

Same problem here

sbe-arg · 2023-08-31T06:29:54Z

hahaha same

reverting to 5.0.2 works as usual

pdobrien · 2023-08-31T23:14:46Z

there is a duplicate listen instruction in the privoxy config file. Once you've started the container, open a shell, remove or comment out one of them, and restart.

nleach7 · 2023-09-01T00:56:39Z

there is a duplicate listen instruction in the privoxy config file. Remove or comment out one of them and restart.

My proxy settings are defined as environment variables. Is a config file something I should migrate to?

pdobrien · 2023-09-01T01:58:13Z

I'm talking about the privoxy config file that's generated on container start (/etc/privoxy/config inside the container). Mine contained two listen statements like so:

listen-address 172.17.0.6:8888
listen-address 172.17.0.6:8888

I commented one of them out and restarted the container, and privoxy was able to start normally. One of the changes in the latest release was to privoxy/scripts/start.sh which I assume caused this issue.

pkishino · 2023-09-01T02:31:01Z

@heavygee can you ctake a look at this as you authored the PR, thanks

edgd1er · 2023-09-01T04:17:31Z

the new way to set the ip is too generic and change both listen lines (ipv4 and ipv6):

docker-transmission-openvpn/privoxy/scripts/start.sh

Line 30 in 4829920

sed -i -E "s/^listen-address\s+.*/listen-address ${adr}:$1/" "$2"

Either move

docker-transmission-openvpn/privoxy/scripts/start.sh

Lines 32 to 33 in 4829920

    
           # Remove the listen-address for IPv6 for now. IPv6 compatibility should come later 
        
           sed -i -E "s/^listen-address\s+\[\:\:1.*//" "$2"

to line 26, before ipv4 modification, or fix the current sed.

here is an example of the replacement I use on another project using privoxy:

# Set the port for the IPv4 interface
  adr=$(ip -4  a show eth0| grep -oP "(?<=inet )([^/]+)")
  adr=${adr:-"0.0.0.0"}
  sed -i -E "s/^listen-address\s+[0-9]{1,3}.*/listen-address ${adr}:${port}/" "$2"

I'm sorry, i'm not using anymore this project and my fork is too much different from this one to send a PR.

heavygee · 2023-09-01T17:09:20Z

Yeah, my bad on that too-grabby sed 🙄 - the #2678 PR has the better fixes in it - can that PR get approved and merged - for preference?

Otherwise, I have submitted PR #2695 to remedy my error.

pkishino · 2023-09-01T23:01:46Z

can all of you please pull :dev branch and test it there, if everything is fine I'll release an update..

Mossop · 2023-09-02T09:12:49Z

can all of you please pull :dev branch and test it there, if everything is fine I'll release an update..

This seems to work for me.

juliemars · 2023-09-02T09:42:52Z

can all of you please pull :dev branch and test it there, if everything is fine I'll release an update..

yep working for me as well thanks!

oregonpillow · 2023-09-03T08:12:10Z

@pkishino would you be open to tests in the pipeline to prevent this kind of issue in the future?

Would you be open to creating CI tests that:

downloads a small public torrent
check the file hash post download to confirm torrenting/vpn functionality worked
a test to confirm privoxy connections work.

i would be happy to help on this.

pkishino · 2023-09-03T08:30:33Z

Hey, sure, That sounds interesting.

…

On Sun, 3 Sep 2023 at 17:12, Timothy Pillow ***@***.***> wrote: @pkishino <https://github.com/pkishino> would you be open to tests in the pipeline to prevent this kind of issue in the future? Would you be open to creating CI tests that: 1. downloads a small public torrent 2. check the file hash post download to confirm torrenting/vpn functionality worked 3. a test to confirm privoxy connections work. i would be happy to help on this. — Reply to this email directly, view it on GitHub <#2692 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7OFYSZ4DMLP6ALVN22EZLXYQ3WNANCNFSM6AAAAAA4EJNB6M> . You are receiving this because you were mentioned.Message ID: ***@***.***>

usma0118 · 2023-09-03T16:14:27Z

+1 facing same issue.

ilike2burnthing · 2023-09-03T18:48:04Z

@usma0118 #2692 (comment)

pkishino · 2023-09-04T03:08:04Z

fixed by #2696

pkishino closed this as completed Sep 4, 2023

tutorempire mentioned this issue Nov 29, 2023

[REQUEST] Transmission-OpenVPN: NordVPN Settings alexbelgium/hassio-addons#1102

Closed

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Privoxy fails to start due to duplicate listen address in config file #2692

Privoxy fails to start due to duplicate listen address in config file #2692

Mossop commented Aug 30, 2023

resuarez commented Aug 30, 2023

ilike2burnthing commented Aug 30, 2023

RafalHo commented Aug 31, 2023

sbe-arg commented Aug 31, 2023 •

edited

pdobrien commented Aug 31, 2023 •

edited

nleach7 commented Sep 1, 2023

pdobrien commented Sep 1, 2023

pkishino commented Sep 1, 2023

edgd1er commented Sep 1, 2023

heavygee commented Sep 1, 2023 •

edited

pkishino commented Sep 1, 2023

Mossop commented Sep 2, 2023

juliemars commented Sep 2, 2023

oregonpillow commented Sep 3, 2023

pkishino commented Sep 3, 2023 via email

usma0118 commented Sep 3, 2023

ilike2burnthing commented Sep 3, 2023

pkishino commented Sep 4, 2023

Privoxy fails to start due to duplicate listen address in config file #2692

Privoxy fails to start due to duplicate listen address in config file #2692

Comments

Mossop commented Aug 30, 2023

Is there a pinned issue for this?

Is there an existing or similar issue/discussion for this?

Is there any comment in the documentation for this?

Is this related to a provider?

Are you using the latest release?

Have you tried using the dev branch latest?

Docker run config used

Current Behavior

Expected Behavior

How have you tried to solve the problem?

Log output

HW/SW Environment

Anything else?

resuarez commented Aug 30, 2023

ilike2burnthing commented Aug 30, 2023

RafalHo commented Aug 31, 2023

sbe-arg commented Aug 31, 2023 • edited

pdobrien commented Aug 31, 2023 • edited

nleach7 commented Sep 1, 2023

pdobrien commented Sep 1, 2023

pkishino commented Sep 1, 2023

edgd1er commented Sep 1, 2023

heavygee commented Sep 1, 2023 • edited

pkishino commented Sep 1, 2023

Mossop commented Sep 2, 2023

juliemars commented Sep 2, 2023

oregonpillow commented Sep 3, 2023

pkishino commented Sep 3, 2023 via email

usma0118 commented Sep 3, 2023

ilike2burnthing commented Sep 3, 2023

pkishino commented Sep 4, 2023

sbe-arg commented Aug 31, 2023 •

edited

pdobrien commented Aug 31, 2023 •

edited

heavygee commented Sep 1, 2023 •

edited