Simbrief connection error

[mwyatt]

Hi, I have not been able to connect to Simbrief for some time (maybe over a year !!).
All entries are as they should be, Alias name etc and nickname all correct. Ignore Time is "ticked".
Addon mananger folder excluded in anti virus (Defender)
Couatl64_MSFS.exe also excluded as a file
Flightplan is active as far as I know.
Error on screen is SIMBRIEF EXCEPTION ERROR1 = HTTP RESPONSE CODE SAID ERROR.
I would like to know what is preventing the connection to Simbrief, all seems to work well without it, but it would be nice !!
Everything else works as intended as far as I know !!
Martin.

[virtuali]

That message can come for many reasons, none of them of course being GSX issues:

- Your Simbrief Alias (username) is wrong, check it, double check it and triple check it. If your username was created a while ago and it contains spaces, it won't work. Simbrief now doesn't allow to create usernames with spaces in it, but if yours was created before they enforced this rule, you need to change it.

- The last dispatched flight might have expired. They expire in a few days.

- Simbrief might really be down. They did have some shortages in the past days.

- A firewall (not antivirus) is preventing GSX from reaching Simbrief. Configure it to be sure the Couatl engine has outside online access.

[wigerup]

Same problem here.
How do I see if the Couati engine is working??

[Murf]

So what does this mean.... and once again how to I fix it???

[pete_auau]

so no advice  given  2  post aboves  yours  worked at all?

[virtuali]

So what does this mean.... and once again how to I fix it???

Does your Simbrief username contain spaces?

If yes, change it and, in fact, Simbrief doesn't allow to create username with spaces inside anymore (because they cause these kind of problems, not just to GSX), but if you created it before they started to enforce creation with usernames with no spaces, it might still contain spaces, so you'll have to edit it and remove any spaces or other non-printable characters from it.

And be absolutely sure you are using your Username (also known as Alias), which is a text string, and NOT your User ID, which is a number.

[Murf]

Nope no spaces in it and my firewall allows couatl Scripting Engine..... so I am lost, and I am sorry to say, but I am about to just remove GSX.
If it's not going to function properly it's not worth having.

[virtuali]

Nope no spaces in it and my firewall allows couatl Scripting Engine..... so I am lost, and I am sorry to say, but I am about to just remove GSX. If it's not going to function properly it's not worth having.

As I've said, it's either a firewall or a space in your username, or you having confused the alias and used the userid instead. It must the ALIAS, it cannot contain spaces and you must be sure your firewall is not blocking the Couatl engine.

Of course, if you posted a startup log, I would be able to tell you exactly what your problem is.

[Murf]

Nope no spaces in it and my firewall allows couatl Scripting Engine..... so I am lost, and I am sorry to say, but I am about to just remove GSX. If it's not going to function properly it's not worth having.

As I've said, it's either a firewall or a space in your username, or you having confused the alias and used the userid instead. It must the ALIAS, it cannot contain spaces and you must be sure your firewall is not blocking the Couatl engine.

Of course, if you posted a startup log, I would be able to tell you exactly what your problem is.

I say again my last... Nope no spaces in it and my firewall allows couatl Scripting Engine..... That's pretty straight forward!!!

Now there could perhaps be something in my firewall I need to configure that I am not aware of... all I know is that it DOES allow the couatl Scripting Engine.

If you give me a step by step of what YOU need to be done in the firewall and how to do it, we MIGHT actually get this solved. As I have said before I am NOT software or windows firewall literate and need it spelled out on how to do it... otherwise it's like trying to shoot a fast moving rabbit in the dark with a sleeping mask on with a bow and arrow!!!!

Yes.... I am getting a bit frustrated.... I can't fully use a product I paid good money for!!! Which makes it useless!!

[virtuali]

I say again my last... Nope no spaces in it and my firewall allows couatl Scripting Engine..... That's pretty straight forward!!!

It won't be the first time somebody is sure of some setting, but it wasn't so. Also, I repeated it, because I suspected you might have not read my reply entirely because, it ended with:

Of course, if you posted a startup log, I would be able to tell you exactly what your problem is.

Since you haven't posted your startup log, you might as well missed the suggestion about checking the username. I'm awaiting your log which, as I've said, will clarlfy what the problem really is.

If you don't know how to create a log, it's on Page 34 of the GSX Manual.

[Murf]

I say again my last... Nope no spaces in it and my firewall allows couatl Scripting Engine..... That's pretty straight forward!!!

It won't be the first time somebody is sure of some setting, but it wasn't so. Also, I repeated it, because I suspected you might have not read my reply entirely because, it ended with:

Of course, if you posted a startup log, I would be able to tell you exactly what your problem is.

Since you haven't posted your startup log, you might as well missed the suggestion about checking the username. I'm awaiting your log which, as I've said, will clarlfy what the problem really is.

If you don't know how to create a log, it's on Page 34 of the GSX Manual.

You are correct... I didn't see you request the log.... Here it is!!

[virtuali]

You are correct... I didn't see you request the log.... Here it is!!

Your log shows you have a very old version of the Couatl engine: 5302, while the current build is 5381 so, before doing anything else, be sure you run the FSDT Updater to get the current version and then, if you still have the same problem, post a new log with the current version.

[Murf]

ok... I ran the live update... reran MSFS... still the same!!!

I have obviously downloaded the log before, but I don't remember where it is and can't find it to give you a more current one.

Update: Found it.... Please find the log attached

[virtuali]

Your error is caused by your Simbrief username having a space in it.

Simbrief must have realized this would cause issues so now, if you try to create a new account with a space in it, will not allow it, but existing usernames that were created before Simbrief made this change, still contain the space.

If you can change your Alias (username = alias ) to not have spaces, it will work.

[Murf]

I have attached a screenshot of my account... I don't see any spaces... do you?? It's been this way since I have had it.