aptalca

FYI, beta18 has a breaking change. You need to delete config folder and start from scratch (only need to enter the emby address and api key)

It seems they're having dns propagation issues at the moment so dns may not be resolving. With the pandemic and most people working from home, cloud service reliability has gone down across the board.

$upstream_port is defined two lines above

Use an incognito window

Sure you can. But you gotta read up and understand nginx configs. Server blocks are for matching and defining domains and subdomains, and location blocks are for uri (subfolder and rest).

Port forwarding issue

That's also why we provide mods for it: https://mods.linuxserver.io

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