crow0827

Thank you for your support. I configured as below. DCS server/nginx server: 192.xxx.xxx.100 (example) DCS port 8089: webgui port nginx port 80: hosting C:¥nginx/html/index.html (copied webgui into C:¥nginx/html) webgui app.js: ip: 192.xxx.xxx.100 and port: 8088 are configured in js/app.js nginx port 8088: proxy pass to 127.0.0.1:8089 I checked that the nginx server is working properly and is able to display the webgui page. But, some of 404 errors are displayed on F12 Developper tool. errors are below. &ACTION=GetJSONData: This item is not displayed when accessed from shared webgui folder. encryptedRequest: Requested URL is different from when accessed from shared webgui folder. from hosted page: Requested URL = http://192.xxx.xxx.100/:8088/encryptedRequest from shared webgui folder: Requested URL = http://192.xxx.xxx.100:8088/encryptedRequest I'm in the dark as to whether this difference in behavior is affecting or whether the configuration file is incorrect. nginx configuration file: deleted I found my mistake. I had rewritten 127.0.0.1 to the server address, but not localhost. It is cause of error. After rewrite app.js, web hosted webgui is working well. I know I'm repeating myself, but thanks for your support!!! Note: procedure Rewrite "127.0.0.1" and "localhost" to DCS server address in the "app.js". Rewrite "8088" to reverse proxy port in the "app.js". Launch nginx with webgui and reverse proxy(transport to DCS webgui port).

I kind of know what to do. But I didn't know how to write the correct configuration file. I need to study up a little.

Maverick I tested the procedure. It works well. Thanks. With hosting web server, I could not understand detail of the operation. Is it completely different from the reverse proxy method? I just hosted the webgui folder and the javascript seems to be working, but it looks the same as when I don't use reverse proxy.

Thanks for the quick reply. If it goes through easily with a reverse proxy, I'd be willing to give it a try. It is too much of a burden on the server host if other members cannot access the server management screen when they want to run a server in the community. I don't want to allow the RDP of the server machine to all community members.

I tried it with disabled firewall. Server did not respond. Could you try it?

Is there any plan to implement local network remote control function? It's too annoying to have to go all the way to the official DCS website to control dedicated server from the remote.

Hi, HB. Could you update the roadmap? You said you wanted to build a helicopter before, but I just want to know if you have any plans yet. Thanks

ebay is the easiest way to get it. I have an F-16 throttle, but I'm hesitant to take out the transducer. I used OTTO P1 when I converted my Stick, but Magnetic Hold Switch will be sold out soon if we don't have good timing. Everyone wants a new one, so it's a battle to get one. Please let me know if you do anything interesting again!

Wow... That's really crazy nice... I can't tell you how impressed I am. I've seen people use Honeywell ET switches and Transducers, but I've never seen anyone do it this thoroughly. I'd say it's almost real. I'm also curious where you got the parts from. Ebay?

Thanks.

Yes, I tested on both version.

Requested to upload replay. https://youtu.be/9-GxHyztDlE FM Homing Light was turned on again after changing switch position from TR to OFF. If you change switch as following flow, FM Homing Light will be off as intended. 1. Initial Mode Selector Switch(MSS) Position - OFF(work as intended) 2. MSS Position - TR (work as intended) 3. MSS Position - DF, FM Homing Light ON(work as intended) 4. MSS Position - TR, FM Homing Light OFF(work as intended) 5. MSS Position - OFF, FM Homing Light ON(work as NOT intended) 6. MSS Position - TR, FM Homing Light ON(work as NOT intended) continue... Executing procedure No.3 and 4 is only to power off Direction Finder Function.

Situation: 1. All power(GEN L/R, INVTR, BAT) is ON. 2. VHF FM Mode Selector Switch Position - ADF. 3. On the NMSP, FM Light is ON. 4. Change VHF FM Mode Selector Switch Position to OFF 5. On the NMSP, FM Light is still ON. (This is bug.) with VHF FM Mode Selector Switch Position - OFF, VHF FM Transceiver Should be powered off. There's no way that feature will work. Physically impossible. I've reported this to the ED a few times and they've all ignored me, but what the hell. It's been neglected for 6 months, and I hope they fix it soon, because if the ADF is still functioning, the FD won't show up even if you want to use the ILS, or something systemic happens.

Hi, All, ED, 3rd Party Developers. I have noticed a few things and would like to share them with you. Did you know that the control panel backlighting in general is regulated by the Military Standard as to what should and should not be illuminated? According to MIL-P-7788E, the connector for powering the light source for the backlight is marked with a white cross. I've checked on more than one plane, and the white cross are illuminated. I haven't seen the actual panel, so I can't say for sure, but I'd like you to check it out a bit. As far as I know, even non-military aircraft are designed to this standard, because the panels I've seen in real life didn't have illuminated cross.

Dear ED Beta testers. As same as below link and bug of this thread, current A-10C may have some bugs with unexpected procedure. Please check not only normal procedure, but also other procedure. link Thanks