My forms are not submitting: they give a timeout error

my forms are not working anywhere on any of my multiple cm1 sites. they just give a timeout error after about 1 minute of trying to connect to the server.

Hi Cheryl,

I assume these forms have been working fine in the past, is that true? Can you link me to one of these forms so I can attempt a submission and monitor what happens with the network connection, to see if that gives us any clue as to what might be happening here? (I promise I won’t spam you too much!)

Hello Nathaniel! Yes, please go to http://cloud4causes.com/joinus/index and fill out the form for an IT Therapy Session. The other forms are still on a production server but are functioning the same way: go to http://hmea.hme.hmeafamily.org/ and fill out a “Connect With Us” and/or a “contact us” form

Hi Cheryl,

It appears that you have your DTS connection URL set to an IP address that is not (or is no longer, if this was working in the past) publically available. The short term solution would be to ask your server admin to make the server’s IP address, 50.22.122.38 , publically available over port 80.

Long term, you’ll want to set CM1 to use a public hostname as the main DTS connection URL. For example, in your delivery-servers.xml, set your from:

<connection-url> http://50.22.122.38:80</connection-url>



To:

<connection-url>http://hmea.hme.hmeafamily.org</connection-url>



Then restart CM1 and republish all of your sites. More detailed instructions relating to this process can be found here:


https://help.percussion.com/percussion-cm1/install-setup/network-and-system-configuration/web-server-configuration/production-web-server-setup/index

Hi Nathaniel - I am working with Cheryl on this problem. We have reset the IP address to the new/correct one, so that’s all set. Now we are getting an SSL timeout error -

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)

does that sound like something in CM1 or does that live off in the server somewhere?

We’d love to get these forms working!

thanks-
bob

Hi Bob,

It looks like you’re using HTTPS (SSL) rather than HTTP for your connection URL. Is this an error? It appears that this server isn’t setup for SSL connections, and additionally, you’re specifying port 80 rather port 443 (the default HTTPS port).

Assuming this is an error, simply changing the connection URL to this and then restarting and republishing CM1 should do the trick (note the removal of HTTPS and “:80”):

<connection-url>http://192.254.217.46</connection-url>

Hi Nathaniel - thanks!

Can you tell me where in the various servers and directories I can find this config file to make the change?

-bob

Hi Bob,

Sure thing. Section #4 of this document outlines where you can find this file and how best to make changes to it:

https://help.percussion.com/percussion-cm1/install-setup/network-and-system-configuration/web-server-configuration/configuring-a-standalone-dts-tomcat-as-a-productio/index

Hi Nathaniel -

here’s a new aspect to this problem.

I went in and edited the file - http://192.254.217.46

and restarted CM1 by first stopping the Percussion service, waiting 5 minutes, then starting the service again. this was 15 minutes ago.

Now I can’t log in to Percussion in the browser - I get a 404 error at the link that was working earlier today.

I can still RDP into the server, so the box is running.

Is there something else that need restarting?

Hi Bob,

A 404 server error typically indicates an accidental duplicate start-up of the CM1 application. Even though you waited the recommended 5 minutes after shutdown, it sounds like CM1 may have hung during the shutdown sequence.

To check whether this is the case, use Task Manager (viewing processes from all users) to manually end all “java.exe” processes running out of the Percussion directory (use View > Select Columns > Image Path Name to see what directory the process is running out of). Once all of these Java processes are down, start CM1 back up, give it a few minutes to load fully, and then attempt to access the application. Let me know if this helps.

Hi Nathaniel -

That seemed to work - thanks!

(Note to anyone else reading this thread using vintage server software - in Server 2003 you need to jump through a few more hoops to see which Java is running where - this page helped me figure it out - http://www.raymond.cc/blog/determine-… )

Percussion-wise: i got the java killed off and started CM1 again. I am now re-publishing the site with the form problem. We’ll know in a while if this has worked.

thanks a lot for the server help - fingers crossed the forms start working…

Hello again -

Another unexpected item popped up yesterday -

Is there something about editing the delivery xml file and restarting CM1 that would make old/outdated/deleted page autolist items re-appear on one of our sites?

-bob

This is a great conversation that’s separate from the main topic, so I created a new topic to continue the discussion. Please reference the new topic here: https://community.percussion.com/t/old-outdated-deleted-pages-appearing-in-auto-list/1025