aptalca

Isn't that a remote access port for postgre? There is no webserver there, is there? The conf you have is only for proxying http (web servers), not regular tcp traffic. For that you'd need to use the stream plugin

Correct. Don't forget to follow the directions at the top otherwise nginx won't start due to duplicate location blocks

Check out the heimdall subfolder conf sample and you'll see how

Try 0.0.0.0

You gotta give us more info. Where is it running? Inside the code-server container?

Shouldn't be an issue

You can do a new docker mod. We already provide a few. They are about to officially launch and the readmes will have info on them starting this week. https://mods.linuxserver.io

Https default is 443. If you use a different port, you'll have to define it to browse it like https://domain.com:1443

Did you Google error 522? It tells you exactly what the problem is. Cloudflare can't reach your server. Check your port forwarding https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

Your renewal conf file is broken for some reason. Perhaps a bad backup/restore. Change the parameters and recreate to force a renewal

Possibly

You don't have to change the server name. That sets your subdomain. Leave it as plex.* Change the container name to plex so you don't have to modify the proxy conf. Follow the rest of the steps outlined at the top of the proxy conf

Each task uses 1 core/thread. If you're only assigned 1 task, it will only use 1 core at a time. You select the max number of cores boinc can use through computing preferences by entering in a percentage. So on a 4 thread machine, you set 50% in settings, it will run a max of 2 tasks at a time and use 2 threads total

Try accessing on the ip directly, not via reverse proxy

A few things wrong here. Using uppercase letters in container name will prevent nginx from properly resolving it. You'll get a 502 If you're trying to access https://url:32400, you're not going through reverse proxy as letsencrypt is accessed at port 443, not 32400. You are giving direct access to Plex via that port. Start over and follow our guides: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/ And for troubleshooting: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

If it was open source you could PR, but it's not. I guess you'll have to let them know and wait until they get to it.

A couple of others on discord mentioned a cloudflare outage that resulted in the same outcome as above. No errors setting txt records, but they can't be verified.

Docker containers can share the gpu

Long time Plex issue. Report it to them

Too many users, the well dried up 😅

You bring up an interesting point I had not considered. s6 supervisor executes the init files in alphabetical order. The custom files in that folder are executed by a script named "99-custom-files" and the python3 docker mod creates an init file named "99-python3" and that's why your custom file is executed before python3 installation. I guess I'll have to update all the mods to use "98-blah" so they execute before the custom files. Until then, restarting the container should fix it for you because on second start, pip will already be installed when your custom file runs.

If you set it to only one gpu's id, f@h will still see both gpus, but it won't be able to start the job on one of them. You'll see an error in the log, something like " no compute devices matched gpu #0 blah blah you may need to update your graphics drivers". I paused that gpu so it no longer receives jobs it won't be able to complete.

Did you read my linked thread above? Post a full log, post your docker run and check the openvpn log in the config folder

Because openvpn-as got an update and they changed some things Check the openvpn logs in the config folder

I tested with 2 gpus and it works There's a screenshot of it in this article: https://blog.linuxserver.io/2020/03/21/covid-19-a-quick-update/ By the way, you don't need to edit the config at all (in fact, don't). If you allow both gpus via nvidia arguments, they'll both be used automatically.