Page 1 of 1

running OpenKM under HTTPS://

PostPosted:Wed Jun 07, 2017 7:13 am
by mbmni
dear sir / madam,

when i am typing the following URL , i am getting the following 404 error

URL is : https://localhost/OpenKM/

404 error is : /OpenKM/OpenKM/ ------ the requested resource is not available.

please be kind to guide me on this issue

thank you.

Re: running OpenKM under HTTPS://

PostPosted:Wed Jun 07, 2017 7:27 am
by FJ1200
My twp-pennyworth:

What OS are you running it on?
Is the firewall open on https?
Have you set the tomcat listening port to an https port like 443?

Since you're using localhost I'm assuming you're running it on Windows as most Linux servers certainly in my experience don't run with a GUI.

Is the Tomcat port clashing with IIS - is the port already bound to something else?

Re: running OpenKM under HTTPS://

PostPosted:Wed Jun 07, 2017 8:03 am
by mbmni
dear sir / madam,

i am running on centOS 6.9.

can you please guide me step by step to solve this issue?

thank you.

Re: running OpenKM under HTTPS://

PostPosted:Wed Jun 07, 2017 9:34 am
by mbmni
dear sir/madam,'

i am attaching the 404 error that i got after i typed the following URL

https://localhost/
404.PNG
404.PNG (23.07 KiB) Viewed 3953 times

Re: running OpenKM under HTTPS://

PostPosted:Thu Jun 08, 2017 6:38 am
by jllort
Try following the steps described here https://docs.openkm.com/kcenter/view/ok ... tandCentOS

Re: running OpenKM under HTTPS://

PostPosted:Fri Jun 09, 2017 4:47 am
by mbmni
dear sir /madam,
i obeyed the given instructions as it is in the following link
https://docs.openkm.com/kcenter/view/ok ... tandCentOS

but when i am restarting the apache, i am getting the following error
apache.PNG
apache.PNG (13.04 KiB) Viewed 3947 times

Re: running OpenKM under HTTPS://

PostPosted:Sun Jun 11, 2017 7:55 am
by jllort
Althought you see this warning, usually the reason why is not starting might be wrong certificates configuration or generation. Sometimes might be some mistake written the conf file, but usualy is the first. Check the documentation section url I wrote, and if everything is like is explained there investigate, try removing SSL parameters anc convert 443 to 80. First step should be get running in port 80 without certificates and then go for SSL, at least it will helps you to identify where might be the issue.