5.6.0 upgrade doesn't work

Post any questions you have about using the Verj.io Studio, including client and server-side programming with Javascript or FPL, and integration with databases, web services etc.

Moderators: Dave, Jon, Steve, Ian

Segi
Ebase User
Posts: 590
Joined: Mon Dec 09, 2013 6:37 pm

5.6.0 upgrade doesn't work

#1

Postby Segi » Tue Sep 10, 2019 9:46 pm

I followed the instructions to upgrade 5.5 to 5.6 exactly as written.

After upgrading my server loads a blank white page. Dev console shows a 404 error

Has anyone here been able to successfully upgrade to 5.6.0 ?

netstat shows that it is listening on port 443. I have a java keystore which I placed in C:\VerjIOData. my server.xml (which the upgrade instructions did not mention at all but I copied to C:\VerjIOData\tomcat\conf).

My configuration from server.xml looks like this:

Code: Select all

	<Connector port="443" protocol="org.apache.coyote.http11.Http11Protocol" maxHttpHeaderSize="8192" SSLEnabled="true" maxThreads="150" minSpareThreads="25" 
     enableLookups="true" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false"  keystoreFile="C:\VerjIOData\tomcat.keystore" keystorePass="MyComplicatedPassword" />

    <Connector port="80" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="443" />
               
               
0 x

Ben
Ebase Developer
Ebase Developer
Posts: 17
Joined: Tue Sep 18, 2007 3:21 pm

Re: 5.6.0 upgrade doesn't work

#2

Postby Ben » Wed Sep 11, 2019 10:42 am

The upgrade instructions should mention server.xml, and I will make sure that mistake is fixed.

We have made important changes to server.xml, so if you have simply copied your old server.xml over the new one, that could explain why it doesn't work.

Any changes you need in server.xml will need to be reapplied to the new version. A copy of the default server.xml is stored in your installation directory at 'instDir/Server/initData/tomcat/conf/server.xml'. This file can be copied to your userdata directory at 'userDir/tomcat/conf'. It sounds like you have found this location. This is the one that should be modified with your https changes.

If you want to email your v5.5 server.xml to us at support@ebasetech.com, I am happy to do this for you.

Hopefully that's the only problem you have. If not then we can look at your logs, or perhaps we can arrange for you to send more of your userdata directory.

regards
Ben
0 x

Segi
Ebase User
Posts: 590
Joined: Mon Dec 09, 2013 6:37 pm

Re: 5.6.0 upgrade doesn't work

#3

Postby Segi » Mon Sep 23, 2019 5:17 pm

Sorry for the long response time but I am only now getting a chance to fix this.

My server.xml configuration from Verj 5.5.0 looks like this:

Code: Select all

	<Connector port="443" protocol="org.apache.coyote.http11.Http11Protocol" maxHttpHeaderSize="8192" SSLEnabled="true" maxThreads="150" minSpareThreads="25" 
     enableLookups="true" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false"  keystoreFile="C:\VerjIOData\tomcat.keystore" keystorePass="mypassword" />
    
    <Connector port="80" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="443" />
Is this the right way to specify the Tomcat keystore ?

Update:

I figured out how to get Verj 5.6.0 to work with SSL and am posting it here in case anyone else runs into this issue.

Before I explain what I did, I should mention that we use ufs and not ebase as the default web app so I followed these 3 steps from the upgrade instructions to rename the web app:

Rename ebase.xml to newname.xml in <userdata>/tomcat/conf/Catalina/localhost
Rename the ebase folder to newname in <userdata>/apps
Restart the server

I copied the code above from my old server.xml into the default one that Verj provides in C:\VerjIOData\tomcat\conf. If you accidentally overrwrote the default server.xml in C:\VerjIOData\tomcat\conf with your own like I did at first, replace server.xml with the default server.xml in C:\VerjIOData\.initData\tomcat\conf first. Then restart Verj

I copied my tomcat.keystore into C:\VerjIOData\security and renamed it truststore. I am not sure if this is needed

We also have an Angular webapp that provides the logon into our Intranet so when you visit https://intranet.oursite.com Tomcat loads index.html from the ROOT webapp.

I created the ROOT folder in C:\VerjIOData\tomcat\webapps and placed the Login web app in this folder and so far everything seems to be working correctly
0 x

Ben
Ebase Developer
Ebase Developer
Posts: 17
Joined: Tue Sep 18, 2007 3:21 pm

Re: 5.6.0 upgrade doesn't work

#4

Postby Ben » Wed Sep 25, 2019 4:58 pm

Hi Segi, that looks good to me.

Placing your keystore file at C:\VerjIOData\tomcat.keystore is good. You can put it anywhere you like. It will contain your private key for the HTTPS connector, making your webapp secure.

Copying the keystore to C:\VerjIOData\security\truststore is not required. The Verjio server will merge any certificates found here into the java truststore. The truststore is used when making secure calls to other services (e.g. a remote REST server). So it probably shouldn't contain your certificate.
0 x


Who is online

Users browsing this forum: No registered users and 3 guests