FSA down? (Client unable to connect)

[CRGaming]

Pops up a message "It looks like you are either not connected to the internet or our homepage is currently down!"

[AdySmith]

I simply cannot launch the client.

Completed a flight, set the park brake and the client crashed.

OK I thought, i'll restore things, but the client won't launch.

Let's have a quick look in the debug file - Notepad crashes if I try to open it.

Ideas?

[joefremont]

Not sure what to tell you ady, see several flights recorded in the last few minutes so the system is running. you might try deleting the fsairlines.ini file in your Documents/FSAirlines folder

[AdySmith]

Tried that, launched the client but when I entered my login details it froze and eventually crashed.

Tried reinstalling, same result!

[joefremont]

Have you tried the beta client? If it gives you the same result email me your fsairlines.ini file and the debug file, will PM you instructions.

[AdySmith]

I've emailed them to you

Ady

[sirthomas]

Hello, since yesterday have exactly the same problem with AdySmith. The client froze and crashed

[joefremont]

We have had a few pilots report similar incidents over the last couple days but so far I have no explanation. Nothing has really changed in the last week to explain it, we did move to the new server early this month but its been working well for a few weeks so that does not seam to explain it. I have tried to reproduce it but have not been able to.

I will make a test client with some additional logging that I will make available by Saturday that we can test with so we can get to the bottom of this problem.

[joefremont]

I have seen reports from two pilots so far. From what i have seen in the logs the very first call from the client is getting blocked, and its one of the most basic calls just trying to get the version numbers of the current stable and beta clients. No funny characters or large blocks of text to overflow the buffers, about the simplest call the client makes. The most likely cause is Firewall software on the pilots computers or possibly by there ISP, but I have not confirmed that yet, the number of flights is down a little since Thursday compared to the week before but it is within the normal range of variation so can't draw any concussions except that most pilots are not having this problem.

So if your having this trouble add us (https://www.fsairlines.net) to your white list for your security software and see if it helps.

It is possible that it may have something to do with our SSL certificate which uses the 'letsencrypt' ' service and it auto-renewed itself on 2023-09-26 right about when the problems started. It was also shared between beta.fsairlines.net and maybe some firewalls are detecting something odd about it. But I made a change so that beta and www no longer share a SSL certificate and regenerated one for www, lets see if it makes a difference.

[sirthomas]

Good morning, unfortunately the problem still exists, the firewall looks ok, FSA is on whitelist but still can't connect. The problem starts suddenly, a day before i did a flight with no problem at all and the next day just i couldn't connect.

Thank you for your efforts

[joefremont]

The mystery of this problem continues. I have about a dozen pilots contact me saying they have had this problem. But at the same time, in the last 48 hours 541 distinct pilots have recorded 1251 flights so the problem is not wide spread, and despite my best efforts have not been able to reproduce the problem. The client is talking to the same server your web browser is so may not be a general blocking of the website, but I wonder if something is blocking our client app. Some things to try.

Try white listing our client app, The client on most systems will be in "C:\Program Files (x86)\FSAirlines\FSAirlines.exe", go into your security software and make sure that app has access to make http and https calls.

https://support.microsoft.com/en-us/win ... 01afe13b26

I do have a relay setup on the system the forum runs in and the client can be set to talk to it rather than the main website directly, to enable using your favorite text editor open "Documents\FSAirlines\fsairlines.ini" and look for [settings] under that add a line that reads

AltServer = 1

Restart your client after you make that change. On the login page it should show "connecting to https://relay.fsairlines.net" on the bottom of the page.

Making this topic global until we get to the bottom of this.

[joefremont]

Update, at least one pilot indicated that adding AltServer value to there fsairlines.ini file worked for them. Not a full solution but maybe a work around for now.

[AdySmith]

My fsairlines.ini file was completely blank (0 bytes)

However I added that line (including spaces) but the problem still exists.

Client still shows as connecting to the normal server not the relay server

[Buschpilot]

Hello Joe,

I have two PC running.
One PC with Win7 32bit...
On this PC all additional programs (Weather, Narvigation, FSAirline-Client) are running.
Everything is connected via Simconnect to the Flusi-PC.
Weather and Plan-G run without problems.
Only the FSA client makes the same problems on this PC.

With my other PC with WIN10 64bit there are no problems with FSAirline-Client.
The Flusi is also installed on this PC.

On the Win 7 32bit PC I have completely reinstalled the FSA-Client 2.5.1.
The FSA-Client has only created an empty fsairlines.ini.
In this empty ini file I made the following entry:
[settings]
AltServer = 1
Saved everything and restarted the FSA client.
Now the FSA client connects to https://relay.fsairlines.net" and works again.

Thank you for your work!

[sirthomas]

I did it and works for me, now the client connects to https://relay.fsairlines.net and until now works fine.

Thank you!