search

OCAP2 / OCAP

OCAP is an Arma 3 mission recording suite. It consists of a serverside addon and a packaged web server executable that allows for after-action review and better insight into what really happened.
Other
58 stars 14 forks source link

OCAP refusing to start and be found ingame when loaded. #1

Closed SGTdanny50567 closed 2 years ago

SGTdanny50567 commented 3 years ago

OCAP Version: v3.3.0 Server OS: Windows

Description: We recently moved to a new server box which also included a change of IP, as a consequnce I updated the OCAP mod folder, the webserver folder and the userconfig to match the new IP's. Upon lauching of the server to test the feature on the new box, the RPT says that;

Call extension 'OcapReplaySaver2' could not be loaded: The specified module could not be found.

I've updated the mod, redone all the IP's, secret passwords and tested in game and it doesn't work. It's not even outputting the logs speciffically for ocap itself into its own folders.

Steps to reproduce: Server specific, worked on the last box not on this one.

RPT File

RPT file uploaded to Google Drive RPT File

SGTdanny50567 commented 3 years ago

Resoveld this partially, upon moving the program to the new box we hadn't installed any previous Visual Studio Runtimes apart from 2019 version. I did some reading on the other forks and then assumed that we needed a older runtime, which I then installed and now the program works now.

Another problem is that the OCAP log is stating that it is curling but not exporting to the servers for viewing.

SGTdanny50567 commented 3 years ago

ocap-main.20210619_213921.log ocap-ext.20210619_213921.log

Zealot111 commented 3 years ago

@SGTdanny50567 I think that issue is pretty clear, curl (called from OcapReplaySaver2_x64.dll) cannot connect to http://127.0.0.1/data/receive.php?option=addFile which is configured in your OcapReplaySaver2.cfg.json file. You should check ocap_web, which should be running. (on the same server in this case)

indig0fox commented 3 years ago

I didn't have any luck in this iteration using localhost as the destination. I had to use the public IP (LAN IP may work if the server is hosted on a physical, local LAN) in order for the saves to function in all instances.

as @Zealot111 stated, the web server component must also be active in order to receive the data that the extension is attempting to send, and it's best to match the Listen IP of the web server component with the Destination IP of the addon/extension component. these mismatching is likely why I couldn't use localhost because the web server wasn't bound to the local interface.

Zealot111 commented 3 years ago

@indig0fox @SGTdanny50567 to setup ocap_web on localhost you need insert "listen": "127.0.0.1:80", into option.json of web_ocap and sent missions to "newUrl": "http://127.0.0.1/api/v1/operations/add",

SGTdanny50567 commented 3 years ago

@SGTdanny50567 I think that issue is pretty clear, curl (called from OcapReplaySaver2_x64.dll) cannot connect to http://127.0.0.1/data/receive.php?option=addFile which is configured in your OcapReplaySaver2.cfg.json file. You should check ocap_web, which should be running. (on the same server in this case)

Just tested this with the web server running and the IP's set all correctly to be looking on the box's specific IP with the correct ports needed, just not wanting to curl flat out.

Zealot111 commented 3 years ago

@SGTdanny50567 try in options.json setup server on all interfaces as "0.0.0.0:80" , check again firewall rules. try open ocap in browser typing 192.168.0.1 or localhost. attach your configuration files (you may omit passwords though)