Buschpilot wrote: ↑Mon Oct 02, 2023 9:01 am
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!
Interesting, wonder if this is a windows 7/32 bit issue? I am running win 11 and can't reproduce it, let me dig out an old windows 7 machine and see if it can reproduce. For those running into this problem, which OS are you using?
I've sworn an oath of solitude until the pestilence is purged from the lands.
sirthomas wrote: ↑Mon Oct 02, 2023 5:47 pm
I use a win7 home premium 64bit OS
Good to know its not a 32bit issue. I pulled out an old windows 7 system I rarely use (actually the one I use to make the release builds for the client, so its very clean) and ran the client there, reproduced the problem. So it does appear to be a windows 7 issue.
I've sworn an oath of solitude until the pestilence is purged from the lands.
I think we may have found a solution. If you were having this problem try it again, if you added "AltServer = 1" to your fsairlines.ini file then remove it before trying.
I've sworn an oath of solitude until the pestilence is purged from the lands.
Buschpilot wrote: ↑Mon Oct 02, 2023 8:41 pm
Great that this problem could be found and fixed so fast.
Some credit goes to you. Your clue that you had a win 7 machine and a win 10 machine and only win 7 had the problem sent me on the path to finding the solution.
I found a lot of help on the forum of the service where we get the SSL certificates for the website. Some of them commented on how insecure windows 7 was and this might be a good opportunity to force your users to upgrade from windows 7. you can be thankful that I am not going to do that.
But it did make me think, at some point I need to rebuild the client with more modern tools and wen we do that support for older windows and 32 bit windows may suffer, this does show me that support for windows 7 is still needed.
I've sworn an oath of solitude until the pestilence is purged from the lands.
Hello Joe,
The problem with the FSA client in connection with WIN7 seems not to be solved yet.
Just now the FSA client in connection with WIN7 worked again only with the "AltServer = 1" entry in the fsairlines.ini.
Buschpilot wrote: ↑Wed Oct 04, 2023 7:55 pm
Hello Joe,
The problem with the FSA client in connection with WIN7 seems not to be solved yet.
Just now the FSA client in connection with WIN7 worked again only with the "AltServer = 1" entry in the fsairlines.ini.
Try it again now,
I've sworn an oath of solitude until the pestilence is purged from the lands.
I need a help. someone resolved the problem, because I had the same problem and I put on the archive fsairliners.ini AltServer=1, so the client open and I put the username and password but not connect and stay in the username and password without connect.
I need a help. someone resolved the problem, because I had the same problem and I put on the archive fsairliners.ini AltServer=1, so the client open and I put the username and password but not connect and stay in the username and password without connect.
Try resetting your password to something simpler, just using letters and numbers.
I've sworn an oath of solitude until the pestilence is purged from the lands.
I need a help. someone resolved the problem, because I had the same problem and I put on the archive fsairliners.ini AltServer=1, so the client open and I put the username and password but not connect and stay in the username and password without connect.
Try resetting your password to something simpler, just using letters and numbers.
I have installed Client v2.6.0 on my computer in the path C://Program files/Lockheed Martin/Prepar3dv4/modules.
I have tried to log in and the client disappears without showing anything.
I have lost two days in this hustle and bustle because I couldn't make my flight.
Sincerely
Hebert Augusto Africano Linares
VIA002
CEO Viasa Virtual Airlines
Cap.Hebert Augusto Africano Linares
CEO Viasa Virtual Airlines