RobV

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by RobV

  1. Just got this to work with SWAG as the reverse proxy. I used the method that SpaceInvaderOne uses to fix a 502 Bad Gateway fault in his latest Nextcloud video - this time here: https://youtu.be/id4GcVZ5qBA?t=1375 I used the SWAG recipes example conf file and just changed the upstream app to point to my unraid server IP and upstream port to the host side port. I made sure I had the media share in the SWAG docker container as per the instructions in the example conf file. Restart SWAG and it is now working perfectly! Here is the code I use (with IPs blanked out) ## Version 2021/05/18 # make sure that your dns has a cname set for recipes # make sure to mount /media/ in your swag container to point to your Recipes Media directory # if using Authelia use this one: # Doc: https://vabene1111.github.io/recipes/install/docker/#using-proxy-authentication server { listen 443 ssl; listen [::]:443 ssl; server_name recipes.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; # serve media files location /media/ { alias /media/; } location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app xxx.xxx.x.x; set $upstream_port 8154; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } }
  2. My server managed to go a few days without the error but it came up tonight and I think Fix Common Problems caught it in the attached logs. Could this be the issue here? I've attached the MCElog output and also noted that when the server froze it killed my entire network somehow! Once I restarted the server other devices could get back onto the network again but I had to restart the router to get the internet back up. Curious. Any help appreciated! I might start a burn test and a memtest. gargantubrain-diagnostics-20181113-1901.zip FCPsyslog_tail.txt
  3. Thanks very much, I've put it into troubleshooting mode and I'll wait for the next freeze.
  4. Hi All, I've been using unraid for a few months and so far it has been brilliant. However, over the past two weeks my server is dying almost every night, I won't be able to access the webgui, the console will show the attached errors and all the VMs/Dockers will be frozen. Only a hard restart will bring it back up. I've also noticed that when the server enters this hung state it will be constantly pinging the network and seems to block the rest of the users on the network from accessing the internet. System Details: i7-8700k AsRock Z370 Extreme4 GTX-1050 Additional PCIe USB3 controller The system is stable, I've done 4k video trans-codes over 8+ hours using Handbrake without any issues and prior to installing Unraid I had windows on it with a whole bunch o stability tests. Due to the nature of the problem the attached screenshot is the best I can do with logging the fault, I've included a syslog as well but I don't know if that will include the error. If there is another way to log the issue please let me know and I will get it! Thanks. gargantubrain-diagnostics-20181105-1538.zip