Fma965

Community Developer
  • Posts

    175
  • Joined

  • Last visited

Everything posted by Fma965

  1. thats only to do with netdata, tbh i need to update my config example as mine is so much cleaner now.
  2. its https you need to go to https://192.168.1.43:444 but really you should be accessing it from a domain externally even when internal
  3. you cant use letsencrypt without public ip access you need to forward those ports
  4. you need to ask in the letsencrypt docker thread. also make sure all your values are right in the docker such as domain name and stuff, no simple typo's, also try setting it to not use subdomains and put your domain jxxxxx1.duckdns.org as the main url/domain
  5. no you need to access it from your external IP or from your DNS not from the 192.168.1.104 address so you need to forward port 80 on your router to 85 and then try it from your duck dns address
  6. run the nginx docker (by linuxserver without all the SSL letsnecrypt stuff) and map it as port 81 in docker then see if you can access the nginx web page from your ip and from your duckdns domain.
  7. contact your ISP, everything else looks fine, send me a updated screenshot of your router port forwarding just to be sure.
  8. don't be sorry it's good. Then your dynamic dns may not be up to date with your IP. or your unraid isn't 192.168.1.104
  9. Firstly thanks for adding so much info You have your port forwards backward. should be 443 to 444 and 80 to 81 not the other way around.
  10. you either have your domain not working correctly on duckdns or your router ports are not forwarded correctly or your docker ports are not correct. to clarify you need to forward port 80 and 443 to the ports of your letsencrypt docker
  11. I'm aware of this i was asking specifically how to go back a version (how to find the version number string) , as you can see in my edit in the quoted post i have already found it. Thanks.
  12. How can i go back to the build before last? 1.12.2.4929 1.12.2.4929 broke LG Tv support and i urgently need it working on LG never mind set the VERSION to 1.12.1.4885-1046ba85f Old version numbers can be found here https://whatpulse.org/app/plex-media-server
  13. it can be any port so for example 5363 to 443 is fine, but you then need to pass port 443 on your router to 5363 aswell.
  14. GUIDE UPDATED WITH CHANGE TO PORT NUMBERS TO WORK ON 6.4 Described in my post reply above.
  15. i have tested this on 6.4 fine, make sure you aren't using ports 80 or 443 and instead use like port 444 and 81 and then in your router forward external port 80/443 to 81/444 on your device ip.
  16. You just need to make sure you have the "URL Base" set correctly, sometimes called a webroot or base url in the settings for the application, e.g sonarr is URL Base
  17. Sounds like you aren't setting the base url's correctly this location = / { return 301 /sabnzbd; location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.2:8989/sonarr; } should be (always close a location block off with a } before doing another) location = / { return 301 /sabnzbd; } location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.2:8989/sonarr; } so with this you have 2 ports accessible to the internet 80 and 443, with your way you would have to forward many ports (one for each service) in order to access them from outside your LAN (internet) --- @all here is the config i currently use. https://gist.github.com/Fma965/540219ade8133e65542e9ec15651fe82
  18. it's all good sold my 4790k and purchased a g4400 and cheap 1151 mobo. already have a raid (HBA) card so thats all fine. VT-D was more for future rather than actual current use.
  19. Hi, So i'm downgrading my 4790k which used to host multiple VM's with GPU passthrough and many docker containers such as sonarr and radarr and plex to something that i can get used for around £50-80 and is still capable of running unraid in a purely nas plus syncthing enviroment. what do people suggest? I would prefer one with VT-D still but only for a low powered gpu passthrough (although this seems unlikely to find)
  20. Great, thats just a different way of doing it. Logs will be needed. Most routers allow access the same as remotely (can't think what it's called, something to do with loopback) therefore you can just access it at xxx.duckdns.org/sonarr etc.