• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About misterwiggles

  • Rank


  • Gender

Recent Profile Visitors

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

  1. Thanks. I got it working a while ago. I just followed the instructions related to the Thraxis docker and I got it working for automated downloads. I also have the Calibre docker looking at a Watch folder so I can add .epub manually. I used this when migrating my epub collection from Apple's Books app.
  2. I have an update here: Ubiquiti finally reached out to me yesterday - 3 months later - saying they are ready to follow up on this case. Given my experiences with the EXACT SAME HARDWARE RUNNING ESXi working just fine on the XG RJ45s, I agree that the issue is most likely Unraid related. So I would suggest that @jonp look into this further. I can give the Ubiquiti case manager Jon P's email and will do so. But I'm feeling a bit bad now that I gave Ubiquiti such a hard time when the culprit is Unraid's interaction with this onboard Intel NIC.
  3. Can someone with a good, solid LL workflow share how they are using LL along with Calibre? I know there is another Thraxis docker that people seem to favor for this integration. But I also see people here using what seems like a simpler method of having LL add books to a Calibre ‘Add Folder’ and then Calibre adds those new books to it’s db when it is launched. My goal is to use the Calibre features to easily side load books on my Kindle/iPad via email. I’d rather not have to manually add these new LL books to Calibre. So before I do down the path of using the Thraxis docker vs Linuxserver dock
  4. @fuzzewuzze Can you briefly write up how you got this finally working. It’s hard for those of us who follow the thread to only see “I think I have it working now” without any details on *how* you got it working. I’m just now setting up LL and want to use Calibre as well. Question for anyone: I have an existing Calibre book library on my local Mac. I would like to move all of this to my Unraid server. I already have other media automation dockers running so am familiar with that process. Want to add LL/Calibre automation. Do I just copy my existing Calibre book library (which contai
  5. I gave up. I never got it to work and Ubiquiti just never followed up on the support case I opened. I expect the core issue DOES involve the interaction between Unraid using the on-board Intel NIC and Ubiquiti switch. I ended up buying a 10G SFP+ card and putting that in my Unraid server instead. That has been rock solid since. I think those RJ45 ports on the XG do have issues with specific NICs and I've concluded that those ports, in some cases, don't provide enough power to keep the connection up. But it seems to DEFINITELY involve the Unraid driver in some weird way as I don't see the issu
  6. The reason I suspected this was an Unraid driver issue was because I had an identical Gigabyte server - same one as @slimshizn - and the onboard NIC 10GT connections dropped with the XG as well as failing to even pull an IP address during a reboot. However, I have a 2nd server with identical hardware running ESXi and that DID NOT DROP any 10G connections when connected to the UBNT XG. So @jonp I do think there is something going on with Unraid’s drivers and their interaction with the UBNT gear at 10G-T. I just couldn’t spend any more time trying to debug this and without UBNT actively engaging
  7. My update is that I ultimately installed an SFP+ card in my Unraid system and then connected that to the XG via a fiber cable. It has been rock solid since then. Not a surprise based on what I had expected and read about the flakey 10G-T ports on the XG. Disappointingly, UBNT has STILL not resolved my open support case on this despite promises that the escalation team would engage within a week. I think clearly those ports on the XG have issues with certain NICs as you suggest and it could come down to the ports not being powered properly so the connection getting dropped. I think UBNT is goin
  8. Thanks for that info. As an UPDATE: I ultimately not only changed the RSTP priorities but also put my XG as the Core root switch in my chain and moved the US-24 to hang off that. Also moved the USG connection to Port 16 on the XG. I was *sure* this would solve my issues. But it didn’t. I still got disconnects after a few hours on Port 13. Have been running Port 13 at 1g for the last 4 days and there have been no issues. I’m frustrated with Ubiquiti support as I have an open case on this issue and they escalated for me to a higher support team. But I’ve heard nothing since then and
  9. @Benson UBNT support asked me to try setting the RSTP priority values differently on my switches. My three switches all had the same priority value. They asked me to try setting my 'root bridge' switch - the US-24 in my case - to lower value than the XG and then to reboot both switches. I will update here once I've retested as to whether this resolve my issue. Again, posting all this here in case it some day helps someone else in same situation.
  10. I was told on the UBNT forums that any hardware post revision 6 has been 'fixed' as to the port issues. My hw revision is 13 so I was assuming the problem was elsewhere and likely firmware related. But will try to get an answer out of UBNT today and swap the switch regardless in hopes of solving this. But would really like to know why I only see this issue with Unraid vs ESXi.
  11. Yes @Benson. I've had no issues since setting Port 13 on the XG to 1g. What can we conclude from this? That this is DEFINITELY a XG issue, i.e. it won't hold the network connection when the port is set for 10g? There were a LOT of these reported issues with this switch during it's beta phase. Apparently UBNT worked on the issues with firmware updates. A lot of the issues were specific to Intel NICs which is what I have. However, I have another server running ESXi which is the exact same hardware and it doesn't lose the connection to the XG at 10g. So I keep concluding that there is something r
  12. @Benson Do you have any updates in your testing? My update is that after switching IP addresses to set the static IP from the Unifi side of things, I managed to have my network connections stay up for 12 hours straight until I had to leave for the weekend. I also left my Unraid log open on screen to see if I could see anything happening once I got back. Unfortunately, some time over Friday-Sunday my connection dropped again and there was nothing new in the log file. My next step is to set Port 13 on the XG to 1g and isolate whether it is the XG itself that is losing the IP/routing
  13. Getting desperate now to narrow issue. I had my Unraid server set to static IP and Gateway in Unraid itself. I noticed on the UBNT side that when I tried to set a static address on the router/USG for this server the Unifi Controller would give me an error. And it seems odd to me that my network drops appear to be the router losing the IP and route to my server on the XG but not the network link connection itself. So last night I set Unraid to dynamic IP and gateway and it pulled a new IP address while still connected to the XG. I then went back to the Unifi side and this time it let me set the
  14. So I only need spanning tree (RSTP or STP) when bridging the two physical NICs? In other words, I can turn OFF any spanning tree on this switch if I am not bridging two or more NICs. Still using Docker and VMs on Unraid so not clear if I need STP or not. Ready to try anything to further isolate issue and pass on to UBNT team.
  15. NEW NEW UPDATE: A complete reboot of the Unraid server DID NOT result is an accessible server after reboot. Something going on with the switch and its interaction with Unraid. Just not clear on the root cause. But I would have expected a reboot to reset the networking issues whatever they are and start the whole process all over again. My guess is that I will need to shutdown the server again, move the network connection back to the 1g switch, boot and things will be normal again. Just not at 10g, which is the whole reason I bought this server and switch. Ugh.