Mathervius

Members
  • Content Count

    34
  • Joined

  • Last visited

Everything posted by Mathervius

  1. Just throwing my hat in with the same problem. Syslog server hasn't been working properly for me so I can't attach logs. I rolled back to 6.8.3 for the time being. Before the update to 6.9.1 I had over 200 days of uptime but after updating I was getting daily crashes and my family uses the server too much for that to happen. I don't have any VMs, no GPU, just about 20 docker containers.
  2. I get the same issue everyday after my Auto Backup finishes and restarts Emby. I've posted on the Emby forums and got nowhere with it. What's strange is that it was gone for a while but the bug was reintroduced with an update a while back. I wish I had paid closed attention to when the error started up again
  3. Can you try to put in the containers IP rather than the container name and see if that makes a difference? Did set/change the ombi base URL? What errors show when you try to load ombi(500/401 etc...)? Did you remember to restart the letsencrypt container after making adjustments to conf files? Do any other containers work properly through the reverse proxy? Anything in firewall logs indicating an issue? Side note: it's a lot easier to lend a hand if you make your links actual links so people don't have to copy/paste everyt
  4. You should be able to assign a static IP to the container using an IP within your LAN subnet. I have a couple networks setup for my docker containers. One uses a VLAN (br1.10) and I manually set static IPs for those containers and then the containers on my LAN just get an IP assigned to them from the server but I could just as easily assign static IPs for them as well.
  5. While this is mostly true I recently did a complete new build and there was one pretty decent headache involving networking. I went from a quad port NIC (used as two bonded connections) to a dual port NIC. When I booted the server there was a mess involving my docker containers networking (they're a mix of VLAN/custom IPs/VPN) and also the MAC address was different so my static mapping from my router wasn't picking up the server properly. I ended up deleting my network config file and then rebooted into GUI mode and made my network adjustments. Everything works great n
  6. I think you could go either way but I prefer using the letsencrypt container for it.
  7. So in your conf file you have something like this: location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_whatever <IP_ADDRESS>; proxy_pass http://$upstream_whatever:<PORT_NUMBER>; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; } You will use the containers IP address instead of its name. In your case you would use the VPN containers IP address and whatever port you use to access the service locally. Don't forget to enable some sort of securi
  8. I've done this by just using the containers IP address/port in the letsencrypt conf file for each service.
  9. When I've had issues with community apps not loading in the past it was caused by a DNS issue on the network. Not sure if you've looked into that yet but sometimes I forget to check the simple stuff first.
  10. This will come down to firewall rules on your pfSense box. I was having a bunch of issues getting communication between VLAN/LAN and every time it came down to firewall rules. I would suggest posting or searching on the netgate forums as that's where I had the best luck,
  11. Are you using the latest version? I started getting a lot of failed downloads and servers not being able to connect errors with the latest version. I realized it was caused by them removing python 2 and my scripts were relying on it to run properly.
  12. @Merson I couldn't get FakeDetector or Completion working even with the 2to3 converter. Any tips if you are using these scripts? I loaded up Sab instead and I'm actually impressed with how well it works but I've always used nzbget in the past.
  13. Mine UNRAID box shows up in the left-side menu under "Locations".
  14. That has always worked for me. Are you able to connect through Finder (not using the connect to server function)?
  15. I went ahead and assigned br2 a static IP address. My hope was to add the br2 static IP to an Alias in pfSense and then use that to route that traffic through a VPN. Kind of like if the docker containers were using Host as their network and Host was being router through a VPN. Unfortunately, that plan does not do what I intended. It works fine but the dockers using br2 do not get router through the VPN as if they were on Host network. I've managed to just manually give IPs to each container and then add those IPs to the pfSense alias and it works fine. I'm n
  16. Shorter version: I currently have docker assigned to br2, which has its own NIC and I manually designate IP addresses to containers from the DHCP pool range I set in the docker settings page. If I change the network setting for br2 from IPv4 address assignment: None to IPv4 address assignment: Static will it mess up my current docker network which utilizes br2?
  17. I have been trying to eliminate call trace issues on my server and have read through lots of info on the forum. Original post After a bunch of issues I was able to get things working better. Now I have br0 up and running on one NIC and br2 running on a second NIC. br0 is the UNRAID network and I have a static IP set for it in pfSense, which is working well. Following a forum thread I set br2 up with it's IP set to none. I then set my docker network to use br2 and gave it a DHCP pool and that's working perfectly. My VMs are also on br2. I would li
  18. I see this in the log a couple times Tower kernel: bond0: the permanent HWaddr of eth0 - MAC:ADDRESS - is still in use by bond0 - set the HWaddr of eth0 to a different address to avoid conflicts
  19. After reading through a bunch of forum posts I tried putting the docker network onto its own NIC. Anytime I change the network settings I am no longer able to reach the machine over LAN. I then deleted the network.cfg and rebooted into GUI mode. I made the suggested adjustments to put docker on its own NIC and once again I lost all network connectivity. I have now adjusted eth0 to: Bonding = no, Enable bridge = yes, Bridging members of br0 = eth0. If I try and set eth0 to a static IP I lose network connectivity again. I have it set with a static IP from pf
  20. OK, I read through that post but my dockers don't have an IP address assigned to them. Mine are Host, Bridge, Proxynet (letsencrypt), and a VPN container. Could one of those networks cause the macvlan issue? Maybe it's because I have docker set to be able to communicate with the host network (Host access to custom networks)?
  21. Well, the crashes are back.... I was finally able to setup Graylog since my other syslog server (unraid) wasn't capturing the issue. I've attached the logs. The other issue is that it seems Graylog didn't export everything in the exact order that it came in. Sorry about that... This came in after rebooting the server and had it running for about an hour: May 26 19:17:08 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa0/0x69e May 26 19:17:08 Tower kernel: Code: 04 e8 56 fb ff ff 44 89 f2 44 89 ff 89 c6 41 89 c4 e8 7f f9 ff ff 48 8b 4c 24 08 84 c0 75 af
  22. I'm assuming you looked at this guide? https://kodi.wiki/view/Adding_video_sources#Adding_Remote_sources Should be the same using an UNRAID SMB share I think.
  23. Have you tried testing with iperf to see the speed between your two devices on your LAN? What OS are you transferring from? MacOS SMB over wifi has been slow for me since I was on High Sierrra. The other thing you might run into is the speed of the disks you are reading from/writing to. I've had much better luck running docker containers on the UNRAID box itself rather than using a separate box.
  24. This happens to me all the time unfortunately. Usually relaunching Finder fixes the issue and then you remount the volume(s) again.