strike

Take a look at the link in the post right above yours and you'll have the answer..

lol, glad I could help

Aaah, I see it now. You have put the endpoint address in the VPN_OPTIONS variable.. This is for advanced OpenVPN options only. Remove that and I think you should be good to go

Then I don't know, better wait for the expert. But one thing you can do is to edit the container and set the debug variable to true, before you start the container again delete the supervisord.log in config, start the container and let it run a few min, then post the log here. Edit: Be sure to remove your username/password

Well, something is obviously wrong with the username an/or password. What happens if you delete that extra line? Are your sure the username/password is correct? Do you have any special characters in the username/password?

First of all you shouldn't be forwarding incoming ports on your router. When you're on a VPN connection the port forwarding must be done on the VPN provider side, not yours. Second, this container does all the "port forwarding" for you if you're using PIA. The only thing you have to do is choose on of the end points that allows port forwarding. The Netherlands would be a good choice I think. I've tried a few VPN providers but the one thing that has been common for all of them is that you get the best speed from the Netherlands, don't ask me why. Third, you could be suffering from "ISP throttling". Where I live some ISP are throttling VPN UDP connectiions, again don't ask me why. If that is the case it can help if you connect over a TCP port instead. Been a while since I've used PIA, but I believe you can choose to connect over TCP, at least you could when I was a member.

Edit the docker and set the DEBUG variable to true. Also delete the log before you start the container again, let it run for a few min and post the new log here. This was also in you log: [warn] Username contains characters which could cause authentication issues, please consider changing this if possible [warn] Password contains characters which could cause authentication issues, please consider changing this if possible

Oh.. So your unriad IP is 172.30.12.x? Then I don't really now.. maybe enable debug (set the debug variable to true), and post a new log

@mashuto I think maybe your lan_network is wrong too LAN_NETWORK defined as '192.168.1.1/24' Think it should be 192.168.1.0 Edit: or 192,168.99.0 if your host IP is 192.168.99.100

LAN_NETWORK defined as '172.30.12.0/24' Change to the correct lan_network See Q5:

No, you have to use "aliases" which are defined in the file. Edit: Or not aliases per se, but the rules has to be defined in the file. An alias is just a combination of rules

It was just a blocked banner right? Than IIRC you can add somthing like this: {-block-as-image} http://192.168.1.1 Where the IP has to be changed to your serverip ofc. If you encounter more images that are blocked on on sistes you can use the same syntax. You can whitelist a specific site or the whole domain. If you use somthing like sickrage/sonarr/radarr/cp you might want to whitelist thetvdb also. Just add .thetvdb.com to the list and you should be good to go. You can just put it in the end of the file. You might also want to write a comment for your future self so you know what it's for.

Use the user.action file to whitelist your server. Don't use the trust file to whitelist. If you do you'll blacklist everything as only the things you whitelist will work.

I believe you have to do the same command but with "checkout master" then restart. Once you're on the master branch again you can update as normal.

From the readme Don't remember if it works on the admin user but it works on normal users.

Before you try to rollback try to stop the docker, see if there is a mako folder in medusa/cache/ (don't remember if it gets deleted at reboot), If it's there delete it and start the docker and see if it works. If not you can try to rollback to the previous version by editing the docker and adding : followed by the tag for the previous version in the repository field. For medusa it would be like this linuxserver/medusa:29 Then apply to download. To find the tag you go to the dockerhub site and click the tags link. When you're ready to update again you can just remove what you added in the repository field or change the tag to latest

If you grab things manually you have to put them in your post processing folder so medusa can do the post processing and mark them as downloaded. That's the proper way to do it, or you can put them directly in your show dir I guess but then you have to go to the show and click on re-scan to get medusa to mark them as downloaded.

AFAIK you have to use NZBtoMedia for it to work. For an 100% correct answer you should ask the devs on IRC (#pymedusa on freenode), or github. But I'm 90% sure that you have to use NZBtoMedia. I'm also pretty sure you can find a guide on how to configure it if you try a google search, I know I have seen it somewhere. But that was for sickrage, don't think it has changed for medusa though.

When you add a show you have to set the default episode status, and you have obviously set that setting to skipped. There are 2 settings when you add as show if I remember correctly, default episode status (for all future episodes) and previous episode status. Since you have set the wrong setting when you added the show, you have to click edit on each show and change default episode status to wanted, and manually change the status to wanted for each episode that is already aired.

You set the indexer when you add the show, so unfortunately I believe you have to delete the show from medusa (be sure to not delete the actual episodes if you have them, medusa will ask) and add it again, this time choosing an another indexer, tvmaze would be a good choice I think. Also, you set the default indexer for when you're adding shows in the general configuration settings "use initial indexer set to". A nice feature would be to able to edit the show, change the indexer and just force a full update on the show. Another would be to pull random posters from the indexer to eliminate this poster problem. I will take this to the devs and see what they say. Just as an FYI the real problem with the posters are that they are marked with the wrong language tag on the indexer. So a random poster in the language set in medusa would be better imo.

There are a couple ways to do this: 1. Go to your show dir delete poster.jpg, go to your docker dir medusa/cache/images and delete the poster there as well as the poster in the thumbnails folder, they are named after the showid on the indexer you're using (295647.poster.jpg). After you have done that go to medusa webui an click on the show, and click force full update. Medusa will now pull images from the indexer. I'm guessing you're using thetvdb, I'm not sure if this is the case for all indexers but for thetvdb medusa is pulling the last poster listed on thetvdb, and I think the issue lies here. So if you're trying the above it will probably pull the last poster again. So go to 2 or 3 2. Change indexer 3. Manually download the poster you want and place it in your show dir naming it poster.jpg delete the poster in your docker cache again and do a force full update, medusa will now pull the poster from your show dir since you already have it there. I don't remember if you have to put it in medusa/cache/images/thumbnails to but if you decide to do that be sure to name it after the showid (295647.poster.jpg)

I don't understand why it works when you changed the network type, it shouldn't matter to openvpn, but hey as long as it works! If the Bridge type is selected, the docker's network access will be restricted to only communicating on the ports specified in the docker settings If the Host type is selected, the docker will be given access to communicate using any port on the host that isn’t already mapped to another in-use docker. I personally like to use bridge on all my dockers so I can map the ports myself. There shouldn't be any security issues "down the line" openvpn is a secure way to connect to your home network. The only thing I would suggest is changing the ip in the routing section back to the unraid ip, and if you wish to have access to other devices in your home network just add those when you need it. As you added the whole subnet in your last change you can now have access to every device in your home network. But you should restrict access only to the devices you need for security purposes in case your certificates gets in the wrong hands somehow..

Hmm, weird.. Been a while since I used the openvpn docker. I don't know if it makes a difference but try instead of your unraidip add the whole subnet, if your unraidip is 192.168.1.xxx add 192.168.1.0/24 in that box,update and restart the docker and try again. And when you try again try to open the webui from the unraid webui first before you try the direct ip:port Edit: And yeah, clear your browser cache on your phone or whatever you're using to browse with.

You're using the unraidip:"dockerport" right? What happens if you open the docker webui from the unraid webui?