chris111486

Make sure that if you have a modem from your ISP that you enable bridge mode. I had an issue a while back where I replaced my router. And my wireguard worked for all of about 2 weeks. Well come to find out my ISP pushed out an update to their network which in turn reverted modem back to default settings. So I needed to go back in to enable bridge mode and it worked like a charm.

I only have 1 NIC connected to my home network. So are you saying that there could be an issue with the 2nd NIC on the blade I'm running my unraid server on then?

Last week after figuring out my issue i had been having with wireguard i went to test it out and make sure i could connect to server from an outside network. As I was in the process of doing this i tried to stream a media file and it stopped transmitting after a while. I went into the system and watch the data on the graph in unraid for network traffic and saw that it nose dived down to 0 and ran at 0. I disconnected it and tried again and it worked but then stopped again. When i went into network settings on the server and also on the main dashboard i see now it says eth 1 interface port is down. Any ideas on how to resolve this issue? its telling me to check cable but i thought eth1 is a virtual network point on the server. I have attaches some screen captures so you can see what I'm seeing. Thanks

Bump

A few months ago i replaced my router. I then also proceeded to update unpaid OS to its current version at that time. I tried to use WireGuard after all this ands it wasn’t working. I then got busy with home and work and wasn’t able to get back around to troubleshooting the issue. Now i have been able to get back trying to troubleshoot the issue and this is where i stand. Long story short i went back to a clean slate. Remade my domain on DDNS deleted the original tunnel created when i had WireGuard working. Followed steps on page 1 and it’s not a complex network and to no avail still unable to connect to server from external means. When i go to do my port forwarding on router it doesn’t seem like it works. And even the tunnel screen shows that it still doesn’t see port forwarding connected via the server. I also tried upnp connection and nothing worked while trying to connect that way either. After each change made on the router i did perform a reboot since i wasn’t sure if it would need a reboot for change to take, because i know that was 1 of my issues the first time i tried setting it up in the beginning a few years back. I go into the logs on both unraid server and router and don’t see the IP of server. I also did a trace route to see if my ISP is using CGNAT. And am not 100% sure if that may be my issue. I have attached photos to see if maybe anybody else sees something i missed. And I understand the photo of tunnel setup screen says forward port but that is already set in my routers port forwarding. Any ideas are greatly appreciated.

Bump

Tried to access my server a couple weeks back on home network and it threw a DNS error. Didn’t think anything about it and shrugged it off. Yesterday i go to try again and still getting same error. I have tried numerous steps like flushing DNS cache, release and renew IP, change DNS server. I also restarted the server via CTRL+Alt+Del thinking maybe it could’ve been something on the server causing it. After server rebooted itself and all other steps bore still getting the same issue except now I have lost access to home bridge amongst other things i had running on the server. I can’t even connect to my raid array. Has anyone ever seen this or have any ideas of what i can try in order to be able to connect to server again. Thank you in advance.

I will look into the updating process to go from the version I am at now to whatever the newest is. If it seems like too much of a task I may have to wait until after the holidays and then try. But I will check the first 2 posts again in the thread and make sure I didn’t miss anything. You don’t think I would have to go back to nothing and re set up everything again do you? I mean with WireGuard. Not server. 😂 😂

The answer to this question may be buried somewhere in previous pages. But i have spent some time trying to figure out why I can’t use wire guard anymore just because i have changed out my router. It was setup and working for the last couple years, and now that i have changed router I can’t seem to remotely connect to it anymore. I have asked a few friends who i have created peers for to see if they can connect to it and same thing. No connection. I can’t even ping them once they have it setup and active on their device. Could there be something so small I’m forgetting to do? I’m still running unraid 6.9.2 which I doubt is the reason it isn’t working. After i setup port forwarding on new router i rebooted router to make sure changes took affect. I put in my sub domain from duck dns instead of the endpoint IP to try and get it to connect. I put my isp IP as the local end point and nothing. I did read something somewhere that if router has UPnP then unraid would detect that, but mine is on and server didn’t detect it. Any ideas would be greatly appreciated. Thanks

So I just upgraded one of my 5tb array drives on server and after bringing it back up and starting parity sync the VM now won’t start. When I try and watch the VM start with built in VNC before switching over to Splashtop to access I just get the dots across center of screen. Even after parity sync completed it still didn’t work. I’m using Mac in a box for my Mac vm. I watched @SpaceInvaderOne video on the docker and tried to reinstall via docker and still nothing. Does anyone possibly have any ideas as to what It could possibly be or something I should look for. The VM has been up and running for almost 60 days with no problems until this swap of drives. Thanks.

Ok. Thanks.

Attached is the ZIP. diagnostics-20200619-0740.zip

Is there a specific folder from diagnostics i should upload?

So I just upgraded one of my 5tb array drives on server and after bringing it back up and starting parity sync the VM now won’t start. When I try and watch the VM start with built in VNC before switching over to Splashtop to access I just get the dots across center of screen. Even after parity sync completed it still didn’t work. I’m using Mac in a box for my Mac vm. I watched @SpaceInvaderOne video on the docker and tried to reinstall via docker and still nothing. Does anyone possibly have any ideas as to what It could possibly be or something I should look for. The VM has been up and running for almost 60 days with no problems until this swap of drives. Thanks.

Thanks.