Basil Hendroff
Wizard
- Joined
- Jan 4, 2014
- Messages
- 1,644
I just installed Chrome on my laptop and when I go to my owncloud page it says:
The site's security certificate is not trusted!
You attempted to reach 192.168.2.121, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications.
You should not proceed, especially if you have never seen this warning before for this site.
Not sure if you've changed your browser settings to reject self-signed certs?????
Problem solved! There were two issues.
The first was I needed to set up port forward for https WAN port 443 in my router to the owncloud jail ip at port 443.
The second was, in my case, because of some sort of port conflict on incoming WAN port 80, I had to use port 83 for incoming http requests to owncloud. When switching to https, I'd forgotten to remove port 83 from the address. That was just silly on my part, but easy to do for a noob.
You may like to consider adding something to your as yet unreleased owncloud guide on owncloud listening on port 80 (http) and port 443 (https) so router port forwarding is a prerequisite. Further, the text below is valid as long as port forwarding uses the same ports between the internal network and the internet (which wasn't possible for me for http for reasons still unclear to me).
Next I'm going to force https. To do this you simply change your browser webpage address from http to https. Next I click on my username in the upper right corner and choose "admin" from the dropdown. Then scroll down to Security and check the box "Enforce HTTPS". This prevents http connections. Now we have some security when transferring files. You will need to cycle the plugin off and then back on for this setting to be enforced. So go ahead and cycle the plugin of and then back on.