Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
what do these errors mean?
#11
Nope! See that is a browser thing. Port 2087 is a port identified to WHM as secured. When you as a user login to WHM, you type
Code:
https://hostname.server.com:2087
, I use my IP. that is when you can get a certificate error, and choose to simply ignore it. Do you get a cert error when connecting ssh? Only browsers and FTP identify certificates. I hope I have tried to help you understand. I get confused also. If I wrong, then I stand corrected.
[Image: hx2n7l.jpg]
Reply
#12
(05-15-2010, 11:30 PM)bdh734 Wrote: Nope! See that is a browser thing. Port 2087 is a port identified to WHM as secured. When you as a user login to WHM, you type
Code:
https://hostname.server.com:2087
, I use my IP. that is when you can get a certificate error, and choose to simply ignore it. Do you get a cert error when connecting ssh? Only browsers and FTP identify certificates. I hope I have tried to help you understand. I get confused also. If I wrong, then I stand corrected.

You're right that browser make it a big deal to check for bad certificates but you actually have to set certain cURL options to get it to work. One of which is:
PHP Code:
curl_setopt($chCURLOPT_SSL_VERIFYPEERfalse); 

See http://unitstep.net/blog/2009/05/05/usin...ted-sites/ for more info
Kevin Mark - TheHostingTool Lead Developer
Reply
#13
Well. when I google around, I now see that this is a common problem.
[Image: hx2n7l.jpg]
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)