13 replies to this topic

[xcom3]

Hi, I am trying to evaluate Livezilla and it works great.
So far I have not enabled SSL for the visitor, because I cannot make it work.

If I edit the server profile to https instead of http, I get this error:

Connection to server refused.

Further information:
The request was aborted: The request was canceled.

That doesn't seem to give me a lot of information. Is this expected if you change to https?
SSL is enabled and working on the server.

Some tips for making this work?

[Derek Punzova]

The port in your server profile should be 443, did you check that?

[xcom3]

Yes, I tried that. It takes around 2 min trying to connect to the server, then it gives me the same error message.

Is there any way to troubleshoot it? Logfiles maybe?

[xcom3]

Any help on this? I really would like to make it work before I buy any license.

I tried several times to make it work now, and the symptom are the same: After around 2 min, I got this error message:

Connection to server refused.
Further information:
The request was aborted: The request was canceled.

The SSL cert is a wildcard cert from RapidSSL and when I do a URL test in creating a new server, it works (webpages shows fine with HTTPS). But the server test just hangs forever (not responding) and I have to shutdown Livezilla server admin forcefully.
I tried to install in different subdirectories, but not luck. I believe I have a pretty standard config on my server, CentOS 6.2 and Apache, and on a dedicated server (no shared hosting).

Is livezilla creating some logs somewhere on the client or server itself that I can check?

[Derek Punzova]

There's a huge number of possible reasons for this (firewall, proxy, uncommon ssl settings, http forwards or other webserver configurations) and LiveZilla is not meant to debug these kind of problems.

I can offer to try to connect from our side. I just need the LiveZilla URL along with an administrator login (via PM).

Thanks.

[Derek Punzova]

Thanks for the login.

I can reproduce this problem on our side as well.

I tracked it down to the .NET Framework base class used for all outgoing connections from LiveZilla which handles everything related to HTTP/S automatically. Unfortunately, we have no influence (and no deeper insight) on the parts of the Microsoft .NET Framework itself so there's not much I can do at this point. I did some research for known problems with SSL but with no success. I also tried some other websites with SSL wildcard but these worked fine so it's not a general wildcard problem.

We also never had one any other complaints about problems in this area so this is really strange. I am sorry but I am out of ideas for now.

[xcom3]

Thanks Derek.

So the problem is in the LiveZilla admin tool (windows).
If I understand you correctly, the problem is present in the latest version if LiveZilla and you have a Windows 7 client with latest updates? Maybe this will be fixed in an upcoming release?

[Derek Punzova]

Sorry, you got me wrong.

The problem is with the .NET Framework (that's a windows component LiveZilla is based on) or with your SSL certificate's installation. Unfortunately, we cannot fix this as the problem occours outside of the code we have influence on.

We used .NET Framework 4.

[marcacer]

I have the same issue. Now how do I turn https OFF, so I can login again in a normal way?
If I'm connecting using http, I get: I need to connected with https (because that's what I programmed in server admin)

[Derek Punzova]

This explains how to get back to HTTP:
http://www.livezilla...y-require-https

[gustavo.seixas]

Please, I have the same error. And it is real, I'm sure that this error is real in Livezilla!
My sources in local machine(Windows) are the same that remotely(earlier Debian), both PHP and Mysql. And its worked in both perfectly. But when I decide to change my internet provider to Amazon EC2, the connection to Livezilla from local machine no longer works. The remote S.O., today, is Linux Ubuntu.
The local S.O. still is Windows 7.

The message is:
"Connection to server refused.

Further information:
The request was aborted: The request was canceled"

I did many, many tests, to confirm this problem.

The address for the store is: https://megabrasilia.com.br

Please. I need to find the solution for this problem.

Ps.: I have downloaded all the sources and database from server to local machine to make sure that. In local machine it work perfectly, with ssl, https.
Configuration for file "C:\Windows\System32\drivers\etc\hosts", in Windows:
127.0.0.1 www.megabrasilia.com.br
127.0.0.1 http://www.megabrasilia.com.br
127.0.0.1 https://www.megabrasilia.com.br

[Derek Punzova]

Hi Gustavo

I doubt that you really face the same problem. Please note that this is a standard error message covering hundreds of different issues.

Please perform an update to the latest version of LiveZilla. If that doesn't fix it, please let me know.

Thanks.

[gustavo.seixas]

I received, today, a message from Google that, possibly, explains this problem. And thus, possibly, suggest a problem for Livezilla to.

The message I receive in portuguese, than I translate in Google Translator and paste:

"Dear Webmaster,
Your website https://www.megabrasilia.com.br/, uses an SSL certificate that is not recognized by web browsers. This will cause many web browsers to block users' access to your website or display a security warning message when your site is accessed.
To fix the problem, get a new SSL certificate from a CA (Certificate Authority) that web browsers trust.
Thank you,
Team web tracking Google"

I do not know for sure if such message make sense, because both Chrome and IE recognize the certificates. But I think the Livezzila not recognize that.
If problem persists, I think I will change the certificates.
Important for analysis: The only difference in principle between the previous certificate and now, is the addition of the intermediate file, called SSLCertificateChainFile.

If you have any suggestion, I appreciate.
Thanks

ps: The new certificate was emitted for RapidSSL CA.

[Derek Punzova]

Thanks for the info. That explains the problems you currently have ...