The Website does not supply ownership information?
Posted: Fri Nov 24, 2017 5:01 am
by simon581923
Hi, I install a CentOS box, the uname -a command responses as
And I installed the ProcessMaker 3.2.1 Community.
However, while I'm trying to log on ProcessMaker 3.2.1, the Firefox complain that 'The Website does notsupply ownership information?', and refuse the user log on.
How can I do?
Should I install httpd service with SSL/TLS protocol?
Re: The Website does not supply ownership information?
Posted: Fri Nov 24, 2017 5:03 am
by simon581923
BTW, I'vd installed the ProcessMaker 3.2.1 on a Windows Server box, and everything fine.
No problem with Firefox.
WIth Chrome, the problem is the same as firefox on CentOS box.
Re: The Website does not supply ownership information?
Posted: Fri Nov 24, 2017 7:45 pm
by amosbatto
In Firefox you will see "The Website does not supply ownership information" for all web sites that don't have a secure connection through https and an "Extended Validation Certificate".
See:
https://support.mozilla.org/en-US/questions/967766
Firefox will show "this connection is not secure" for any password field in a web site that doesn't use https.
You can turn it off. See:
https://support.mozilla.org/en-US/questions/1164003
You can also turn it off by creating a mozilla.cfg file with the line:
lockPref("security.insecure_field_warning.contextual.enabled", false);
See:
https://support.mozilla.org/en-US/questions/1176926
It is best to configure PM to use SSL/TLS to avoid these warnings, however you should be able to log even if you see these warnings. If you aren't able to login, then you have some problem in how you installed PM. Did you follow these
instructions to install PM?
Re: The Website does not supply ownership information?
Posted: Sun Dec 03, 2017 9:22 pm
by simon581923
Hi, Amosbatto,
After two weeks of try & Error, We could not implement the SSL with Processmaker in CentOS 7.
We are not familiar with Linux & SSL, and, we haven't budget to purchase official SSL certificate.
But, this situation wasn'y happened under Windows Server 2012 environment.
So that, we decided using Window Server 2012 with Processmaker Community Edition for testing.
Anyway, Thank for your information.