CC beta releases 3.4.4j, 3.4.4k, 3.4.4l

[Purple Lady]

Originally Posted by chaley

The CC debug log is empty.

I just sent it again from both yahoo and gmail.

[chaley]

Originally Posted by Purple Lady

I just sent it again from both yahoo and gmail.

I received the one sent via gmail. The one sent via yahoo arrived empty.

The log tells me what is happening, but it doesn't explain why. What I see:

1) CC does a quick check to see if the IP address in settings is visible.

2014-10-19 13:23:12.231:  Networking: checking if connect possible to ip:port xxxxx
2014-10-19 13:23:12.248:  Networking: Can connect to xxxxx

We see that this check succeeds. Some machine answers to that address. We also see that it succeeds very quickly, in 17 milliseconds, so we can assume that the machine is rather "close".

2) Because the check succeeded, CC does not do an automatic scan.

3) CC next tries to connect "for real".

2014-10-19 13:23:12.262:  ContentServer: creating connection to http://xxxxx:pppp/

This connection also succeeds in that something accepts the connection.

4) The machine that accepted the connection is mute, not answering CC's requests within two minutes.

2014-10-19 13:25:12.305:  ContentServer: Target auth state: UNCHALLENGED
2014-10-19 13:25:12.306:  ContentServer: Target auth scheme: null
2014-10-19 13:25:12.308:  ContentServer: Target status code:408
2014-10-19 13:25:12.310:  ContentServer: header: Content-Length: 0:Content-Length:0
2014-10-19 13:25:12.312:  ContentServer: header: Content-Type: text/plain:Content-Type:text/plain
2014-10-19 13:25:12.313:  OPDS: general connection failure: Server refused request: error code 408

Error code 408 is "timeout".

So, what we have is some machine accepting connections for your external IP address but not responding to queries on that connection. My guess is that your router is accepting the connections for some reason, but is unable to forward the connection or information to your server.

You can probably work around this by putting the internal IP address of your server into the first address box and the external IP address into the second address box. When connected by wifi to your local network, the internal address will (should) work. When connected to your carrier, the first address will fail because it is a private IP address, so CC will fall over to the second, external, address.

We can't do anything about falling back to automatic because as far as CC is concerned there is a computer out there answering connection requests. CC doesn't know that it is connecting to a black hole.

[Purple Lady]

Originally Posted by chaley

I received the one sent via gmail. The one sent via yahoo arrived empty.

The log tells me what is happening, but it doesn't explain why. What I see:

1) CC does a quick check to see if the IP address in settings is visible.

2014-10-19 13:23:12.231:  Networking: checking if connect possible to ip:port xxxxx
2014-10-19 13:23:12.248:  Networking: Can connect to xxxxx

We see that this check succeeds. Some machine answers to that address. We also see that it succeeds very quickly, in 17 milliseconds, so we can assume that the machine is rather "close".

2) Because the check succeeded, CC does not do an automatic scan.

3) CC next tries to connect "for real".

2014-10-19 13:23:12.262:  ContentServer: creating connection to http://xxxxx:pppp/

This connection also succeeds in that something accepts the connection.

4) The machine that accepted the connection is mute, not answering CC's requests within two minutes.

2014-10-19 13:25:12.305:  ContentServer: Target auth state: UNCHALLENGED
2014-10-19 13:25:12.306:  ContentServer: Target auth scheme: null
2014-10-19 13:25:12.308:  ContentServer: Target status code:408
2014-10-19 13:25:12.310:  ContentServer: header: Content-Length: 0:Content-Length:0
2014-10-19 13:25:12.312:  ContentServer: header: Content-Type: text/plain:Content-Type:text/plain
2014-10-19 13:25:12.313:  OPDS: general connection failure: Server refused request: error code 408

Error code 408 is "timeout".

So, what we have is some machine accepting connections for your external IP address but not responding to queries on that connection. My guess is that your router is accepting the connections for some reason, but is unable to forward the connection or information to your server.

You can probably work around this by putting the internal IP address of your server into the first address box and the external IP address into the second address box. When connected by wifi to your local network, the internal address will (should) work. When connected to your carrier, the first address will fail because it is a private IP address, so CC will fall over to the second, external, address.

We can't do anything about falling back to automatic because as far as CC is concerned there is a computer out there answering connection requests. CC doesn't know that it is connecting to a black hole.

I will try putting in the second address box when I get home. Did the Calibre log I sent you show anything? I cancelled the connect after 30-45 seconds because it was obvious it wasn't working.

I just sent you the debug log again from K-9 mail and attached a 2nd copy of the debug log manually to see if it is attached properly. Maybe the auto attach only works using the gmail app.

[chaley]

Originally Posted by Purple Lady

I will try putting in the second address box when I get home. Did the Calibre log I sent you show anything? I cancelled the connect after 30-45 seconds because it was obvious it wasn't working.

The calibre logs don't show content server connections, so I couldn't tell anything from them. You can see content server logs by going to Preferences / sharing over the net and pressing the "View server logs" button.

I just sent you the debug log again from K-9 mail and attached a 2nd copy of the debug log manually to see if it is attached properly. Maybe the auto attach only works using the gmail app.

The first attachment was a mimetype header with no data. The second attachment was there.