Ostias_Koldo Posted October 5, 2022 Share Posted October 5, 2022 (edited) Hi! I've been using unraid for two days and today my server doesn't connect to the internet, so it doesn't have access to the Unraid server. I am using a trial key and without internet access the array is stopped. I have tried different options that I have found in the forum and none have worked for me Can someone help me? servidor-diagnostics-20221005-2138.zip Edited October 5, 2022 by Ostias_Koldo Quote Link to comment
JonathanM Posted October 5, 2022 Share Posted October 5, 2022 5 minutes ago, Ostias_Koldo said: I am using a trial key and without internet access the array is stopped Trial keys require internet access to start the array, purchased keys work without internet. Otherwise people could use a trial forever. Quote Link to comment
Ostias_Koldo Posted October 5, 2022 Author Share Posted October 5, 2022 6 minutes ago, JonathanM said: Trial keys require internet access to start the array, purchased keys work without internet. Otherwise people could use a trial forever. I understand, but I don't know why the server doesn't have internet access. Quote Link to comment
JonathanM Posted October 5, 2022 Share Posted October 5, 2022 4 minutes ago, Ostias_Koldo said: I understand, but I don't know why the server doesn't have internet access. Sorry, I misunderstood your question. Can you ping your router IP address from the console? (192.168.2.1) Quote Link to comment
Ostias_Koldo Posted October 5, 2022 Author Share Posted October 5, 2022 7 minutes ago, JonathanM said: Sorry, I misunderstood your question. Can you ping your router IP address from the console? (192.168.2.1) Sorry, i don't speak english well. My problem is that my server cannot connect to key-server. Quote PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.333 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.361 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.326 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.352 ms 64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=0.305 ms 64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=0.267 ms 64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=0.354 ms 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.356 ms 64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=0.313 ms Quote Link to comment
JonathanM Posted October 5, 2022 Share Posted October 5, 2022 Those ping results are from the Unraid terminal? Can you ping 1.1.1.1? Quote Link to comment
Ostias_Koldo Posted October 5, 2022 Author Share Posted October 5, 2022 6 minutes ago, JonathanM said: Those ping results are from the Unraid terminal? Can you ping 1.1.1.1? Yes, from unraid terminal Quote root@Servidor:~# ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. From 10.253.0.1 icmp_seq=1 Destination Host Unreachable ping: sendmsg: Destination address required From 10.253.0.1 icmp_seq=2 Destination Host Unreachable ping: sendmsg: Destination address required From 10.253.0.1 icmp_seq=3 Destination Host Unreachable ping: sendmsg: Destination address required From 10.253.0.1 icmp_seq=4 Destination Host Unreachable ping: sendmsg: Destination address required From 10.253.0.1 icmp_seq=5 Destination Host Unreachable ping: sendmsg: Destination address required From 10.253.0.1 icmp_seq=6 Destination Host Unreachable ping: sendmsg: Destination address required Quote Link to comment
JonathanM Posted October 5, 2022 Share Posted October 5, 2022 Can you ping both of those addresses from another computer connected to the same router? Quote Link to comment
Ostias_Koldo Posted October 5, 2022 Author Share Posted October 5, 2022 (edited) 13 minutes ago, JonathanM said: Can you ping both of those addresses from another computer connected to the same router? From computer with windows connected to the same router. (The result is in Spanish) And thank you very much for your help. Quote C:\Users\artur>ping 192.168.2.1 Haciendo ping a 192.168.2.1 con 32 bytes de datos: Respuesta desde 192.168.2.1: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.2.1: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.2.1: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.2.1: bytes=32 tiempo<1m TTL=64 Estadísticas de ping para 192.168.2.1: Paquetes: enviados (sent) = 4, recibidos (received) = 4, perdidos (lost) = 0 (0% perdidos), Tiempos aproximados de ida y vuelta en milisegundos: Mínimo = 0ms, Máximo = 0ms, Media = 0ms Quote C:\Users\artur>ping 1.1.1.1 Haciendo ping a 1.1.1.1 con 32 bytes de datos: Respuesta desde 1.1.1.1: bytes=32 tiempo=4ms TTL=59 Respuesta desde 1.1.1.1: bytes=32 tiempo=5ms TTL=59 Respuesta desde 1.1.1.1: bytes=32 tiempo=4ms TTL=59 Respuesta desde 1.1.1.1: bytes=32 tiempo=4ms TTL=59 Estadísticas de ping para 1.1.1.1: Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0% perdidos), Tiempos aproximados de ida y vuelta en milisegundos: Mínimo = 4ms, Máximo = 5ms, Media = 4ms Edited October 5, 2022 by Ostias_Koldo Quote Link to comment
JonathanM Posted October 5, 2022 Share Posted October 5, 2022 That doesn't make sense to me. Try unplugging and replugging the ethernet cord to the server without rebooting and see if you can get a response after it renegotiates. Quote Link to comment
Solution Ostias_Koldo Posted October 5, 2022 Author Solution Share Posted October 5, 2022 7 minutes ago, JonathanM said: That doesn't make sense to me. Try unplugging and replugging the ethernet cord to the server without rebooting and see if you can get a response after it renegotiates. Thank you very much for your hep. I have found the solution following the steps of this thread https://forums.unraid.net/topic/93527-solved-ethernet-interface-down-no-internet-accessible-on-network-683/ I have deleted the folder /config/wireguard on the flash device and now my server connect to key-server!! But I don't know why wireguard causes a failed internet connection. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.