Server not seen on global server
-
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.
-
-
@w0dk4 an addition!
So our angry gov blocked some ip ranges
Even apolitic sites like discoverygc.com and freelancerserver.de are blockedResult of GLS Workaround: html redirect instead of ip list at the gls_workaround.txt
Sooo…
Quickfix is replace:
[Settings] ListServerHostname=gun.fllistserver.com ServerListURL=http://freelancerserver.de/serverips.txt[Settings] ListServerHostname=gun.fllistserver.com ServerListURL=http://www.flserver.de/serverips.txtIdea is… If you want and have time to make new GLS version with mirrors, ex:
[Settings] ListServerHostname1=gun.fllistserver.com ListServerHostname2= ListServerHostname3= ServerListURL1=http://freelancerserver.de/serverips.txt ServerListURL2=http://www.flserver.de/serverips.txt ServerListURL3= -
Oh man, I feel bad for you guys… Maybe we could also add a subdomain to Starport aliasing the workaround URL as further backup.
I like the idea of mirrors, don’t know if w0d has the time to work on that though.
