jottad.exe hangs, producing the attached log.

[shamekas]

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version): jotta-cli_0.4.4986_windows_amd64

Description of problem: jottad.exe hangs without connecting.

Expected: That it works :)

jotta-cli status (jotta-cli status):

Cannot issue status command without logging in first, jotta-cli.exe hangs on login command with jottad producing the attached log.

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

pid:1896 2018/12/18 09:59:40 Starting C:\temp\reinst\j\jottad.exe version 0.4.4986
pid:1896 2018/12/18 09:59:40 Starting with datadir C:\Users\Administrator/.jottad
pid:1896 2018/12/18 09:59:40 Scan interval set to: 2m0s
pid:1896 2018/12/18 09:59:40 Created scheduler
pid:1896 2018/12/18 10:00:01 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:00:02 Starting. No user logged in
pid:1896 2018/12/18 10:00:02 Stopping database
pid:1896 2018/12/18 10:00:02 grpc api running on :14443
pid:1896 2018/12/18 10:00:23 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:00:23 Error checking for new versions Get https://repo.jotta.us/archives/VERSION: dial tcp 185.179.128.26:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:00:45 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:01:07 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:01:29 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:01:51 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:02:13 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:02:35 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:02:57 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:03:19 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:03:41 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:04:03 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:04:25 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:04:47 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:1896 2018/12/18 10:05:09 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Traceback

Additional info: There is a system-wide proxy configured in the standard windows dialog "Internet proterties/LAN settings/Configure proxy server" The proxy works for other hosts in my network and this machine has all permissions necessary at the proxy. All other programs accessing the internet from this host works through the proxy, which as I said is system-wide. The machine is not directly connected to the internet, and doesn't have direct access, so please don't suggest to not use a proxy.

[shamekas]

Is there anyone looking into this, or is it going to be ignored for all eternity?

[shamekas]

Is there anyone looking into this? I know the standard answer is that you look into everything posted here but I can't believe it when no one is asking any further questions. No debugging goes so well that the first report is enough.

I will keep updating this with one comment every month. In a year there will be 12 comments of mine with the same text, asking for the same thing, namely that someone takes these reports seriously. We are customers. If anything, this will be one the most commented issues on this page.

[Kimbsen]

In version 0.5 we default to using the systemproxy for http if one exists. Did that resolve your issue?

[shamekas]

@Kimbsen No, it doesn't work; v0.5.13645 produces the attached log output. The machine (windows 2008 R2) has a system-wide proxy configured (Internet proterties/LAN settings/Configure proxy server). Other programs on the host can access the internet so this is not a proxy misconfiguration. I don't even see a connection attemp in the proxy logs from this host.

@olihey It's not #2995 as the log is different and I have jottad v0.4.4986 running on two other hosts with access to the internet and both work (These two have direct access to the internet).

The log follows:

pid:2572 2019/03/17 14:17:55 Starting C:\Program Files (x86)\JottaCli\jottad.exe version 0.5.13645
pid:2572 2019/03/17 14:17:55 Starting with datadir C:\Users\Administrator/.jottad
pid:2572 2019/03/17 14:17:55 Rates set @ download:0B upload:0B
pid:2572 2019/03/17 14:17:55 Scan interval set to: 1h0m0s
pid:2572 2019/03/17 14:18:16 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:2572 2019/03/17 14:18:17 Starting. No user logged in
pid:2572 2019/03/17 14:18:17 Stopping database
pid:2572 2019/03/17 14:18:17 grpc api running on :14443
pid:2572 2019/03/17 14:18:38 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:2572 2019/03/17 14:18:38 Error checking for new versions Get https://repo.jotta.us/archives/VERSION: dial tcp 185.179.128.26:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:2572 2019/03/17 14:19:00 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
pid:2572 2019/03/17 14:19:22 Unable to register device : Post https://api.jottacloud.com/auth/v1/register: dial tcp 77.40.214.217:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

[Kimbsen]

Yeah, after thinking on this, it probably doesn't work as i thought it would under windows as jottad is running as LOCAL_SYSTEM and the environment proxy settings are probably not availiable in that context.

It should however be possible to add a system environmental variable on the form: "http_proxy=http://127.0.0.1:8081/" which jottad should attempt to use.

[shamekas]

Ok this finally works. It's enough to set up a variable for the account running jottad, doesn't have to be system-wide.

I see traffic in the proxy log through port 443.

Thanks for the help.