December 9, 20205 yr 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.
December 10, 20205 yr 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
December 10, 20205 yr Author 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.
December 10, 20205 yr 51 minutes ago, coolguy1771 said: 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. 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
December 10, 20205 yr Author 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.
December 10, 20205 yr 7 minutes ago, coolguy1771 said: The issue is only on unraid. The rest of my network is unaffected. 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
December 10, 20205 yr Author 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. neon-diagnostics-20201210-0826.zip
December 10, 20205 yr 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 Edited December 10, 20205 yr by Opawesome
December 10, 20205 yr Author 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.
December 10, 20205 yr 55 minutes ago, coolguy1771 said: All of those pings work. This made me really confused. And what about: < traceroute -i br0 8.8.8.8 > and < traceroute -i br0.400 8.8.8.8 > ?
December 10, 20205 yr Author 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.
December 10, 20205 yr 1 minute ago, coolguy1771 said: That's what i was referring to. These 2 last commands are different
December 10, 20205 yr Author 1 minute ago, Opawesome said: These 2 last commands are different I'm an idiot and misread your reply. Edited December 10, 20205 yr by coolguy1771
December 10, 20205 yr 2 minutes ago, coolguy1771 said: I'm an idiot and misread your reply. That does not make one an idiot by any means
December 10, 20205 yr 1 minute ago, coolguy1771 said: I dont see the second command. It seems you issued the no. 1 twice.
December 10, 20205 yr Author Just now, Opawesome said: I dont see the second command. It seems you issued the no. 1 twice. Just realized that myself. Btw what does the -i command do?
December 10, 20205 yr 8 minutes ago, coolguy1771 said: Just realized that myself. Btw what does the -i command do? 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 if I understand correctly created the wg0 and wg1 interfaces and associated routes) 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 ! ) Edited December 10, 20205 yr by Opawesome
December 10, 20205 yr Author 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.
December 10, 20205 yr Author 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.
December 10, 20205 yr 4 minutes ago, coolguy1771 said: when i specified an interface they pings and trace routes worked. When i tried the same commands without specifying and interface it failed. 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 ? Edited December 10, 20205 yr by Opawesome
December 10, 20205 yr Author 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.
December 10, 20205 yr Author Just now, Opawesome said: Then I guess it is time to investigate here : Good luck ! Agreed. Thank you so much.
Archived
This topic is now archived and is closed to further replies.