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

[BUG] - How to run 2 instances of this docker #175

Open
7 tasks done
dhbtfs opened this issue Feb 15, 2023 · 1 comment
Open
7 tasks done

[BUG] - How to run 2 instances of this docker #175

dhbtfs opened this issue Feb 15, 2023 · 1 comment
Labels

Comments

@dhbtfs
Copy link

dhbtfs commented Feb 15, 2023

Version of protonvpn-docker

NA

Credential & Plan

  • I have verified that my VPN credentials are valid
  • I am using OpenVPN credentials and not my proton account credentials.
  • I have verified that the servers I am trying to connect to are available under my plan.

System Architecture

NA

Running on a NAS?

Yes

Container Runtime

Docker with defaults

Version of Kubernetes

NA

Version of docker/podman runtime

NA

Troubleshooting

  • I have tried steps mentioned in TROUBLESHOOTING
  • I am using latest version of the docker image

Relevant log output

No response

Any additional info

Obviously I know how to make another copy, but if I run both. 2nd connection won't establish.
Is there any way to fix this so they wouldn't clash with each other?
I am using 1 for P2P and 1 for Jdownloader random server.

Code of Conduct & PII Redaction

  • I agree to follow this project's Code of Conduct
  • I have removed any sensitive personally identifying information(PII) and secrets from in this issue report.
@dhbtfs dhbtfs added the bug Issue is a bug label Feb 15, 2023
@tprasadtp tprasadtp added help and removed bug Issue is a bug labels Mar 22, 2023
@PrometheusWannaB3
Copy link

How are you running it? docker commands, podman or docker-compose?

There should be some log files from the docker host for what's happening. for example my secret key file wasn't chmod'd to 600 and it wouldn't run at all.
Found that with 'docker-compose logs '

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

No branches or pull requests

3 participants