help request: debugging pagekite logs

[Ram]

I've a https server running at home and I use pagekite to expose thru
my own server. The problem I'm having is that pagekite says all kites
are flying well, but the webpage gives the error:
The connection was interrupted

=====================================================

The connection to steven.joe.mydomain.us was interrupted while the
page was loading.

The site could be temporarily unavailable or too busy. Try again in
a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy,
make sure
that Firefox is permitted to access the Web.

=====================================================

On the server the logs look like this:

ts=5fa96ec1; t=2012-05-08T14:06:41; ll=57c; BE=Live; proto=https;
domain=steven.joe.mydomain.com; id=s2af/~49.232:45095
ts=530fa96ec1; t=2012-05-08T14:06:41; ll=57d; BE=Live; quota=None;
id=s2af/~49.232:45095

The client logs say :

ts=5fa96ed8; t=2012-05-08T15:07:04; ll=4; debug=FIXME: Should try
epoll!
ts=5fa96ed8; t=2012-05-08T15:07:04; ll=5; FE=112.192.49.23:443
ts=5fa96ed8; t=2012-05-08T15:07:04; ll=6; FE=112.192.49.23:443;
proto=https; domain=steven.joe.mydomain.com; ssl=False; id=s1
ts=5fa96ed8; t=2012-05-08T15:07:04; ll=7;
bid=https:steven.joe.mydomain.com; status=0x1000
ts=5fa96ed8; t=2012-05-08T15:07:04; ll=8; connect=112.192.49.23:443
ts=5fa96ef6; t=2012-05-08T15:07:34; ll=9; debug=Ping;
host=112.192.49.23:443; id=s1
ts=5fa96f55; t=2012-05-08T15:09:09; ll=a; debug=Ping;
host=112.192.49.23:443; id=s1
ts=5fa96f73; t=2012-05-08T15:09:39; ll=b; debug=Ping;
host=112.192.49.23:443; id=s1
ts=5fa96f9e; t=2012-05-08T15:10:22; ll=c; debug=AuthThread: done
ts=5fa96f9e; t=2012-05-08T15:10:22; ll=d; debug=UiCommunicator: done

Pagekite says:

Kites flying well -- all is well.

What am I missing? This is an ubuntu box. On the localhost, my server
does render properly. What am I missing?

[Christoph Witzany]

Are you sure you are checking the right domain?

You are mentioning steven.joe.mydomain.us while the kite is ponting at
steven.joe.mydomain.com.

If something is wrong with pagekite you get a pagekite error message
that also tells you if the error is on the frontend or backend side.

Your pagekite logs look pretty inocuous, don't see any sign of trouble there.

Can you ping the domain your frontend runs on?
If you ping it, does it connect to the correct ip address?

regards
Christoph (pagekite user & fan)

2012/5/8 Ram <mobileb...@gmail.com>:

[Bjarni Rúnar Einarsson]

Hi Ram,

On Tue, May 8, 2012 at 7:36 PM, Ram <mobileb...@gmail.com> wrote:
>
>   The connection to steven.joe.mydomain.us was interrupted while the
> page was loading.

Here you say steven.joe.mydomain.us, below you have a .com address.

Maybe you know this already, but I also notice that you are only
flying an HTTPS kite, which means the front-end will not be listening
for connections over normal HTTP for that domain. Flying an HTTPS
connection like this also depends on you having a properly configured
SSL certificate for your webserver.

> =====================================================
>
> On the server the logs look like this:
>
> ts=5fa96ec1; t=2012-05-08T14:06:41; ll=57c; BE=Live; proto=https;
> domain=steven.joe.mydomain.com; id=s2af/~49.232:45095
> ts=530fa96ec1; t=2012-05-08T14:06:41; ll=57d; BE=Live; quota=None;
> id=s2af/~49.232:45095

--
Bjarni R. Einarsson
Founder, lead developer of PageKite.

Make localhost servers visible to the world: https://pagekite.net/

[Ram]

Hi Bjarni,

Thanks for the quick reply. Indeed the domains are the same. I just
did an error while obfuscating the "mydomain.com/us". Sorry about
that. Indeed the https://localhost:xxx works, which means that my
https server keys are setup right. Also, on other machines, I have no
problem using https://steven.mydomain.com. On this ubuntu box,
steven.joe.mydomain.com is creating trouble. I wonder if the problem
is because of the extra "." in the url?

Thanks.

On May 8, 4:03 pm, Bjarni Rúnar Einarsson <b...@pagekite.net> wrote:
> Hi Ram,
>

[Bjarni Rúnar Einarsson]

On Tue, May 8, 2012 at 9:17 PM, Ram <mobileb...@gmail.com> wrote:
> Thanks for the quick reply. Indeed the domains are the same. I just
> did an error while obfuscating the "mydomain.com/us". Sorry about
> that. Indeed the https://localhost:xxx works, which means that my
> https server keys are setup right. Also, on other machines, I have no
> problem using https://steven.mydomain.com. On this ubuntu box,
> steven.joe.mydomain.com is creating trouble. I wonder if the problem
> is because of the extra "." in the url?

Well, the log snippet you sent was so short it is hard to say, but it
didn't contain any lines indicating that the front-end (what you are
calling a server) had seen any incoming traffic at all. The number of
dots in the URL only matter if you are using a wild-card certificate
and terminating the SSL at the front-end, which does not appear to be
what you are doing.

If you prefer you can send me some complete, unsanitized log snippets
privately and I will take another look. Obviously I will keep your
details confidential. While you won't tell me the domain name and
only give me sanitized log fragments, it is very difficult to debug
with any degree of confidence.