![](http://content.invisioncic.com/u329766/set_resources_34/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
coolguy1771
-
Posts
17 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by coolguy1771
-
-
Just now, Opawesome said:
Then I guess it is time to investigate here :
Good luck !
Agreed. Thank you so much.
-
Just now, Opawesome said:
I meant let me know if removing Wireguard fixes the issue
Unless you meant that < traceroute -i wg0 8.8.8.8 > and < traceroute -i wg1 8.8.8.8 > work ?
Turning off the wireguard tunnels made everything start working.
-
1
-
-
Just now, Opawesome said:
Please let me know
when i specified an interface they pings and trace routes worked. When i tried the same commands without specifying and interface it failed.
-
1
-
-
Just now, Opawesome said:
It enforces the use of the specified interface.
I am by no means an expert, but in your position, I would try maybe to temporarily remove Wireguard (which I nderstand to be the wg0 and wg1 interfaces) to see if that fixes the issue.
Because for what I can see, your Unraid machine can communicate to the internet when we force it to use the br0 or br0.400 interfaces.
(but this is without any warranty !
)
I think you're right.
-
1
-
-
-
-
1 minute ago, Opawesome said:
These 2 last commands are different
I'm an idiot and misread your reply.
-
3 minutes ago, Opawesome said:
And what about:
-
< traceroute -i br0 8.8.8.8 > and
-
< traceroute -i br0.400 8.8.8.8 > ?
That's what i was referring to.
-
-
23 minutes ago, Opawesome said:
Sorry, I see you have vlan and other stuff which I don't know how to trouble shoot.
While you wait for some more expert fellow user to help you, maybe you could also try to:
- ping your gateway and other local devices from the Unraid terminal to see what happens
- < sudo ping -I br0 8.8.8.8 > and
- < sudo ping -I br0.400 8.8.8.8 >
Best,
OP
All of those pings work. This made me really confused.
-
5 minutes ago, Opawesome said:
Then I think you should post:
- the diagnostics files
- copy of the unraid routing table
- and maybe the result you get if you issue command < traceroute 8.8.8.8 > in your Unraid terminal
Best
OP
Attached are the things you requested.
-
9 minutes ago, Opawesome said:
Well, if you can't ping anything, even from your router, then it is unlikely an Unraid issue I am afraid, and rather a networking issue that you will need to fix with your router.
Best
OP
The issue is only on unraid. The rest of my network is unaffected.
-
7 hours ago, Opawesome said:
Hi,
I would personally start troubleshooting by trying to ping GitHub.com from the router WAN interface. If successful, then I would try pinging GitHub.com from the unraid console.
If pinging GitHub.com fails but pinging to its resolved IP works, then this is indeed a DNS resolver issue. You can find ones DNS's IPs with online DNS resolvers you will find on Google.
I hope this helps.
Best,
OP
I can’t ping GitHub or anything other than my internal network. I’ve tired 1.1.1.1, 8.8.8.8, 9.9.9.9 and the backups for those as well.
-
about a week ago i started receiving an error in the fix common problems plugin where it was saying.
Unable to communicate with GitHub.com
I've tried changing DNS servers, IP address, everything I could think of and nothing has worked. I would really appreciate some help with fixing this issue.
-
9 hours ago, JorgeB said:
Try uninstalling the docker folder plugin.
That worked, Thank you.
-
1
-
-
Diagnostic File attached. I've got no idea on this one, it pops when I try to go to the VMs page.
DNS Issue
in General Support
Posted
This problem has now been solved.