Chrome refuses connect with local host

[pck42]

As Requested, could you please send me a screenshot of what the WebDisplay looks like when up and runnin.
Happy New Year!
pck42

[pointy56]

Firstly, you will find a screenshot of how Web Display looks when it first starts up in Appendix D of the User Manual.
As it's a web server the display is the same whether you access it directly from a browser, or via the MSFS Toolbar Add-On.

Coming back to the problem that you are having, your latest screenshots clearly show the cause:
Web Display tries to open a log file in it's home folder and this is being trapped by Windows UAC as it regards it as a protected folder.
It is possible that this issue has been caused by changes introduced by a Windows upgrade.

Did you install PF3 as 'Administrator'? Installing as Administrator should avoid this problem.
Open the FS_Addons folder in file Explorer, right-click on the PF3 folder and select the Security tab; click on the Advanced button - who is the Owner?
Perhaps you could upload a screenshot of that window.

In the meantime I will see if I am able to reproduce the problem that you are having.

Thanks,
Martin

[pck42]

Hi Martin, attached screen shot shows I am the owner of PF3 and I am also the owner of PF3 Web Display. As far as installing PF3 as administrator, can't swear to that. Of course I could reinstall PF3 (UGH).
pck42

[pointy56]

I think that I'm getting closer to understanding the problem that you're having - it does seem to be affected by UAC and Administrator privileges.
I need to investigate further and will come back to you as soon as I have more news.

Regards,
Martin

[pointy56]

OK, I finally found time to take a more in-depth look at this.

The only way that I can find to avoid multiple UAC pop-ups when starting PF3 is to run PF3 as Administrator.
If you do that, then you will get a single UAC pop-up (for PF3 itself), but none for other programs (WX, PF3-Updater, PF3WebDisplay, etc.).
Unfortunately I cannot find an alternative solution; these programs require Admin privileges because of restrictions that Windows imposes
on accessing resources that they need to use - writing files to a folder or opening a socket for a web server, for example.

What I'm still not sure about is if an update to Windows 11 has in some way affected the way that UAC handling works.

Anyway, hopefully this explains the situation and provides you with an acceptable solution.

Regards,
Martin