fmp4m

Members
  • Content Count

    345
  • Joined

  • Last visited

  • Days Won

    1

fmp4m last won the day on April 22 2018

fmp4m had the most liked content!

Community Reputation

15 Good

About fmp4m

  • Rank
    Member
  • Birthday September 26

Converted

  • Gender
    Male

Recent Profile Visitors

1441 profile views
  1. Do not go with a r420 or Rx20 for your office if you need it to be quiet. These are made for datacenters and are not considered quiet. Mine are installed in an area I dont hear, and yes have way more than 16tb in each.
  2. NX = No Execute Mode PSS = Power Supported State You can safely have both off.
  3. Do you have Discord or some other online messenger? Can you PM me your info so I can troubleshoot directly with you. I feel we can solve this rapidly that way.
  4. NAT Loopback and DNS Rebinding are completely different. Plex uses "HASH".plex.direct to create dns entries or proxy to your server. the domain.com/plex service uses this. You can verify this is being done by visiting the /plex location and reviewing the certificate, which you will find is issued to plex.direct. I feel that something is interrupting the connection to /plex (XML-Plugins-API) interface causing you this issue. Can you create another /anything and point it to a known working interface? sonarr/radarr/npm If this works, then the config is working and creating the
  5. Hi Tucubanito07, The npm-01 that had the corrupt PEM would need its "conf" file deleted from the app data. You can copy the conf to another folder and review it to recreate that proxy host. When you delete that conf, NGINXProxyManager will load all but that host that is corrupted. (which sometimes can be more than one) you would then re-add that proxy host. Example: npm-01 = jimmy.domain.com Delete conf (/etc/letsencrypt/renewal/npm-1.conf) Load NPM Review hosts for missing one or review the conf file for the missing host info and re-add. H
  6. You're welcome. It appears somehow your fullchain.pem became corrupted (likely blanked out). Rebuilding would fix this.
  7. As I have said, I have mine configured and working. One thing I am thinking you may have an issue with /plex/ goes to a ".plex.direct" url by translation. Do you have DNS Rebinding allowed for "plex.direct"? If not, ONLY IP:32400/plex will work. If so, then domain.com/plex/ will work.
  8. Check certs 6,7,12,13,20 as those are erroring. Are those files there? I suspect not. In which case, you will have to delete those hosts and recreate or manually force those to regenerate.
  9. /mnt/cache/appdata/NginxProxyManager/letsencrypt/archive/npm-20
  10. Can you check the archive folder for the originals please?
  11. Have you checked the "/etc/letsencrypt/live/npm-20/" or any of the //etc/letsencrypt/live locations to see if the fullchain.pem is there? It seems the symlinking is broken for them. Example: drwxrwxrwx 1 nobody users 94 Dec 9 17:01 ./ drwx------ 1 nobody users 138 Dec 11 16:39 ../ -rw-rw-rw- 1 nobody users 692 Jul 30 14:01 README lrwxrwxrwx 1 nobody users 29 Dec 9 17:01 cert.pem -> ../../archive/npm-1/cert3.pem lrwxrwxrwx 1 nobody users 30 Dec 9 17:01 chain.pem -> ../../archive/npm-1/chain3.pem lrwxrwxrwx 1 nobody users 34 Dec 9 17:01 fullchain.pem -
  12. Have you created/configured "proxy.conf" and placed it where it wants it? An alternative to the proxy.conf file is setting those options in the advanced nginx settings of the advanced location (gear cog). However I am not proficient with how to format them for this location. client_max_body_size 10m; client_body_buffer_size 128k; proxy_bind $server_addr; proxy_buffers 32 4k; #Timeout if the real server is dead proxy_next_upstream error timeout invalid_header http_500 http_502 http_503; # Advanced Proxy Config send_timeout 5m; proxy_read_timeout 240; proxy_send_
  13. @CorneliousJD I think I finally, through troubleshooting, figured out a fix that will work for your environment. In you Organizr SSO Setup point it to the local IP/Docker IP of plex. http://IP:32400/plex I was digging in my sso settings and any local comm's go through these on my setup, only externally clickable links etc do not.
  14. I successfully have plex.domain.com setup and working. I also have plex.domain.com/plex working. 401 Unauthorized - is expected, IF you are not logged in for the /plex to work. However my /plex location is https not http, is yours?
  15. You can add your TLD example.com and under custom locations point it to /plex.