saarg
Community Developer
-
Joined
-
Last visited
Everything posted by saarg
-
This container is only doing letsencrypt/nginx. No dynamic ip stuff.
-
You add that in the extra domain field. If it isn't i the template, then add a variable in the template checking the correct name in the github link in the first post.
-
I don't have it bookmarked, so no link, but it's somewhere in those threads. Posted by aptalca. Nginx is black arts for me, but nginx can handle multiple things on port 443 at the same time. Try googling reverse proxy openvpn and the first hit should be a guy that did it. Edit:
-
You can use nginx to proxy the vpn connection. There should be instructions in this thread or the letsencrypt thread for how to do it. Should be posts from @aptalca
-
Why do you need to set up port share?
-
It should work as with every other container. Looking at your screenshot, you have changed the PUID and PGID from the standard 99/100. Any reason for that? Also, posting the container log might help to figure it out.
-
Maybe because he tries to be nice?
-
If you run the offical Plex container, please use their support forum. Or if you think this is an unraid issue, open a topic in the general support subforum.
-
This is support for unraid users. Go to our discourse forum or discord for support on other platforms.
-
I recently exchanged one of my cache disks from a Samsung EVO 850 500GB to a nvme 1TB Samsung EVO 860. The first issue I noticed was that none of the docker containers worked as it seems that the docker.img file became read only while doing the initial replace (You probably understand better what happened from the log). Should the mounting of docker.img maybe wait until device replacement is finished? Anyway, that is not the main issue I wanted to report, and it was fixed by stopping and starting the docker service. I followed the FAQ entry here: After I replaced the drive I still got drive full messages when copying to a share with cache enabled. When I checked the unraid gui, the size of the cache pool was still saying 750 GB even though I now had two 1TB disks. After a quick check, I saw that the filesystem on the new 1TB drive was the same size as the old 500GB drive. After running btrfs filesystem resize 1:max /mnt/cache the issue was resolved. I can see from the syslog that it does the resize command, but it looks like it's using the old device /dev/sdc1 and after the resize the device is changed to /dev/nvme0n1p1. I know this is 6.7.2 and this might be changed in 6.8, but I'll post it in case it's not. Below is the output of some btrfs commands before and after the resize command. root@Server1:~# btrfs fi usage -T /mnt/cache Overall: Device size: 1.41TiB Device allocated: 931.46GiB Device unallocated: 512.39GiB Device missing: 0.00B Used: 624.15GiB Free (estimated): 408.50GiB (min: 408.50GiB) Data ratio: 2.00 Metadata ratio: 2.00 Global reserve: 130.98MiB (used: 0.00B) Data Metadata System Id Path RAID1 RAID1 RAID1 Unallocated -- -------------- --------- --------- -------- ----------- 1 /dev/nvme0n1p1 463.70GiB 2.00GiB 32.00MiB 465.78GiB 2 /dev/sdb1 463.70GiB 2.00GiB 32.00MiB 512.36GiB -- -------------- --------- --------- -------- ----------- Total 463.70GiB 2.00GiB 32.00MiB 978.14GiB Used 311.39GiB 699.41MiB 96.00KiB root@Server1:~# btrfs filesystem show /mnt/cache/ Label: none uuid: ca04e038-59fa-4d03-a900-74b50150a144 Total devices 2 FS bytes used 312.07GiB devid 1 size 465.76GiB used 465.73GiB path /dev/nvme0n1p1 devid 2 size 978.09GiB used 465.73GiB path /dev/sdb1 root@Server1:~# btrfs filesystem resize 1:max /mnt/cache Resize '/mnt/cache' of '1:max' root@Server1:~# btrfs filesystem show /mnt/cache/ Label: none uuid: ca04e038-59fa-4d03-a900-74b50150a144 Total devices 2 FS bytes used 312.28GiB devid 1 size 931.51GiB used 465.73GiB path /dev/nvme0n1p1 devid 2 size 978.09GiB used 465.73GiB path /dev/sdb1 The command below was ran today as I forgot to run it after the resize. root@Server1:~# btrfs fi usage -T /mnt/cache Overall: Device size: 1.86TiB Device allocated: 959.46GiB Device unallocated: 950.14GiB Device missing: 0.00B Used: 641.83GiB Free (estimated): 632.56GiB (min: 632.56GiB) Data ratio: 2.00 Metadata ratio: 2.00 Global reserve: 140.84MiB (used: 0.00B) Data Metadata System Id Path RAID1 RAID1 RAID1 Unallocated -- -------------- --------- --------- --------- ----------- 1 /dev/nvme0n1p1 477.70GiB 2.00GiB 32.00MiB 451.78GiB 2 /dev/sdb1 477.70GiB 2.00GiB 32.00MiB 498.36GiB -- -------------- --------- --------- --------- ----------- Total 477.70GiB 2.00GiB 32.00MiB 950.14GiB Used 320.21GiB 725.50MiB 112.00KiB server1-diagnostics-20191221-2036.zip
-
Google is your friend. https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/
-
That is normal if you set the version variable to latest. But why did you set your PUID to 999? If you use unraid that should be 99.
-
I did not see that yesterday. Probably blind. I don't know what we are going to do about it yet, but it seems strange he didn't update the bridge if that is the new version.
-
It says where in the reddit thread: Linux: /usr/lib/plexmediaserver/Plex Relay
-
Where does the dev say that booksonic bridge is going forward? There haven't been a commit on github for 2 years, so I find that strange.
-
It will not, as you don't have the correct name or path to plex relay by looking at the reddit link.
-
The ssl port is 1443, unless you have changed it. domoticz.sh isn't used in the container.
-
Plex usually knows what is a problem in their software or in the container. So shouldn't be a problem going to the official forum.
-
Yes, update the container. Do not use the built in updater.
-
How long did you wait after you started the container? It generates the ssl certificate on first run, so might be you didn't wait until the certificate was created.
-
It's not something we support, so it's on your own risk. You have to follow the airsonic documentation and then figure out how to do it in a container.
-
I don't see why you post this in the Airsonic support thread?
-
If you change it to host, the port mapping doesn't do anything, so it's still using port 1900.
-
Did you follow the upgrade procedure for command line linked in the first post?
-
I triggered a build, so it should be ready in a couple of hours.
