Closed Shamazo closed 1 year ago
this was transferred as it is a provider issue, not container issue.. second, please try using dev branch before raising any further issues.. third, check that /config/openvpn-credentials.txt contains username/password
Thank you for your help. My mistake with the repos, I had thought it belonged in the main repo since thats where the nordvpn scripts are located.
After much debugging, I found my solution.
"/config/openvpn-credentials.txt" did contain my username/password, but when inspecting it with cat, I had missed that there were extra newlines between the username and password. This is a very dumb mistake, but if anyone runs into this in the future when their secrets are base64 encoded, do "echo -n $password | base64" and not "echo $password | base64"
Thank you for your help. My mistake with the repos, I had thought it belonged in the main repo since thats where the nordvpn scripts are located.
After much debugging, I found my solution.
"/config/openvpn-credentials.txt" did contain my username/password, but when inspecting it with cat, I had missed that there were extra newlines between the username and password. This is a very dumb mistake, but if anyone runs into this in the future when their secrets are base64 encoded, do "echo -n $password | base64" and not "echo $password | base64"
thank you, even after looking at the file after my recent hydration change i was confused. cheers :people_hugging:
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
openvpn is requesting user authentication, but the username and password are set in the environment variables. This results in the container being unable to start.
Anything else?
This configuration used to work ~2 years ago when I initally set it up. Today I was bringing my cluster back online and needed to update the nordvpn credentials, and that was when I ran into the issue. I am probably doing something stupid ... but I haven't been able to resolve this in a few of hours of trying.