[hellbinder]

The Web Entry opens for anonymous users but as soon as they hit submit the following error page opens up Fatal error: Maximum execution time of 40 seconds exceeded in C:\Program Files\ProcessMaker\apps\processmaker\shared\workflow_data\sites\workflow\public\5037536624c3588c4871256001528966\wsClient.php on line 122.

Anyone got any idea what might be wrong?
If any additional information is needed, I'll procure it on demand.
Thanks in advance,
--Jerome--

[roelveldhuizen]

What happens if you raise the maximum execution time?

You can do this by editing your php.ini or use in the script 'ini_set('max_execution_time', 300);' in your case changing the php.ini is probably the easiest.

[amosbatto]

Jerome,
Open your php.ini file and look for the following line like:
max_execution_time = 40 ; Maximum execution time of each script, in seconds
Increase the maximum number of seconds and then restart the Apache web server. (If you don't know how to restart Apache, just reboot.)

Depending on your system you can find the php.ini file in a number of different places.

Debian/Ubuntu:
/etc/php5/apache2/php.ini
or
/etc/php5/cgi/php.ini

Red Hat/Cent OS/Fedora:
/etc/php.ini

Windows:
C:\Program Files\ProcessMaker\php\php.ini

[hellbinder]

I'm now getting the message:
Bad Request
This web entry should be regenerated, please contact to your system administrator.

After a restart of the computer I got this:
Could not connect to host
This web entry should be regenerated, please contact to your system administrator.

[hellbinder]

bump, anyone got any idea of what the problem could be?

[fisher]

Encountered the same problem:
Could not connect to host

This web entry should be regenerated, please contact to your system administrator.

The task assigned to an SQL user... no idea why it is not working. Any suggestions?
Version 3.1.3-community.

[amosbatto]

What happens if you delete the web entry and then recreate it? What happens if you create a new user in PM and assign that user to the web entry?

Also try clearing the ProcessMaker cache by going to Admin > Clear Cache.

[fisher]

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.