SyberSin

Hello, I have a custom network setup that all my dockers are running on with nginx proxy manager forwarding to them via container names instead of ip address. This works for 90% of my containers except for a few. I get bad gateway if I use the container name. Why is that? and is there a way to fix it? They are all on the same custom network. So far, Freescout, Vikunja, and Element will not allow me to use the container name.

That does seem very similar to what I'm experiencing. So I changed my binhex deluge to use libtorrentv1 and I already notice the Unraid dashboard feels more responsive. We will see if that was the issue or not. Thank you

It looks like it might be an issue with the network drivers? also my bios is slightly out of date but the latest version doesn't list any changes made that seem significant? I'm on bios 1003: https://www.asus.com/us/motherboards-components/motherboards/workstation/pro-ws-wrx80e-sage-se-wifi/helpdesk_bios/?model2Name=Pro-WS-WRX80E-SAGE-SE-WIFI Should I upgrade to 1201? I also found the intel drivers for what's on my board (Intel® X550-AT2 dual 10Gb Ethernet) for Linux here: https://www.intel.com/content/www/us/en/products/sku/84329/intel-ethernet-controller-x550at2/downloads.html but there is so many options I'm not sure which on is correct, or even if I need to / should? The options for linux are: Complete Driver Pack All OS 8/25/2023 Ethernet Connections Boot Util, Preboot Images, and EFI Drivers 8/7/2023 PCIe 10 Gigabit Connections under Linux 8/7/2023 Virtual Function Driver for 10 Gigabit Connections under Linux 8/7/2023 Non-Volatile Memory Update Utility 3/29/2022 Plus some of these have 10 different Linux options to download when I click on them. If I do, which one and how would I go about installing on unraid?

Okay it finally did it again, here is the syslog and new diagnostics. It was last seen on my network at 10/1/2023 8:10AM pacific standard. server-diagnostics-20231001-1456.zip syslog

Okay, yeah I just set it to use the flash option instead. Do I need to reboot for it to take effect? as the docs mention it captures everything from the start of the boot process. So when I need to shutdown the server again and pull the plug, do I extract the logs first before I plug the server back in? Or would you like me to plug the server back in, reboot then extract the logs?

Thank you for your help, I just setup the syslog server as follows: local syslog server rotation: 100mb number of files: 4 Should that be fine? and do I need to reboot unraid or keep it running?

Hello, I'm having a serious issue with my unraid server. I would greatly appreciate if somebody could help me. Please read, as this is a unique issue that I have not seen anywhere else on the forums. I have searched and read almost every post on the forums and other places online with no solution. My unraid server keeps disappearing from my network, which is happening every day now. I cannot connect to it via ssh, gui, local network, or by my direct 10gb connection. It's as if the eth ports are not working (although lights are blinking on them and my unifi dream machine.) The server shows as offline in my dream machine as well. I also cannot boot into safe mode or into the gui mode with a monitor attached, the output hangs if I try and it never comes online, cannot even reach the console. I have reset the network, and the server with no luck. When this happens, I essentially loose the whole server. Now here is where it gets stranger. I posted about this issue once a while back with no responses: The solution I found in that post still 'works'. If I completely unplug the server from power, plug it back in, it boots and shows on my network just fine. I don't even need to replace the network config files. Just unplug. But unlike the first time, after the server is running for about 24 hours, it will disappear from my network again, and all the symptoms above come back. I need to shut down the server with the power button and pull the plug again, reboot and Ill have access again and it shows backup on my network like nothing is wrong. I first had that issue 7 months ago, and the server has been running constantly since then with no issues. All of a sudden, this problem is happening every morning now. So my solution is obviously not ideal and this is making my server unusable. I do not think this is related but I did make a few changes before this started happening. One of my pool drives died, so I replaced that drive and I upgraded my parity drives, I rebuilt the parity, checked the parity and everything was fine. 24 hours later this problem started happening again. Luckly, I tried my 'solution' and got back my server, so I immediately upgrade to 6.12.4 (from 6.11) hoping that would work. This morning the issue happened again. In my other post I mentioned what I originally changed that appears to have started this whole issue. (Setting up a 10gb connection between my computer and server following space invaders guide.) attached is the diagnostics. server-diagnostics-20230927-1216.zip

Okay I believe I found the solution. For those in the future that may come across this problem: 1. Pull the plug. Shutting down is not enough, physically pull the plug from the power supply. (It appears something was saved on the hardware that prevented the eth ports from resetting to their previous state.) 2. Create a backup of your flash drive, and replaced the network.cfg and network-rules.cfg (Luckly I had a backup of these two files to use. Also make sure to use the same exact flash drive. Do not use another drive with your backup files as this caused the boot to hang.)

I just tried booting with a flash backup I have from 2 days ago, same result, cannot access the server. The only difference is the backup flash is not even allow me to boot into gui mode, it hangs when it's done printing to the screen, as if I choose normal boot. Its as if the changes I made broke the on board ethernet ports?? The router is not seeing the server even with my backup which had no issues.

Hello, I followed the below space invader one guide to setup a 10GB connection between my server and another computer and it completely broke my gui access. I changed the interface eth1 ip address to static at 10.10.10.26 and enabled bridging, clicked apply and restarted. Now I cannot access the server over the network (not even in gui mode) and I cannot even ssh into it anymore. It's like it does not exist on my network. I removed the flash drive and deleted network.cfg and it did nothing, I still cannot access my server. My router does not even show the server is connected any more. I reset my router and removed the dhcp reservation I had set for the server. I tried connecting both ethernet ports to my switch as well. Nothing is working. I waited 15 minutes after rebooting the server to make sure it was completely booted up. Please any help to get my server back would be greatly appreciated, I am out of ideas and have tried everything I have found on the forums.

I'm not sure what was wrong, I couldn't get this to work all day yesterday, woke up this morning and now it works. Thank you again.

Hello, thank you for this container. I cannot seem to get this to work with nginx proxy manager though. All my other containers are working fine except this one. I'm assuming there is something that needs to be changed in the docker to allow this to proxy correctly? Any idea of want needs to be done?