aptalca

Your port forwarding is not correctly applied. Try restarting the router

Open a github issue for a feature request and we'll add it when we get to it

I'll look into port share. It sounds like it might be useful

No, there is no dyn dns update. We recommend ddclient or router based solutions Edit: looks like saarg beat me to it

Never used port share in openvpn, don't really know anything about it. Unfortunately stream and http cannot listen on the same port. For a while I used port 80 with stream for openvpn. Then I switched to using port 53 over udp. Both let me access openvpn on various public wifi that normally block vpn connections. It's not bulletproof, but works well. I'm now using wireguard over 53 udp and openvpn over 80 tcp

Explain "I have given the server a static IP address"

See the article on our blog titled "customizing our containers" and you can create an init script that deletes it on container start

Correct. Stock unraid does not have the necessary nvidia drivers or the nvidia runtime required. The nvidia plugin allows you to install custom builds of unraid that include the necessary drivers and docker runtime. Only install the unraid builds via the nvidia plugin to make sure that your Plex container continues to use nvidia hw transcode. And yes, until recently, Plex only supported hw encode. Now it supports both. No need for other scripts or wrappers. Just the custom unraid build and the linuxserver container make it work.

Set the max speed to 12 and then set the throttle to 8 (66%). I would assume the way you currently set it up (100%) would be handled as "no throttle"

According to the readme, you're supposed to run it on your host, not inside the plex container

Clarifying that in the proxy conf. Thanks for the heads up: https://github.com/linuxserver/reverse-proxy-confs/pull/108

Why not assign them different subdomains and run everything on 443?

Log entry is from November 17, which states that the expiration date is December 26 and thus not due for renewal. That's correct and expected behavior. Read the readme to find out how renewals are handled and what to do when you receive the expiration email.

They get rotated weekly. You should have logs for up to a year

Still not supported. None of us use ipv6 so can't even test. This is the only attempt made (by an outsider contributor): https://github.com/linuxserver/docker-duckdns/pull/11

Modify an existing conf and use the ip in the proxy pass directive

Both localhost and 127.0.0.1 refer to locations inside the letsencrypt container. Replace that with an address letsencrypt can use to access traccar Also it's set to listen only on port 80, which is not right. Don't copy paste a config from elsewhere. Take an existing proxy conf and modify accordingly. Also see the examples provided in the default site conf.

See here for customizing: https://blog.linuxserver.io/2019/09/14/customizing-our-containers/

Your docker run and how you set up the accounts to start

Most likely line endings in the script. Make sure it's Unix format

Probably the app redirecting to the host address without the port

No, not a common issue. But without any further info, impossible to tell what causes it

Unraid stock does not have nvidia runtime or the nvidia drivers for hardware transcode. You need to install the custom nvidia version through the nvidia plugin

Did you check line 3 of your ssl.conf?

Did you upgrade from an older openvpn-as version (in other words, did you update for the first time in a long time)? If so, see the notice in the readme. You'll have to edit the as.conf and uncomment the admin line, replace it with a non-existing user.