Server not seen on global server
-
Add your server manually here (with a dns name if you dont have static ip): http://www.flserver.de/add_server.php
And integrate this into your mod: http://www.freelancerserver.de/download/flgls_workaround_v10.zip
-
Interesting. My router firewall identifies that website as having malicious content and won’t allow me to connect.
Regarding the suggestions W0dk4 provided, that’s been done on FLU for years.
I refreshed the IP by re-adding the server using the link you provided and the workaround patch is already integrated into the mod. Players are still reporting though that they can’t see the server on the list.
-
The mod is to be run on the client side, correct? The only thing that needs to be done on the server side is to change the list server setting in freelancer.ini.
Right?
-
The FLU server is in the global server list and has been resubmitted just in case.
Players have the correct files incorporated and they’re still unable to see the server.
Anything else to try?
-
Does anyone else see an IP of 5.9.69.107 in their firewall? It traces back to germany and it’s connected to my server even though nobody else is on.
That wouldn’t be the global server, would it?
The server doesn’t even show up in my list now even though it’s connected to my LAN.
Edit: All right, here’s some more info.
If I use the fldirectip.hta option to log in I can see the server in my list when I use the WAN IP address but I can’t log in. The server waits and then says that a connection couldn’t be made.
If I use the same option but use the LAN IP address (192.168..) I can see the server in my list and I can log in.
If I attempt to log in normally using the regular shortcut and global server to access the server it doesn’t even show up in the list.
I’m thinking FLU is under attack again. Nothing has changed in the mod or on the server. The server is running and works as evidenced by the fact that I can log in using the local IP address and the fldirectip.hta login method. Something is preventing it from showing up on the global server list and something is preventing the server from being accessed using normal methods.
There are no changes to the router, the modem, the firewall either on the router or on the server.
Any ideas?
Oh, and we’re still failing to make connection to the list server.
-
gun.fllistserver.com is 5.9.69.107
Some routers refuse to pass connections from LAN hosts to the routers WAN IP addresses…mine is one of them. If i want to verify a port is properly opened on my WAN IP I need to scan from a external IP address. -
So, that IP address is legit.
Still at a loss as to why FLU does not show up on the list.
Players report this started about a month ago. Interestingly enough I never had a problem being connected directly with the LAN and others have been able to log in as well but it’s worse now.
Nobody has logged in since I logged out last night and that’s unusual.
I’ll review all firewall settings again when I get home tonight but it’s a mystery.
-
robocop wrote:
So, that IP address is legit.Still at a loss as to why FLU does not show up on the list.
Players report this started about a month ago. Interestingly enough I never had a problem being connected directly with the LAN and others have been able to log in as well but it’s worse now.
Nobody has logged in since I logged out last night and that’s unusual.
I’ll review all firewall settings again when I get home tonight but it’s a mystery.
Sorry, it seems like there is a problem on our end (updating http://www.freelancerserver.de/serverips.txt does not seem working). So it is not your fault, the GLS workaround does not currently work as it is intended to be. I’ll try to fix it ASAP
Players report this started about a month ago.
On 1.10. (a month ago), the HDD of our server at freelancerserver.de blew up and apparently Crazy was also running the GLS on it. So at least rest assured, this is apparently the problem. I’ll try to get the update process of the serverip file running again, then the workaround should actually work again.
-
Oh thank God!
I very much appreciate your work on this W, it’s largely due to your efforts and others like Crazy, DownUnder, Adoxa, and too many others to list that FL is still up and running today.
R
-
It showed up briefly but when I attempted to connect I got that wait for it dialogue and then got dropped due to unable to make connection to server.
After refreshing the list the server no longer appears.
-
Problem appears to be resolved.
Thanks W0dk4.
-
Hey everyone, long time, no see
So our (very mildly alive) server has moved to a different address and that’s when i noticed that GLS is still down?
http://www.flserver.de/add_server.php is also not working, tried adding both fl.elite-games.ru and 195.42.181.130.
-
No connection from either server or client for me.
The server is hosted in a datacenter in another city too so the only common thing between it and my client are Russian IPs. Could those be blocked on GLS’s side by any chance? Because i don’t see another reason why it would be inaccessible. -
Can’t see a reason why GLS would block it. It’s more likely a router issue as i said. I sorted my own server out not long ago, and i had issues connecting to it, to find it was my isp’s router blocking it it. Once i turned that into a bridge and used my own router behind it by creating a static ip, all was well. What operating system you using? Do you have Adoxa’s exe hack for FL barring ipv6 searches?
-
I’m certain it’s not the router or anything on my end. I have three very different machines in very different locations all unable to reach UDP port 2300 for gun.fllistserver.com.
This is on my work Linux machine:
Endeavour ~ # nping --udp -p 2300 gun.fllistserver.com Starting Nping 0.7.01 ( https://nmap.org/nping ) at 2018-01-13 08:25 MSK SENT (0.0378s) UDP 10.*.*.*:53 > 5.9.69.107:2300 ttl=64 id=12481 iplen=28 RCVD (0.2234s) ICMP [5.9.69.107 > 10.*.*.* Port unreachable (type=3/code=3) ] IP [ttl=50 id=54616 iplen=56 ]
This is on my home machine (Windows 8.1 IPv6 disabled) trying to connect with FL itself:
https://bsox.s3.amazonaws.com/ShareX/2018/01/2018-01-13_08-30-52.pngMy server is colocated in a proper datacenter in a different city, so while i didn’t run wireshark on it, i’m pretty sure the problem isn’t there or in its (datacenters) routers.
The only, and i mean only, common thing between these three is that they’re all located in Russia. I could try making an Amazon EC2 instance and trying from there but i think i gathered enough info already.
-
Based on that info, looks like things are fine on your end, especially the 8.1 machine. I mean that shows your internal IP and external which if the router wasn’t configured properly would show another internal port.
I just find it odd that Russian IP’s would be banned. I don’t see how GLS would do that. I mean if i want to ban anyone i do it through the FL server software i use called Flac, could do it on the router as well if i wanted. GLS doesn’t stop those IP’s from coming in, I stop them. Has to be another explanation
-
Not really. Starport has been attacked repeatedly over the years by very specific IP ranges and we’ve been tempted to block Russian and Chinese IPs since that would’ve nixed 99% of them. We ended up not doing it and getting some DDoS protection, but I don’t know if Crazy could actually implement that with the GLS since it’s not just a website.
It’s possible IP ranges have been banned on the GLS because of that. You’ll have to hope Crazy sees this and answers you.
-
Guys, the GLS has been down since “Last Global Server Contact: 10/1/2017 4:20:14 AM CE(S)T”
–> http://www.flserver.de/topservers.htm
I tested the ip on the-starport.net and it seems reachable. I re-added your server via http://www.flserver.de/add_server.php
Let’s see if it gets picked up. Maybe you added the server while it was offline - in this case, the server does not get added to the database.