Exactly the same for me mate,
Exactly the same for me mate,
It's been a LONG time since I decided to check on LFS and was hoping to update my 6Q to whatever the latest is and waste some time over Xmas I don't usually have. Logitech Wheel is out of the loft and ready.
I get "The program was unable to connect to the master server... etc..."
I also have ping and traceroutes as above that perfectly show that the server is there and I have no problems with connectivity. ie. master.liveforspeed.net [188.122.74.153]
I paid for this BTW, this isn't just the demo.
(ETA: Maybe if I just delete my LFS and download the demo and upgrade it that will work?)
I get "The program was unable to connect to the master server... etc..."
I also have ping and traceroutes as above that perfectly show that the server is there and I have no problems with connectivity. ie. master.liveforspeed.net [188.122.74.153]
I paid for this BTW, this isn't just the demo.
(ETA: Maybe if I just delete my LFS and download the demo and upgrade it that will work?)
I got the same message earlier today. But after a few tries it started working for some reason.
You should try again when you can.
I tried a few times and then just completely installed the latest demo version (6U) and then unlocked it without a problem.
A 500-600MB download is nothing these days, unlike when that was considered huge and patches were necessary back then!
A 500-600MB download is nothing these days, unlike when that was considered huge and patches were necessary back then!
Hello!
I'm having master server connection issue, I can't caoonect to master server.
Here's my results:
From "ping master.liveforspeed.net":
Reply from 188.122.74.153: bytes=32 time=63ms TTL=47
Reply from 188.122.74.153: bytes=32 time=53ms TTL=47
Reply from 188.122.74.153: bytes=32 time=55ms TTL=47
after this moment cmd app switches off...
And from "tracert master.liveforspeed.net":
1 <1 ms <1 ms <1 ms flybox.home [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
after this moment cmd app switches off...
I'm having master server connection issue, I can't caoonect to master server.
Here's my results:
From "ping master.liveforspeed.net":
Reply from 188.122.74.153: bytes=32 time=63ms TTL=47
Reply from 188.122.74.153: bytes=32 time=53ms TTL=47
Reply from 188.122.74.153: bytes=32 time=55ms TTL=47
after this moment cmd app switches off...
And from "tracert master.liveforspeed.net":
1 <1 ms <1 ms <1 ms flybox.home [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
after this moment cmd app switches off...
I am also currently having issues connecting to the master server from the LFS Client?
Stuck on waiting for reply from master server and then LFS stops responding.
Stuck on waiting for reply from master server and then LFS stops responding.
my results, doesnt work on 0.6R, but it works on the newest version.
test 1:
Pinging master.liveforspeed.net [188.122.74.153] with 32 bytes of data:
Reply from 188.122.74.153: bytes=32 time=64ms TTL=45
Reply from 188.122.74.153: bytes=32 time=58ms TTL=45
Reply from 188.122.74.153: bytes=32 time=61ms TTL=45
Reply from 188.122.74.153: bytes=32 time=58ms TTL=45
Ping statistics for 188.122.74.153:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 64ms, Average = 60ms
test 2:
Tracing route to master.liveforspeed.net [188.122.74.153]
over a maximum of 30 hops:
1 1 ms 3 ms 2 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 22 ms 31 ms 36 ms bks4-dci-1.vrf1257-520.bundle-ether3s148.tele2.net [130.244.87.177]
4 18 ms 29 ms 38 ms bks-pe-1.bundle-ether60.tele2.net [130.244.49.45]
5 28 ms 17 ms 29 ms bks-fgw-1.ae2-202.tele2.net [213.100.43.18]
6 31 ms 29 ms 27 ms c213-100-43-17.cust.tele2.se [213.100.43.17]
7 40 ms 32 ms 32 ms bks4-core-1.bundle-ether60.tele2.net [130.244.49.44]
8 28 ms 31 ms 28 ms tvt-core-1.bundle-ether40.tele2.net [130.244.49.160]
9 28 ms 29 ms 33 ms te0-3-1-2.rcr51.rix01.atlas.cogentco.com [149.14.74.49]
10 38 ms 31 ms 47 ms be3735.ccr22.sto03.atlas.cogentco.com [154.54.59.57]
11 51 ms 56 ms 63 ms be2282.ccr42.ham01.atlas.cogentco.com [154.54.72.105]
12 62 ms 59 ms 64 ms be2816.ccr42.ams03.atlas.cogentco.com [154.54.38.209]
13 81 ms 72 ms 59 ms be3385.rcr21.rtm01.atlas.cogentco.com [154.54.58.198]
14 64 ms 60 ms 77 ms be3133.nr21.b025461-0.rtm01.atlas.cogentco.com [154.25.10.186]
15 87 ms * 69 ms interactive-3d.demarc.cogentco.com [149.6.110.22]
16 65 ms 58 ms 73 ms 109.200.218.91
17 56 ms 76 ms 61 ms s6.lfs.net [188.122.74.153]
check 2: didn't have master.liveforspeed.net in it
check 3: firewall is allowing connection
test 1:
Pinging master.liveforspeed.net [188.122.74.153] with 32 bytes of data:
Reply from 188.122.74.153: bytes=32 time=64ms TTL=45
Reply from 188.122.74.153: bytes=32 time=58ms TTL=45
Reply from 188.122.74.153: bytes=32 time=61ms TTL=45
Reply from 188.122.74.153: bytes=32 time=58ms TTL=45
Ping statistics for 188.122.74.153:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 64ms, Average = 60ms
test 2:
Tracing route to master.liveforspeed.net [188.122.74.153]
over a maximum of 30 hops:
1 1 ms 3 ms 2 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 22 ms 31 ms 36 ms bks4-dci-1.vrf1257-520.bundle-ether3s148.tele2.net [130.244.87.177]
4 18 ms 29 ms 38 ms bks-pe-1.bundle-ether60.tele2.net [130.244.49.45]
5 28 ms 17 ms 29 ms bks-fgw-1.ae2-202.tele2.net [213.100.43.18]
6 31 ms 29 ms 27 ms c213-100-43-17.cust.tele2.se [213.100.43.17]
7 40 ms 32 ms 32 ms bks4-core-1.bundle-ether60.tele2.net [130.244.49.44]
8 28 ms 31 ms 28 ms tvt-core-1.bundle-ether40.tele2.net [130.244.49.160]
9 28 ms 29 ms 33 ms te0-3-1-2.rcr51.rix01.atlas.cogentco.com [149.14.74.49]
10 38 ms 31 ms 47 ms be3735.ccr22.sto03.atlas.cogentco.com [154.54.59.57]
11 51 ms 56 ms 63 ms be2282.ccr42.ham01.atlas.cogentco.com [154.54.72.105]
12 62 ms 59 ms 64 ms be2816.ccr42.ams03.atlas.cogentco.com [154.54.38.209]
13 81 ms 72 ms 59 ms be3385.rcr21.rtm01.atlas.cogentco.com [154.54.58.198]
14 64 ms 60 ms 77 ms be3133.nr21.b025461-0.rtm01.atlas.cogentco.com [154.25.10.186]
15 87 ms * 69 ms interactive-3d.demarc.cogentco.com [149.6.110.22]
16 65 ms 58 ms 73 ms 109.200.218.91
17 56 ms 76 ms 61 ms s6.lfs.net [188.122.74.153]
check 2: didn't have master.liveforspeed.net in it
check 3: firewall is allowing connection
my test results":
Microsoft Windows [Version 10.0.19043.1466]
(c) Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\twanb>oing for master.liveforspeed.net
'oing' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\twanb>ping for master.liveforspeed.net
Ping request could not find host for. Please check the name and try again.
C:\Users\twanb>tracert master.liveforspeed.net
Tracing route to master.liveforspeed.net [188.122.74.158]
over a maximum of 30 hops:
1 3 ms 4 ms 3 ms mijnmodem.kpn.home [192.168.2.254]
2 7 ms 6 ms 17 ms 195-190-228-160.fixed.kpn.net [195.190.228.160]
3 * * * Request timed out.
4 * * * Request timed out.
5 24 ms 25 ms 21 ms nlrtm1-rt004i.i3d.net [109.200.218.247]
6 8 ms 9 ms 16 ms s11.lfs.net [188.122.74.158]
Trace complete.
C:\Users\twanb>
Microsoft Windows [Version 10.0.19043.1466]
(c) Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\twanb>oing for master.liveforspeed.net
'oing' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\twanb>ping for master.liveforspeed.net
Ping request could not find host for. Please check the name and try again.
C:\Users\twanb>tracert master.liveforspeed.net
Tracing route to master.liveforspeed.net [188.122.74.158]
over a maximum of 30 hops:
1 3 ms 4 ms 3 ms mijnmodem.kpn.home [192.168.2.254]
2 7 ms 6 ms 17 ms 195-190-228-160.fixed.kpn.net [195.190.228.160]
3 * * * Request timed out.
4 * * * Request timed out.
5 24 ms 25 ms 21 ms nlrtm1-rt004i.i3d.net [109.200.218.247]
6 8 ms 9 ms 16 ms s11.lfs.net [188.122.74.158]
Trace complete.
C:\Users\twanb>
Master server is down. DDOS again?
Nothing major, except a short surge happened tonight, the master server was probably still fine. You can always check here: https://www.lfs.net/online/activity
The master server itself isn't down, but the mod hosting system is definitely borked a bit. Mods that are uploaded/updated today can't be driven because of the "Your vehicle is not known to this host" message. It may be a global thing, but I've only tested it on "Just A Ride" so far
it is happening again this evening
dont know this is the right place to say it but nowadays its back. im often facing with slow loading, "the site is not safe" or "500 internal server error" thing. dont know anyone have those that often but its almost everyday routine for me. its started to become annoying at some point.
It's not just you.
For the last few days our site has been attacked repeatedly. It is a DDoS attack, meaning millions of packets, with unidentifiable origin, are thrown at our server every second. We have taken various steps to reduce the effect and there is more to do. Contrary to what some people believe, there is no single, catch-all fix that can be applied to prevent all DDoS attacks.
I would be grateful if people will not start talking about it, expressing frustration or giving us advice on how to fix it. Victor is fully aware.
Thank you.
For the last few days our site has been attacked repeatedly. It is a DDoS attack, meaning millions of packets, with unidentifiable origin, are thrown at our server every second. We have taken various steps to reduce the effect and there is more to do. Contrary to what some people believe, there is no single, catch-all fix that can be applied to prevent all DDoS attacks.
I would be grateful if people will not start talking about it, expressing frustration or giving us advice on how to fix it. Victor is fully aware.
Thank you.
no puedo crear un servidor nuevo en linea
tengo un problema y es que no puedo crear ningun servidor en lfs, y no no hay un servidor abierto previamente y aun asi me dice que tengo un host abierto, ya descarte que tenga otro lfs, todo esto ocurrio en el dia que se cayeron los servidores de lfs hace unas semanas,
resultados de pruebas
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Users\Cesar> ping master.liveforspeed.net
Haciendo ping a master.liveforspeed.net [188.122.74.151] con 32 bytes de datos:
Respuesta desde 188.122.74.151: bytes=32 tiempo=220ms TTL=50
Respuesta desde 188.122.74.151: bytes=32 tiempo=207ms TTL=50
Respuesta desde 188.122.74.151: bytes=32 tiempo=210ms TTL=50
Respuesta desde 188.122.74.151: bytes=32 tiempo=219ms TTL=50
Estadísticas de ping para 188.122.74.151:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 207ms, Máximo = 220ms, Media = 214ms
C:\Users\Cesar> tracert master.liveforspeed.net
Traza a la dirección master.liveforspeed.net [188.122.74.151]
sobre un máximo de 30 saltos:
1 3 ms 1 ms 2 ms 192.168.1.1
2 36 ms 36 ms 36 ms 190.39.160.1
3 40 ms 35 ms 42 ms 172.26.25.246
4 * * * Tiempo de espera agotado para esta solicitud.
5 77 ms 104 ms 115 ms 10.82.1.33
6 44 ms 44 ms 43 ms 10.82.1.14
7 101 ms 101 ms 108 ms ae14-502.miami16.mia.seabone.net [195.22.199.108
]
8 * * * Tiempo de espera agotado para esta solicitud.
9 94 ms 101 ms 91 ms be3087.ccr22.mia01.atlas.cogentco.com [154.54.88
.233]
10 118 ms 108 ms 102 ms be3483.ccr42.atl01.atlas.cogentco.com [154.54.28
.49]
11 * 118 ms 118 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24
.221]
12 141 ms 124 ms 167 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40
.109]
13 194 ms 193 ms 204 ms be2490.ccr42.lon13.atlas.cogentco.com [154.54.42
.86]
14 200 ms 213 ms 236 ms be3383.rcr21.rtm01.atlas.cogentco.com [154.54.57
.254]
15 247 ms 298 ms 303 ms be3133.nr21.b025461-0.rtm01.atlas.cogentco.com [
154.25.10.186]
16 203 ms 204 ms 221 ms 149.6.111.58
17 693 ms 292 ms 263 ms nlrtm1-rt016i.i3d.net [109.200.219.45]
18 * * * Tiempo de espera agotado para esta solicitud.
19 205 ms 203 ms 226 ms s4.lfs.net [188.122.74.151]
Traza completa.
creo que todo esta bien ya que en si puedo unirme a cualquier servidor mas no crear uno, espero que me ayuden a solucionar esto
resultados de pruebas
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Users\Cesar> ping master.liveforspeed.net
Haciendo ping a master.liveforspeed.net [188.122.74.151] con 32 bytes de datos:
Respuesta desde 188.122.74.151: bytes=32 tiempo=220ms TTL=50
Respuesta desde 188.122.74.151: bytes=32 tiempo=207ms TTL=50
Respuesta desde 188.122.74.151: bytes=32 tiempo=210ms TTL=50
Respuesta desde 188.122.74.151: bytes=32 tiempo=219ms TTL=50
Estadísticas de ping para 188.122.74.151:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 207ms, Máximo = 220ms, Media = 214ms
C:\Users\Cesar> tracert master.liveforspeed.net
Traza a la dirección master.liveforspeed.net [188.122.74.151]
sobre un máximo de 30 saltos:
1 3 ms 1 ms 2 ms 192.168.1.1
2 36 ms 36 ms 36 ms 190.39.160.1
3 40 ms 35 ms 42 ms 172.26.25.246
4 * * * Tiempo de espera agotado para esta solicitud.
5 77 ms 104 ms 115 ms 10.82.1.33
6 44 ms 44 ms 43 ms 10.82.1.14
7 101 ms 101 ms 108 ms ae14-502.miami16.mia.seabone.net [195.22.199.108
]
8 * * * Tiempo de espera agotado para esta solicitud.
9 94 ms 101 ms 91 ms be3087.ccr22.mia01.atlas.cogentco.com [154.54.88
.233]
10 118 ms 108 ms 102 ms be3483.ccr42.atl01.atlas.cogentco.com [154.54.28
.49]
11 * 118 ms 118 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24
.221]
12 141 ms 124 ms 167 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40
.109]
13 194 ms 193 ms 204 ms be2490.ccr42.lon13.atlas.cogentco.com [154.54.42
.86]
14 200 ms 213 ms 236 ms be3383.rcr21.rtm01.atlas.cogentco.com [154.54.57
.254]
15 247 ms 298 ms 303 ms be3133.nr21.b025461-0.rtm01.atlas.cogentco.com [
154.25.10.186]
16 203 ms 204 ms 221 ms 149.6.111.58
17 693 ms 292 ms 263 ms nlrtm1-rt016i.i3d.net [109.200.219.45]
18 * * * Tiempo de espera agotado para esta solicitud.
19 205 ms 203 ms 226 ms s4.lfs.net [188.122.74.151]
Traza completa.
creo que todo esta bien ya que en si puedo unirme a cualquier servidor mas no crear uno, espero que me ayuden a solucionar esto
Hello, I have deleted your host instance so hopefully you can start one now.
Master server connection problems?
(416 posts, started )
FGED GREDG RDFGDR GSFDG