• Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About xorinzor

  • Rank


  • Gender
  • URL
  • Location
    the Netherlands

Recent Profile Visitors

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

  1. Disabling and re-enabling doesn't work for me, I've done that in the past for some other reasons, but this container always has had the same problem. Still unresolved, I don't believe it has anything to do with the custom networks since all of my other containers work with custom networks just fine.
  2. Can you post the output of the commands that have been mentioned in previous replies? Could help establish a baseline. I think everyone here is roughly having the same problem.
  3. I recently got a managed switch and have since been playing around with it, configuring different vlans to make my network more secure. For example, the management interfaces from the router and managed switch can only be accessed via the management vlan. This vlan doesn't have internet access however (by design). If I configure the untagged vlan from unraid to be this management vlan, and have another vlan for docker I'd be able to restrict access to the unraid interface too. If I make the management-vlan the untagged vlan for unraid (ie: it's main eth0 interface)
  4. This is a support topic for Wireguard, I'm afraid your issue lies somewhere else. I don't even think it's related to Unraid, you could create a topic here, or maybe some other forum.
  5. Hm, even those settings are the same as mine. Did you get to test a connection to wireguard via the local network?
  6. What output do you get on the command below? sysctl -a | grep -e "ipv4.ip_" -e "wg0" Don't be suprised, the output is quite a lot
  7. can you connect from the local network to the server? This would further narrow down if it's related to the port forwarding, or something else. EDIT: Can you also put a screenshot of your routing table here? (viewable at /Settings/NetworkSettings)
  8. It's shown as up, but not what service is running (checked using nmap) https://suip.biz/?act=nmap
  9. I've learned over time never to trust output of applications themselves, but just to get it from the source. It can't hurt to check netstat just in case
  10. Interesting, though you can kinda confirm it by checking the output of netstat -atunl | grep 51820
  11. That has been tested already, it's closed. We're just trying to figure out why at this point. Could be completely unrelated to the port forwarding if there's no service listening to the port.
  12. I've had no issues with my intel xeon upon rebooting. Wasn't aware of any issues with intel either. Did you notice my edit? If you checked the port I don't think that's the issue, but it can't hurt to make sure. Let us know what the logging tells you (do another port check to trigger it, as well as try to connect with a wireguard client)
  13. Do you have a static IP configured for your unraid server? Are other ports on your unraid server reachable? What if you enable the logging in your router for that port, does that give you any indications? I use unraid 6.8.2 too, but it works fine for me. EDIT: the blurred local endpoint, just to make sure, isn't set to Unraids local IP, but your external IP. Correct? In which case, did your external IP perhaps change?