blocking of the COE process disables closing of the process, failing silently

[Unsongheroes]

No description provided.

[Unsongheroes]

GetPId() and isrunning() in the COEProcess file is causing issues if the pid file is being removed or auto-generated by the OS, a check is needed and a deletion of the pid file might be a good solution.

[idhugoid]

When the pid file exists, but the COE is not responding (or was shutdown externally), the IsRunning() function succeeds when clicking on the Launch COE button in here

IsRunning() needs to go beyond asserting that the pid file works:

• It may check if the pid process is still running (not perfect if it is not responsive)
• It may check if the /version pinging of the server is good (this should always be tested...)

We should also try to delete the pid file in case we discover the server is not responding and but the file exists... Maybe issue a console error???

[Unsongheroes]

Things to try:

To block all TCP and UDP port except some port 80,443,8443 by windows defender firewall inbound and outbound rule, you could follow the steps:

1. Control panel > System and Security > Windows Firewall > Advanced settings

2. Right-click Inbound Rules and click new rule.

3. Choose Port and next.

4. Choose TCP and UDP, type 80,443,8443 in Specific local ports, and next.

5. Choose Block the connection and next.

6. Choose the profile you want to apply and next.

7. Type the name and Description you want and finish.

I think instead of doing what it says here, you can go to the same place and the rule would just block a specific port

Than you can see if you can replicate or catch an error message...