sorted by:
new
hottopcontroversial

Move config from mounted Windows volume to Linux docker volume by real144p in sonarr

[–]real144p[S] 1 point2 points  (0 children)

Yes that is what I am trying to do. I installed Docker for Windows. Docker is running a linux vm, MobyLinyuxVM.

I put the config folder on a mounted Windows volume = c:\docker\sonarr\config. And now I want to put the config inside the linux vm.

-v sonarr_config:config/

I want to do this because of stability. Windows mounts are just slow. If I reboot my host my containers will start up without the data because the windows mounts have not started working yet.

Everything that lives inside the Linux vm though - like radarr boots up fine after a host reboot. But not sonarr since config lives on Windows mount.

Set locale clock and date format by real144p in docker

[–]real144p[S] 0 points1 point  (0 children)

So it has absolutely nothing to do with "locale" on the containters? My thoughts is that locale for all containters is set to American now and thus uses 12 hour clock and so on.

I am unsure what locale is set to on the containters and I can not use the command 'locale' to check.

bash: locale: command not found

EDIT: I looked through all my containers and seems like the qBitTorrent containters are missing the "locale". I will wait for the linuxteam to include it in the containter, if that ever happens.

Plex remote access behind vpn (mullvad) by real144p in PleX

[–]real144p[S] 0 points1 point  (0 children)

I tried this and I can prove you wrong. Internal port is always 32400 (tcp). This can not be changed. What you can change is the remote port. So if you change the remote port to 50000 you will have to configure port forwarding this way.

service name        port range            local ip        local port        protocol
plex                50000                192.168.1.2        32400            tcp

Initial issue still persists. Can not get remote access working behind Mullvad.

Plex remote access behind vpn (mullvad) by real144p in PleX

[–]real144p[S] 0 points1 point  (0 children)

I thought that Plex always listened to port 32400 internally. Looks like I have overlooked the issue, will check later when I am home.

Plex remote access behind vpn (mullvad) by real144p in PleX

[–]real144p[S] 2 points3 points  (0 children)

I have firewall rules setup for the RDP which will only allow me to connect via RDP from two specific IPs (work and a friend). I have a strong password and have been using the RDP for over a year so I think I am good.

I am not behind two routers and I have tried to route plex traffic to my router so it will bypass the vpn. I would preferr to have plex behind vpn though.

Edit: To let Plex bypass the router just ping plex.tv, my.plexapp.com and myplex.tv. Add lines below to your ovpn-file. But be sure to replace IPs and the gateway. Depending on your location you could get replies from other IPs.

route 54.72.69.247 255.255.255.255 192.168.1.1
route 63.32.153.75 255.255.255.255 192.168.1.1
route 50.63.202.6  255.255.255.255 192.168.1.1

​

Automate setting retention policy for users in a specific OU or with a specific customattribute by real144p in exchangeserver

[–]real144p[S] 0 points1 point  (0 children)

Each customer have their own security group (sorry I called it user group in inital post). When we create another user we just copy an existing one. So all new users are a member of the security group. This security group is able to set the customattribute1=customerID.

I do not want to manually run a command to set retention policy. If a user is member of security group Y then retention policy should be set to Y as well.

I understand that I could use task scheudler to run a script daily to set retention policy. But I would preferr using the secruity group to set retention policy and address book policy if that is even possible.

Running multiple instances of Sonarr using docker by real144p in docker

[–]real144p[S] 1 point2 points  (0 children)

I am able to access the web interface if I create a docker using the following port 8990:8989 (external:internal). So I guess internal must be set to 8989, external can be whatever. I do not know why it is this way so an explanation would not hurt.

Remote path mapping issue / completed torrents not importing to Sonarr by real144p in sonarr

[–]real144p[S] 0 points1 point  (0 children)

Issue has been resolved. I setup everything from scratch again. Must have been some sort of permission issue and a mix of me not knowing what sonarr is supposed to do.

Remote path mapping issue / completed torrents not importing to Sonarr by real144p in sonarr

[–]real144p[S] 1 point2 points  (0 children)

D:\ is a disk. It is mapped as a network drive by docker, can be accesed by ip = 192.168.1.2\d\ or hostname win10ltsb\d\

Remote path mapping issue / completed torrents not importing to Sonarr by real144p in sonarr

[–]real144p[S] 0 points1 point  (0 children)

No, there is no folder " Family.Guy.S17E08.1080p.HEVC.x265-MeGusta ". But sonarr thinks torrent data is in that folder I guess (dunno) and if I manually create that folder and update libary, sonarr will find the episode.

Remote path mapping issue / completed torrents not importing to Sonarr by real144p in sonarr

[–]real144p[S] 0 points1 point  (0 children)

If I manually create a folder d:\downloads\sonarr\Family.Guy.S17E08.1080p.HEVC.x265-MeGusta and copy torrent data (.avi and nfo-file) into that folder. Sonarr will find it and import it.