-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Can no longer access web interface and connection doesn't seem to be working #1374
Comments
Can you provide your log? I am looking into some issues with the dead web interface. |
Let me know if there's anything else i can do. I tried switching the server it connects to but i get the same result.
|
seems to be giving me a tls error now.
|
Yes, |
They've never changed, but I'll check them to see if I have anything weird going on. Could the config files being out of date be causing this? |
There is an error "Supplied config ipvanish-US-Dallas-dal-a39.ovpn.ovpn could not be found." in the log |
No matter what I try I get that, none of the servers will connect, then it tries the default and seems to connect but nothing works. I verified that they do work normally through the vpn software on my PC. How would I check to see if it's the correct ovpn file? |
The fact that is saying ".ovpn.ovpn" makes me think it is a config error or naming issue. |
Oh, I see that now, I'll check |
Please check the path/name in the config file as well as the name of the actual .ovpn file |
i copied that straight from the config, i fixed the duplicate ".opvn.opvn" that was from copy and pasting and not paying attention, but it doesnt fix the problem, still get the exact same errors. https://www.ipvanish.com/software/configs/ if where i got them from, should i look somewhere else? |
Can you upload the new log file? |
You might also want to check if you are getting UDP packets using tcpdump. |
|
I am still seeing "Supplied config ipvanish-US-Dallas-dal-a39.ovpn could not be found." |
yes, but no matter which server i switch it to it doesnt work, same error on all of them. thats why i wondered if their updated configs were the issue. (i have no idea what i'm doing or talking about) |
Can you provide your docker start cmd? |
this? |
i should note this has been running steadily for a very long time with no settings changed, which was why i was so confused |
thanks for helping, i appreciate the effort |
Where are you putting your .ovpn file? |
Are you using docker run? or docker compose? |
Sure, note that I am not dev on this project, I am a user as well, it just happened I come across some issue that I am trying to fix, I try to help but I am not the expert on this. |
This happened once before and it was randomly the default server he had set stopped working. I changed the server and that fixed it. That's why i was wondering if they just needed to update the configs or something. This is border line over my head |
Can you also upload the defalt.ovpn file in ipvanish, that should be what it is using when fallback happens. |
I think the current use the ipvanish-NL-Amsterdam-ams-a03.ovpn, but I don't think that is what got used by what your log shows. |
That (defalt.ovpn) was updated on Mar 29 on with commit f79f03c |
In fact, all config files were updated on Mar 29 for IPVanish, if you still have an old version of it and it is falling back to default it will cause problems I think. |
I don't know anything about the .opvn files, or where to find them. That part has always just worked. I use the docker app on my synology nas to run it....I just flip the switch on the container to turn it on and it's worked great for 2 years. |
Sorry, I wasn't seeing all of your comments, missed quite a few of them. |
I also installed the dev branch with the exact same results |
Hey @seamartin00. I see you've been trying a lot of different approaches here. It might be that the configs are outdated but looking at this page that you linked to seems to always show today's date. Anyways. I want you to pull the latest version of the image and try to completely recreate your container setup. I see the list of environment variables you have set up in your docker setup and the vast majority of that is no longer needed. I see that you have mounted "/video" to "/data/completed". I would recommend you to mount all of /data from within the container to a folder on your disk. This is both to store Transmission operational data as well as keeping incomplete torrents on the local disk as containers usually have a limit on storage (I've seen 10GB). After you've successfully updated your container, it will be visible in the logs and we'll see from there. I'll have a look at making an update script for config files for IPVANISH so that the configs will keep up to date. |
Allright. So I've created a script that will run for each container startup and will fetch a fresh set of configs for IPVanish, see #1456. |
Ok, appreciate that info. I'm headed off to work right now but I'll go through all of that when I get home. I'm learning all this stuff as I go, so i really appreciate the help. |
Looking at this again. You also need to remove the |
@haugene I had this same issue and fixed it by removing the TRANSMISSION_WEB_HOME variable. I saw in #1452 (and here) that many variables are no longer needed and you recommended creating a new container to clean things up. Is there any way to get a list of only the current variables? I'd rather not create a new container if I don't have to and don't mind going through one by one to remove those no longer needed if I have something to compare against. Thanks! |
@brossow Well. Necessary. There's few of those. OPENVPN_PROVIDER, OPENVPN_CONFIG, OPENVPN_USERNAME and OPENVPN_PASSWORD are a few core ones. Then the LOCAL_NETWORK is of course a friend when it comes to accessing the web ui. Apart from that there are no "mandatory" variables. But there is a short list of transmission settings that you cannot set through the UI. That means, you can - but they will be overwritten on the next restart. This used to be all of them, but is now just this list: https://github.com/haugene/docker-transmission-openvpn/blob/master/Dockerfile#L33 The reason they are special is that we modify networking, file permissions and other stuff according to what they're set to. So we need you to override them with variables if you want to override them. Apart from that everything can be set in Transmission UI. |
@haugene Great info. Thanks for the FAST reply! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I was wondering if something in a recent update caused my setup to no longer work? Its been running stable with no changes for ages and now i get nothing. I noticed the configs for IPVANISH updated today (https://www.ipvanish.com/software/configs/) but im not sure if thats the issue or not. I tried to switch back to the default server and had no change. I also cannot open the transmission web interface. Any ideas on what to try next?
The text was updated successfully, but these errors were encountered: