Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Jesper on August 12, 2002, 03:38:30 PM

Title: Blocking of https from SME-server!?
Post by: Jesper on August 12, 2002, 03:38:30 PM
Hi.. hope someone inhere can help me out...

I try to contact my firm's servermanagement site...
It's through a https connection, but everytime I try I get this message..:

ERROR
The requested URL could not be retrieved

--------------------------------------------------------------------------------

While trying to retrieve the URL: https://www.minwebside.dk:8443/

The following error was encountered:

Read Error
The system returned:

   (104) Connection reset by peer
An error condition occurred while reading data from the network. Please retry your request.

Your cache administrator is admin@dkm.dyndns.org.



--------------------------------------------------------------------------------
Generated Mon, 12 Aug 2002 10:32:23 GMT by SME.dkm.dyndns.org (Squid/2.4.STABLE3)


So it seems like there's something wrong with my server... used to work fine.. but now... nope :(
Does anyone have any idea of what to do?  (Need to say that I'm not a expert on Linux - so please be gentle with the reply's) :o)

Thanx
Jesper
Title: Re: Blocking of https from SME-server!?
Post by: schotty on August 12, 2002, 07:01:34 PM
im just having a guess at this....
Are you connecting through a firewall? does your Proxy allow the use of https: ??

Can u connect to other sites with https: and can you connect with https:/ within your lan. Have you turned https: on??
Title: Re: Blocking of https from SME-server!?
Post by: Jesper on August 12, 2002, 07:05:28 PM
Yeah!

Thanx for reacting... found the error..
Simply because my computer (not the server) had the automatic registrations of options turned on (within the Lan-settings for the browser).

DOH! I'm stupid.. but thanx anyway!

/Jesper
Title: Re: Blocking of https from SME-server!?
Post by: Oluf on December 05, 2002, 06:25:52 AM
Jesper,

Thanks for posting this "How I solved it". I had the same problem, and it was also related to the browser settings (darn IE).

-Oluf