https issue

Questions and answers for all installation-related topics for Servoy products

https issue

Postby stevek » Fri Mar 08, 2013 10:19 pm

hello all!

I hope someone has experienced this and found a solution.

I have servoy v 6 running on Centos 6.3 x64

Going to http://mysite.com:8080 works great

I instaledl apache for several other things I need

I installed a self signed certificate following the docs on the servoy WiKi and I can successfully connect to

https://mysite.com:8443

after plowing through the warnings resulting from a self-signed cert

I then purchased a SSL cert, configured it accourding to the company and inseting it into the correct location within servoy and making sure the settings in server.xml were correct.

Now when I try to goto https://mysite.com:8443 I still get the warning it is self signed, and after agreeing, it sends me to the default apache page.

So, I can connect to servoy on port 8080 with apache (httpd) also running

I cannot connect on https (port 8443 or 443)

Hope someone has a suggestion


Thanks
stevek
 
Posts: 53
Joined: Thu Jan 25, 2007 7:19 pm

Re: https issue

Postby Harjo » Sat Mar 09, 2013 12:35 pm

can you tell us more what your setup exactly is?

on which ports is Servoy configured and on which port is Apache listening?

if you use Apache in front of Servoy server (as a mod-proxy) you need to install the certificate in Apache, not in Servoy!
Harjo Kompagnie
ServoyCamp
Servoy Certified Developer
Servoy Valued Professional
SAN Developer
Harjo
 
Posts: 4321
Joined: Fri Apr 25, 2003 11:42 pm
Location: DEN HAM OV, The Netherlands

Re: https issue

Postby stevek » Tue Mar 12, 2013 4:32 pm

Harjo,

Thanks for the insight! Now after messing around with this, i have succeeded in confabulating myself even more.

This is what I have done initially -

1. Entered the SSL cert info into the /server/conf/server.xml file within servoy using both self signed (failed) then my purchased SSL (failed). Would not allow access to servoy in both cases. I then commented out those two lines using
<!-- --> so I could come back later to look at it again. Restarted servoy and I can access with http://mysite.com:8080

2. disabled the /etc/httpd/conf.d files, restarted apache with all default settings, listening only to port 80. Website opens fine, and I can access servoy on port 8080

3. enabled the etc/httpd/conf.d files, made a ssl container for the main site (mainsite.conf) on port 80 and 443. restarted apache, works fine at https://mysite.com. Servoy works fine on port 8080 (warnings of self signed certs appear when starting smart client)

4. adapted the ssl.conf to include servoy with these lines affected:

Listen 443
### beginning of virtual container ####
<VirtualHost _default_:443>
-- all SSLCertificate entered correctly as verified by being able to goto https://mysite.com`

ADDED -
ProxyPass / http://mysite.com:8080/


</ VirtualHost> ## end of container

When I goto https://mysite.com, it displays the website fine. When I goto https://mysite.com, it displays the start page for Servoy (the default index.html at 8080) as a https site (lock displays in address bar as it should)

But, when you click on the link to start the smart client, it says the cert is self-signed and gives warnings

What am I missing, or, what have I goobered up?

I found some entries in the forum on this and tried:

ProxyPass / http://nb1.region1tasc.org:8080/
# # # ProxyPass /tunnel ajp://nb1.region1tasc.org:8010/tunnel flushpackets=on
# # # ProxyPassReverse / http://nb1.region1tasc.org:8080

with only the first entry partially working.

Thanks for all who read this and suggest any alternatives.
stevek
 
Posts: 53
Joined: Thu Jan 25, 2007 7:19 pm

Re: https issue Partial fix

Postby stevek » Thu Mar 14, 2013 12:03 am

Partial solution to the problem:

First, thank you Harjo for your help!

i reconfigured the ssl.conf to include:
ProxyPass / http://nb1.region1tasc.org:8080
ProxyPassReverse / http://nb1.region1tasc.org:8080

Now I default to the servoy launch page and all the servoy-webclient services are running in https.

I still get warnings when I start smart-client - java screams it is not a valid ssl certificate. Will still look for the answer to that.

In addition, I am now able to access the main website as http://

Although, I'd really like that to be https also, but need further digging to figure this out also.

So, for now, servoy web client runs in https great!

Thanks again

Wanted to give an update - hope this does no make the post too long...............

After adding the ProxyPass into ssl.conf:

Now I have full https for Servoy, but lost https for apache. I can only access the apache portion by http://

Now, if I comment out the system-wide ProxyPass above, and replace with:

# ProxyPass /smart/ http://nb1.region1tasc.org:8080/servoy-webclient/
# ProxyPassReverse /smart/ http://nb1.region1tasc.org:8080/servoy-webclient/

# ProxyPass /nb/ http://nb1.region1tasc.org:8080/servoy-client
# ProxyPassReverse /nb/ http://nb1.region1tasc.org:8080/servoy-client

I have full SSL (https) for the whole system. I can access the website and groupware with https

BUT,

Servoy will not operate correctly. Smart client will crash during javaws loading, and the web-client loses ALL graphics and formatting

How can I fix this?

I'd post screenshots to show what Iam explaining but am unsure how to here.

Thank you for reading and I appreciate any suggestions.
stevek
 
Posts: 53
Joined: Thu Jan 25, 2007 7:19 pm


Return to Installation

Who is online

Users browsing this forum: No registered users and 4 guests

cron