Article View: alt.os.linux.mandrake
Article #559Re: http:// does work but https://
From: Kasper Dupont
Date: Mon, 01 Oct 2001 18:43
Date: Mon, 01 Oct 2001 18:43
49 lines
3098 bytes
3098 bytes
I tried telneting to the ports 78-82 on this host. On port 80 one of the times I got a no route to host error. The rest of the times telnet just kept retrying. On the other ports I got an immidiate connection refused. Which is the usual error when no program is listening on the port. I think something must explicitly block connections. My computer sends the SYN packets but no response comes back. If traceroute could use TCP SYN packets instead of UDP packets it would be possible to see exactly how far the packets comes. (But I don't have the time to start rewriting traceroute.) Does this problem appear even if you try from a browser on the same computer, or is there only problems accross the net? Maybee your ISP blocks access to port 80 on your machine. (To protect you against CodeRed and friends??) Try typing the these two commands as root and tell us what output you get: iptables -L ipchains -L �j���H wrote: > > sorry, it should be https://kkwong.no-ip.com works but not > http://kkwong.no-ip.com > any comment? > thanks a lot in advance. > > "�j���H" <a@b.com> ���g��l�� news:9p90a7$6jf2@imsp212.netvigator.com... > > I have installed Mandrake 7.2 with IP forward by no-ip.com. > > When I access the homepage of my server, http://xxx does work but > > https://xxx works. > > What should I do to solve the problem? > > Please help. > > > > foreverbigface@yahoo.com > > > > > > -- Kasper Dupont
Technical Details
Message-ID:
<3BB8B964.41C6@daimi.au.dk>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!howland.erols.net!news.net.uni-c.dk!not-for-mailReferences:
<9p90a7$6jf2@imsp212.netvigator.com> <9pa9j9$j8g1@imsp212.netvigator.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII X-Google-Thread: f798d,21052ec04edd5b07 X-Google-Attributes: gidf798d,public X-Google-Thread: f8a83,21052ec04edd5b07 X-Google-Attributes: gidf8a83,public X-Google-Thread: 10d8ad,21052ec04edd5b07 X-Google-Attributes: gid10d8ad,public X-Google-Thread: 103fcc,21052ec04edd5b07 X-Google-Attributes: gid103fcc,public X-Google-Thread: f9b51,21052ec04edd5b07 X-Google-Attributes: gidf9b51,public X-Google-Thread: 106e9e,21052ec04edd5b07 X-Google-Attributes: gid106e9e,public X-Google-Thread: f9382,21052ec04edd5b07 X-Google-Attributes: gidf9382,public X-Google-ArrivalTime: 2001-10-01 11:43:50 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!howland.erols.net!news.net.uni-c.dk!not-for-mail From: Kasper Dupont <kasperd@daimi.au.dk> Newsgroups: alt.os.linux.mandrake,comp.os.linux,comp.os.linux.security,comp.os.linux.setup,hk.comp.os.linux,tw.bbs.comp.linux,uk.comp.os.linux Subject: Re: http:// does work but https:// Date: Mon, 01 Oct 2001 20:43:48 +0200 Organization: daimi.au.dk Lines: 49 Message-ID: <3BB8B964.41C6@daimi.au.dk> References: <9p90a7$6jf2@imsp212.netvigator.com> <9pa9j9$j8g1@imsp212.netvigator.com> NNTP-Posting-Host: vertigo.daimi.au.dk Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: news.net.uni-c.dk 1001961829 33318 130.225.19.42 (1 Oct 2001 18:43:49 GMT) X-Complaints-To: usenet@news.net.uni-c.dk NNTP-Posting-Date: Mon, 1 Oct 2001 18:43:49 +0000 (UTC) X-Mailer: Mozilla 3.04 (X11; I; IRIX64 6.5 IP27)