FSDreamTeam forum

Products Support => GSX Support MSFS => Topic started by: Frabarba on March 09, 2025, 11:37:26 pm

Title: can't connect to simbrief
Post by: Frabarba on March 09, 2025, 11:37:26 pm
When i start a flight a red message appears saying "can't connect to simbrief", i tried reinserting the alias multiple times but it doesn't work also by changing it in simbrief settings
Title: Re: can't connect to simbrief
Post by: Wise87 on March 10, 2025, 03:48:59 am
Same here. Started after latest update for me.
Title: Re: can't connect to simbrief
Post by: virtuali on March 10, 2025, 01:33:45 pm
GSX can connect with Simbrief just fine (I just tried it now) so no, the latest update hasn't changed anything. The most common reasons for that error are:

- Your username is wrong or not set. username means Alias NOT Pilot ID, so it's a string, not a number

- Your flightplan on Simbrief has expired.

- Your firewall/antivirus is preventing the Couatl engine to go online.
Title: Re: can't connect to simbrief
Post by: Wise87 on March 10, 2025, 03:16:36 pm
GSX can connect with Simbrief just fine (I just tried it now) so no, the latest update hasn't changed anything. The most common reasons for that error are:

- Your username is wrong or not set. username means Alias NOT Pilot ID, so it's a string, not a number

- Your flightplan on Simbrief has expired.

- Your firewall/antivirus is preventing the Couatl engine to go online.

- I'm using my user name. Again, Simbrief worked fine until I updated GSX.
- I had just created the Simbrief flightplan so it wasn't even 10 minutes old. My aircraft imported it just fine.
- My firewall settings haven't changed since prior to the GSX update and my AV which is the Windows Defender has GSX and Virtuali exemption set.
Title: Re: can't connect to simbrief
Post by: virtuali on March 10, 2025, 04:41:11 pm
I can only repeat and confirm, Simbrief works just fine in the current update ( as I've said, I tested before posting, to be sure ). Check again all the things I said to check, which are the only ones that could possible cause the error discussed in this post.