Welcome, Guest. Please login or register.
Did you miss your activation email?
Saturday 21 December 2024, 11:17:37 am

Login with username, password and session length

Visit the Official Endian Reference Manual  HERE
14262 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Problem with Google Docs and some sites
0 Members and 3 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Problem with Google Docs and some sites  (Read 24848 times)
boanergos
Jr. Member
*
Offline Offline

Posts: 5


« on: Monday 21 July 2014, 06:49:19 pm »

Hello to everyone. I installed Endian Firewall 3.0.

It works, but I have encountered an issue when I try to edit a Google Document or managing different https connections.

Firefox told me:
"docs.google.com uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for efw-1405531257.localdomain (Error code: sec_error_cert_signature_algorithm_disabled)"

Same stuff for Chrome:

The endian firewall settings are more or less with default and I have disabled outgoing firewall. Why the firewall is not able to NAT properly and to pass the certification validation to my internal clients?

How can I avoid this error message? Which kind of configuration I need to make in my endian installation?

Thank you very much for the help.

Marco
Logged
mmiat
Sr. Member
****
Offline Offline

Gender: Male
Posts: 236


WWW
« Reply #1 on: Monday 21 July 2014, 07:34:55 pm »

check your pc timestamp, I've had a similar error once
do you have proxy enabled?
Logged

---------------------
IT Consultant
www.fsw.it
Hardware & Software
boanergos
Jr. Member
*
Offline Offline

Posts: 5


« Reply #2 on: Monday 21 July 2014, 11:03:54 pm »

I have read it on the Net.

The clock is perfectly synced with ntp server and no proxy is enabled.

Sad

Thanks for the answer!

Marco
Logged
mmiat
Sr. Member
****
Offline Offline

Gender: Male
Posts: 236


WWW
« Reply #3 on: Monday 21 July 2014, 11:30:17 pm »

I'm using Endian 2.5.2, but no configuration is required to use Google Docs. In my company we use it without problem or unique configuration. I'd think that problem is not endian. Why do you think it's caused by endian? for firefox message referring to efw-1405531257.localdomain?
Logged

---------------------
IT Consultant
www.fsw.it
Hardware & Software
boanergos
Jr. Member
*
Offline Offline

Posts: 5


« Reply #4 on: Tuesday 22 July 2014, 12:31:24 am »

I have a wifi network outside the endian and it work flawlessly. Each time I move my PC in the network of Endian firewall, I receive this error.
I will try to switch to version 2.5.2 and I will see if it works.

Cheers,
Marco
Logged
mmiat
Sr. Member
****
Offline Offline

Gender: Male
Posts: 236


WWW
« Reply #5 on: Tuesday 22 July 2014, 05:45:49 pm »

visto che la conversazione pare riguardare solo noi due, ti scrivo in italiano che mi viene meglio Smiley
hai già cercato in rete altre soluzioni al problema? ad esempio qui:
https://support.mozilla.org/en-US/kb/connection-untrusted-error-message
scrivono:
Quote
A common situation is when the certificate is actually for a different part of the same site. For example, you may have visited https://example.com, but the certificate is for https://www.example.com. In this case, if you access https://www.example.com directly, you should not receive the warning.

hai provato ad usare la navigazione in incognito, per capire se magari il browser s'è associato il certificato in modo errato? bye
Logged

---------------------
IT Consultant
www.fsw.it
Hardware & Software
boanergos
Jr. Member
*
Offline Offline

Posts: 5


« Reply #6 on: Tuesday 22 July 2014, 07:18:14 pm »

Ho provato a mettere la navigazione in incognito, ma il risultato è sempre lo stesso.
A questo punto installo la 2.5.2 che hai messo tu e per ora pace. Non ho tempo purtroppo di stare dietro a questo problema.

Vediamo come va.

Sembra che il certificato sia filtrato e (bruttissima frase) non si natti il certificato dal nome del firewall all'host di destinazione.

A presto aggiornamenti, provo a farlo in pausa pranzo.

Ciao,
Marco
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.078 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com