Jump to content

aptalca

Community Developer
  • Content Count

    2837
  • Joined

  • Last visited

  • Days Won

    2

aptalca last won the day on March 16

aptalca had the most liked content!

Community Reputation

266 Very Good

5 Followers

About aptalca

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Check out the heimdall subfolder conf sample and you'll see how
  2. You gotta give us more info. Where is it running? Inside the code-server container?
  3. 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
  4. Https default is 443. If you use a different port, you'll have to define it to browse it like https://domain.com:1443
  5. 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/
  6. Your renewal conf file is broken for some reason. Perhaps a bad backup/restore. Change the parameters and recreate to force a renewal
  7. 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
  8. 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
  9. Try accessing on the ip directly, not via reverse proxy
  10. 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/
  11. 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.
  12. 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.