I am trying to set up the Web API for the FMC.
AAO 4.51b09 MSFS 2020 PMDG 777f
What I have done:
1. copied the folder: pmdg777fmc” into the folder \Documents\LorbyAxisAndOhs Files\WebPages\
2: Adjusted the file 777_Options.ini. I am sure that I have done it correctly, then with another application the FMC runs without problems on another computer. https://flightsim.to/file/77669/pmdg-77w-cdu
3: Added the two scripts as Aircraft automated scripts to the template.
 “PMDG-PMDG_777_CDU” one shot
“PMDG-PMDG_777_Data” repeating
Since it does not work, I looked at the scripts and both have the same text:
(PMDG:reserved[0])
Is that correct????
4: Host firewall adjusted
The program C:\Program Files\LorbyAxisAndOhs_MSFS\LorbyAxisAndOhs_MSFS.exe
is enabled for inbound and outbound rules for private and domain for UDP and TCP for all ports.

5. I tried to call local with Edge

http://localhost:43380/webapi/pmdg777fmc/left.html
http://localhost:43380/webapi/pmdg777fmc/right.html
http://localhost:43380/webapi/pmdg777fmc/center.html

Nevertheless, it does not even work on the local PC.
What is still missing for success?
Thanks for your help
Stefan

Translated with DeepL.com (free version)

On 1/3/2025 at 9:07 AM, Stefan01 said:

Nevertheless, it does not even work on the local PC.

Most likely, the F has a different API and the WebFMC cannot work. It was made for the initial 777 release. I will see if I can check it out over the weekend.

On 1/3/2025 at 9:07 AM, Stefan01 said:

Is that correct????

Yes. With theses scripts the contents are irrelevant. It is only the script name that just has to be configured as an Autoscript.

Edited January 5, 20251 yr by Lorby_SI

On 1/3/2025 at 9:07 AM, Stefan01 said:

What is still missing for success?

Don't know, sorry. I've tested it on my computer, the WebFMC is working fine here (for the 777F) without any changes.

1. Firewall: it is not enough to allow access for the program itself. You have to create incoming and outgoing rules specifically for the TCP Port 43380. With an incoming request, the firewall doesn't know and doesn't care what app is listening for it. You have to tell the firewall that receiving data on that port is OK in general.

2. localhost: on some computers, "localhost" doesn't work (because of a mismatche hosts file). You may have to use an actual IP address instead (127.0.0.1 or whatever "real" local IP your computer has - check on the cmd with "ipconfig")

Edited January 5, 20251 yr by Lorby_SI

Thank you very much for your help. The error was elsewhere. I also have the Elgato Streamdeck plugin. The port must be 9080/9081 for this to run without errors.
This means that the ports for the fippanel and the hooks are also 9080/9081.
I don't think it is possible to assign different ports. I am now running the FMC on a second PC by calling port 9080 instead of 43380 as described in the readme.txt for the FMC.
Thanks again Stefan

15 minutes ago, Stefan01 said:

Thank you very much for your help. The error was elsewhere. I also have the Elgato Streamdeck plugin. The port must be 9080/9081 for this to run without errors.
This means that the ports for the fippanel and the hooks are also 9080/9081.
I don't think it is possible to assign different ports. I am now running the FMC on a second PC by calling port 9080 instead of 43380 as described in the readme.txt for the FMC.
Thanks again Stefan

The WebAPI port can be changed in the AAO "Tools" menu, both for AAO itself and the SD plugin too. The StreamDeck software must be shut down for this (right click the SD icon in the system tray, bottom right of your screen, the option to terminate the StreamDeck software is in there).
9080 is the old logic, now 43380 is the default port for AAO. To many other software product use 9080 too, and there were always conflicts. Not so with 43380...