ljm42

Administrators
  • Posts

    3143
  • Joined

  • Last visited

  • Days Won

    13

ljm42 last won the day on May 19

ljm42 had the most liked content!

Converted

  • Gender
    Undisclosed
  • Personal Text
    the answer to life, the universe, and everything

Recent Profile Visitors

30099 profile views

ljm42's Achievements

Proficient

Proficient (10/14)

607

Reputation

38

Community Answers

  1. Instructions for configuring remote access are here: https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29 There is likely an issue with your port forward in step 10. You need to configure that on your router, outside of the Unraid interface. Step 11 is how to test it.
  2. When the My Servers plugin is uninstalled you will not be able to sign in to Unraid.net, but in Unraid 6.10+ there will still be a menu in the upper right corner of the page to manage your Unraid license. If you think a plugin is not completely uninstalled, feel free to reboot. Unraid is installed from scratch every reboot so any plugins not listed on the plugins page will not be installed after a reboot.
  3. Sorry for the trouble, you should be able to provision again. We are looking into ways of making sure this remains stable.
  4. The built-in WireGuard implementation does not store anything in appdata. Maybe you have a WireGuard docker? I'd recommend asking in that docker's support thread. If you can't find that, ask in General Support. Be sure to upload your diagnostics (from Tools -> Diagnostics)
  5. This is one of the more complex things to do and it sounds like you got pretty far, nice! In the OP there is a link to this post, have you seen it? https://forums.unraid.net/topic/88906-lan-to-lan-wireguard/
  6. The "protocol" should be "TCP" rather than "Both". But I doubt that would prevent you from connecting. I'd recommend contacting your ISP, it seems like they may be blocking you from accepting incoming connections.
  7. There are still two nics specified in the config/network.cfg file on the flash drive. The system is using the first one (192.168.10.97) but I don't think there is a way to remove the second (192.168.0.102) one via the webgui. The safest would be to delete the config/network.cfg file from the flash drive and reboot. The system will generate a new one automatically and give it a DHCP address. If you then want to go to Settings -> Network Settings and manually assign the desired IP you can. Or... we don't usually recommend this, but you could try manually editing the config/network.cfg file and removing these lines from the end, then reboot: IFNAME[1]="eth1" DESCRIPTION[1]="HP Micro Eth 1" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.0.102" NETMASK[1]="255.255.255.0" SYSNICS="2" If you run into any trouble rebooting, plug a keyboard/monitor directly into the server. You will be able to see the new IP address right before the login prompt. You can also login to the shell and run 'diagnostics' to place a new diagnostics.zip file on the flash drive.
  8. If you are still seeing GLIBC errors in your log I would recommend a reboot. See https://forums.unraid.net/topic/112073-my-servers-releases/#comment-1154449
  9. Not a bug, but a technical limitation. Support for this hidden setting is unlikely to return.
  10. Looks like an issue related to jumbo frames. Do you see a measurable improvement with jumbo frames enabled? My understanding is that it makes very little difference, but complicates everything. If you don't absolutely need it, I'd recommend reverting back to the default MTU of 1500 (on Settings -> Network Settings)
  11. Likely unrelated. It sounds like your system does not reboot reliably. If it happens again you could try fully powering the system off and then powering it back on, if that works then there may be a "fast boot" option you need to disable in the bios. To further troubleshoot that I'd recommend a new thread in the General Support area (along with diagnostics from Tools -> Diagnostics) so that more people see it, as this thread is in the My Servers area of the forum. Note that safe mode does not fix anything on its own, it simply boots the system without any plugins. So booting into safe mode and immediately rebooting normally is basically the same as just rebooting normally.
  12. Your http port is set to 9080, but your ssl port is set to 90443. 90443 is too large, so nginx is unable to start. Edit the config/ident.cfg file on the flash drive and change: PORTSSL="90443" to something else, perhaps: PORTSSL="9443" Then run: /etc/rc.d/rc.nginx reload
  13. There were a lot of good improvements to SSL support in Unraid 6.10, unfortunately the hidden BIND_MGT setting was a casualty. I deleted that gist as it was from 2019. If you want to see the current rc.nginx, look on your server at /etc/rc.d/rc.ngxinx
  14. After booting in gui mode you should be able to open a terminal/shell. Type "diagnostics" and note the filename it created. Then grab that file off your flash drive and attach to your next post in this thread.