The online racing simulator
Searching in All forums
(497 results)
Victor
Developer
Problems always arrive all at the same time. This time it was physical server problems. Should be solved now though.
Victor
Developer
Ah, nice! Thanks for letting me know.
Victor
Developer
Hm yeah, the problem is that we've locked down the server the relay ran on. Port 47474 is open for the outside to connect to, but the relay is not allowed to make outgoing connections to random ports (the hosts). This is due to us locking traffic down upstream, on a switch and not a firewall. And the switch isn't stateful, so it's not capable of discerning between incoming and outgoing connections / traffic.
Because of that, I've moved the relay to another server with some more networking freedom. The relay is now connecting to all hosts again and you can use it if you connect [your app] to isrelay.lfs.net .
BUT this brings another problem ... the LFS Remote apparently was coded to connect to "lfs.net" and not "isrelay.lfs.net". So now it's trying to connect to the wrong thing. On top of that I seem to have displaced the source code for the LFS Remote ... so now there is no way of fixing it.
Sooooo ... I guess the need for a HTML5 remote is really there now.
Unfortunately that's not a quick solution, but one that can be realised if I can find some free time (or maybe it can be a community effort? I've no problems making it an open source project ... it'll be javascript anyway, so it's open by default Smile )
Last edited by Victor, .
Victor
Developer
Is it working now for everybody?
Victor
Developer
How about now?
Victor
Developer
ouch sorry, missed this. It's running again.
Victor
Developer
Quote from BIzO :Scawen, what about adding that version in the archive downloads?

Yep, good idea. Done.
Victor
Developer
Yup. This is fixed now.
Victor
Developer
This is fixed now. Sorry for the inconvenience!
Victor
Developer
Hm missed this thread until now ... all web traffic is proxied by Cloudflare now and we do not have any particular IP blocks. So I'm not sure what's going on there.
Victor
Developer
Fixed
Victor
Developer
It's currently blocked because of server lock down. Need to find a solution to this without opening up our server again. This may mean that it will be unavailable for a while.
Victor
Developer
This seems resolved.
Victor
Developer
CoudFlare is still "Authorizing the certificate", which is why I think we get this error. I'm hoping this will resolve itself soon, if not I'll contact their support.
Victor
Developer
Hosts still online and available with new patch?
Victor
Developer
It's slightly related to the attacks, but not directly. I know what the problem is, but I haven't had the time to fix it (the post indexer isn't currently running, so new posts are not indexed).
Will find some time when the current issues have gone.
Victor
Developer
Hi,

Because you did not use the uninstaller, some registry entries have remained. That makes the installer think you still have installs there.
I think you can find the registry entries in HKEY_CURRENT_USER\Software\Live for Speed
You'll probably have multiple of those. Delete any you don't have anymore. You can see to which LFS folder they belonged by viewing all their details.

oh, yeah there may also still be one or more Windows Start Menu items that you may have to manually remove.
Victor
Developer
Indeed! Attack on the master has started again.
Victor
Developer
Quote from Kova. :So it's better to wait until that patch to be sure that attacks won't happen again? Because I had to postpone the French league's race since no one was able to join the server with these issues.

If you want to be absolutely sure there will be no hickups, then yes. So far today though, it's been quiet (knocks on wood).
Victor
Developer
ah, lfsforum.net hasn't been moved to CloudFlare and so all requests go directly to our web server, but you'll be blocked there (no direct requests allowed anymore)
can move that domain as well.
Do you still use it then? Smile
Victor
Developer
We try to null-route (plainly block) attacks, preventing servers from being drowned in traffic so that other LFS services remain available, which is why you could still ping it. But by blocking the attacks (closing ports), we do block the service behind it as well, which is why the master is / was down from time to time.
The websites now sit behind CloudFlare and the web server has been locked down with switch ACL's. This already has protected the website from attacks late last night.
The website indeed has always been available through IPv6 because the attack only occurred on IPv4.
Finally, we have a plan to better protect the master, however it will take a bit of work and a patch for LFS. Hopefully that will come later this week.
Victor
Developer
In the end it really does not matter who's doing it. And no matter what reasons they may have, we will never give in this way.

So in the coming days we will be working on more protection for our sites and services, hopefully keeping LFS in the air during hard times.
FGED GREDG RDFGDR GSFDG