Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when using proton port flips often and has trouble #317

Open
5 of 6 tasks
chrisdrackett opened this issue Oct 13, 2024 · 0 comments
Open
5 of 6 tasks

when using proton port flips often and has trouble #317

chrisdrackett opened this issue Oct 13, 2024 · 0 comments

Comments

@chrisdrackett
Copy link

chrisdrackett commented Oct 13, 2024

Is there a pinned issue for this?

  • I have read the pinned issues

Is there an existing or similar issue for this?

  • I have searched the existing issues

Is there any comment in the documentation for this?

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

Is this related to the container/transmission?

  • I have checked the container repo for issues

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

Config used

    image: haugene/transmission-openvpn
    container_name: transmission
    cap_add:
      - NET_ADMIN
    volumes:
      - /volume1/docker/transmission/proton:/etc/openvpn/custom/
      - /volume2/downloads:/data
      - /volume1/docker/transmission/config:/config'
    environment:
      - OPENVPN_PROVIDER=custom
      - OPENVPN_CONFIG=us-az-106.protonvpn.udp
      - OPENVPN_USERNAME=…
      - OPENVPN_PASSWORD=…
      - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
      - LOCAL_NETWORK=192.168.0.0/16
      - TRANSMISSION_WEB_UI=transmissionic
      - TZ=US
      - PGID=100
      - PUID=1036
      - LOG_TO_STDOUT=true

Current Behavior

I'm seeing the following in the logs:

tm

where it'll find a port and its open, then immediately set another port. At this point it will try and fail to find the new port open 50 times.

Expected Behavior

When it finds an open port stick to it for more than a second

How have you tried to solve the problem?

I've reviewed the script, but I'm not an expert on any of this.

Log output

posted in current behavior

Environment

- OS:
- Docker:

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant