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:80802. 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:8080with only the first entry partially working.
Thanks for all who read this and suggest any alternatives.