- Tue Apr 04, 2017 4:11 am
#790098
I have created a brand new process, did not help. Cleared cache (both pm and browser, deleted cookies, etc.)
The pm server is behind a proxy. The pm server itself also running on ssl, the proxy passes the https traffic to the pm server.
Usually I configure my backend servers to run on http only and the proxy server does the https - http translation but some apps really dislike this. The pm for example fails to load the designer, unless the backend server running on ssl too.
To test the wdsl I went to the ...en/neoclassic/setup/webServices url, changed the settings to https, and was able to log in and run the tests, so I assume the wsdl/soap itself is supposed to work.
I did tcpdump on the client side, and it looks the client is talking https only. I double check the traffic, but it takes some time.
Meanwhile I have captured a packet which is going from the backend server (appserver) address to the proxy server external address (ie. like 10.10.10.10 to 123.45.67.89) to the 8081 port which is weird because no 8081 port configured in our pm app/webserver (it was, but I have changed this for testing).
Yeah. Ricocheting the port 8081 into the appserver (behind the proxy) via ssl (i.e. https) did help and now the webentry is working. It looks it is mandatory to have the 8081 port directed to the appserver regardless the other traffic. (Appserver is the server running the pm, behind the proxy). Not sure if it is intentional, probably I have missed a step. And I not allowed to run the processmaker on port other than 80 or 443.